--- Log opened Wed Dec 18 00:00:44 2019 00:35 -!- dasunt [~dasunt@192.249.59.215] has quit [Ping timeout: 252 seconds] 00:36 -!- dasunt [~dasunt@192.249.59.215] has joined #se2600 07:22 <@Corydon76> Evilpig_: any firewall rules? 07:23 < Evilpig_> nope 07:23 -!- Imgur[m] [nebimgurma@gateway/shell/matrix.org/x-qzbqzcfdexprurwg] has quit [Ping timeout: 240 seconds] 07:23 < Evilpig_> couldn't ping from that server to the gateway either 07:24 < Evilpig_> i'm thinking maybe a bad update for my hardware 07:24 <@Corydon76> You might also try to modprobe -r / modprobe the driver. Reset it. 07:25 < Evilpig_> that's a good idea. i'll try that if it happens again 07:25 < Evilpig_> as a potential remediation for when i'm not at home I thought about building out a simple ping to the gateway once a minute and if it fails 10 pings reboot 07:27 <@Corydon76> Just be sure to turn that off while you're upgrading your gateway 07:27 < Evilpig_> yeah that'd be a pita 07:28 <@Corydon76> Maybe pick 3 hosts on your network, one being an AP, and then if none of them respond, axe it. 07:28 < Evilpig_> it's happened twice now, i'm gonna hope it doesn't happen again. the first time it happened was right after I patched it, it came upwas on the network for a minute or two then just nothing until I rebooted it 07:28 < Evilpig_> the second time happened last night just out of the blue 07:29 < Evilpig_> been getting some plex crashes with their latest build and figured that they did something with libc again that my version didn't like so I finally went ahead and applied all of the latest patches so it really could be anything 07:38 < Evilpig_> you know if it happens again I might just roll the plex version back to 1.18.2.2029 just to rule out something in their new builds being the trigger 08:04 <@Mirage> i'm not impressed by the new player so far 08:05 < Evilpig_> it is certifiable garbage for sure 08:11 -!- strages [uid11297@gateway/web/irccloud.com/x-bamgzlyjqnckqhof] has joined #se2600 08:14 <@opticron> well, it's solved some of the issues I had with the old one so I'm at least ok with it 08:17 <@Dolemite> mr0ning, be0tches and h0ez! 08:17 * aestetix bugs Dolemite 08:22 <@Dolemite> Mirage: I would be supportive of going to a "new player" for Plex if they'd actually put in controls to let you tweak the audio synchronization. 08:27 <@Mirage> It seems like on just about everything you have to pause at the beginning of it, wait a few seconds, then play again to get it to sync up initially. So far it's been pretty good about keeping up afterward for me 08:28 -!- K4k [elw@unaffiliated/k4k] has joined #se2600 08:34 <@opticron> hmmm...I don't have audio sync problems at all 08:39 <@eryc> Evilpig_: do you have power management turned on? 08:55 < Evilpig_> eryc: nope. 08:55 < Evilpig_> at least I shouldn't. I haven't been in that bios in years 08:56 < Evilpig_> the rewind/fast forward functions of the new player stink. and I miss having the resolution, bitrate, etc show in the upper left when I hit pause, etc 09:21 -!- Imgur[m] [nebimgurma@gateway/shell/matrix.org/x-evmflbxqfqaxcaci] has joined #se2600 09:46 -!- Imgur[m] [nebimgurma@gateway/shell/matrix.org/x-evmflbxqfqaxcaci] has quit [Write error: Connection reset by peer] 10:40 -!- Imgur[m] [nebimgurma@gateway/shell/matrix.org/x-wfsgmrmksmdbowmt] has joined #se2600 11:36 -!- K4k [elw@unaffiliated/k4k] has quit [Read error: Connection reset by peer] 12:38 -!- K`Tetch [~no@unaffiliated/ktetch] has joined #se2600 12:40 -!- K`Tetch_ [~no@unaffiliated/ktetch] has quit [Ping timeout: 265 seconds] 14:34 < Evilpig_> well.... we broke awx/ansible tower, again 14:34 < Evilpig_> Hi Wilbur, 14:34 < Evilpig_> That's my bad, I see now that the clearing of job events does not actually reclaim id values. We are currently discussing this with our engineering team to see if the integer sequence and be reset or maybe modify the id column type to bigint. I will get back with you shortly. 14:35 < Evilpig_> we found a problem in their database scheme for storing events by exceeding the number of event generations that they apparently ever considered possible 15:19 <@eryc> hahaha 15:22 <@eryc> Evilpig_: for a sizable django app i developed even i used bigint's for my id's 15:23 <@eryc> i just sent redhat a patch to make include_role work in handlers 15:24 <@eryc> to fix https://github.com/ansible/ansible/issues/20493#issuecomment-562067210 15:24 < PigBot> include_role doesn't work from handlers · Issue #20493 · ansible/ansible · GitHub (at github.com) http://tinyurl.com/sq5gshu 15:25 <@Corydon76> Evilpig_: you exceeded 4.2 billion events? 15:25 <@Corydon76> Or just 2.1 billion (signed)? 15:25 <@eryc> probably the latter 15:26 <@Corydon76> Yeah, so many places don't consider the advisability of using unsigned integers. But if so, that's an easy bit to flip, which at least extends the time until they need to come up with a real fix. 15:27 <@eryc> just checked and django doesnt offer an unsigned integer field but they added biginteger around 10 years ago 15:27 <@eryc> not sure if that was in the version i was using at the time because i manually updated the schema 15:28 <@eryc> speaking of whic, Evilpig_ you can alter the table and make it a bigint if you want.. shouldn't break migrations but there's a risk 15:28 <@eryc> i could test django 15:29 <@eryc> Corydon76: most of the time if you're looking at unsigned you probably need 64bit anyway 15:29 <@Corydon76> I was thinking along the lines of a stopgap measure 15:30 <@eryc> postgres will happily convert to bigint afaik 15:30 <@Corydon76> If you run out at 2.1b, then expanding to 4.2b works until you can come up with a migration to 64 bit. 15:30 <@eryc> and django doesnt know it only checks if all the migratiosn were applied by looking for names in a table 15:30 <@Corydon76> Yeah, but... the problem is how long you're down while it does the conversion. 15:30 <@eryc> well he's down currently 15:30 <@eryc> heh 15:30 <@Corydon76> Flipping to unsigned shouldn't take any time at all 15:31 <@eryc> well he deleted all his events too 15:31 <@eryc> so it's an empty table with a maxed out identity 15:31 <@Corydon76> Heh, yeah, empty table 15:31 <@Corydon76> alter sequence... 15:32 <@Corydon76> I have index tables, and the alter sequence is now part of the rebuild process, because we once upon a time hit the max 15:32 <@eryc> yea reseting the sequence to 1 is probably the safest bet 15:45 < Evilpig_> Corydon76: 2.1b, yes 15:46 < Evilpig_> django doesn't reap old ids apparently. so we're likely going to switch to that to a bigint for a short term fix while they refigure things out 15:47 <@Corydon76> I love idiots on Quora who assume that if a cop is likely to shoot you in the back that stopping and obeying instructions is going to keep you alive. 16:52 < Evilpig_> well my plex server is off the net again. time to troubleshoot 17:13 < Evilpig_> modprobe was no use, changing ports on the switch had no effect, changed the ip of the interface and no effect. 17:13 < Evilpig_> just installed tcpdump so next time I can try to see something there, not sure what but maybe something. 19:34 <@Dagmar> Interface statistics are often quite telling 20:09 < Evilpig_> super boring 20:09 < Evilpig_> enp3s0: flags=4163 mtu 1500 inet 10.0.0.252 netmask 255.255.255.0 broadcast 10.0.0.255 ether 4c:cc:6a:88:47:a0 txqueuelen 1000 (Ethernet) RX packets 677249013 bytes 998394013076 (929.8 GiB) RX errors 0 dropped 69 overruns 0 frame 0 TX packets 191455444 bytes 148396131435 (138.2 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 20:10 < Evilpig_> I was hoping for a bunch of drops myself 20:24 < Evilpig_> I nabbed dmesg, messages, ifconfig, netstat before I rebooted it last just to get a glimpse at what might be going on 20:56 <@Dagmar> It's probably systemd. 21:36 <@Dagmar> That it shows a zero should have stood out as significant 21:36 <@Dagmar> @#$@#$ --- Log closed Thu Dec 19 00:00:45 2019