#dev | Logs for 2020-01-20

« return
[15:24:37] <Bytram> TheMightyBuzzard: Good morning! Looks like something is going sideways on dev. at h:05, h:10, h:20, h:30, h:40,, and h:50, I am getting e-mailed a "slashd Error Alert" that "SLASHD line 165 produced the following error: update_twitter.pl odd exit (status 25, signal 0)"
[15:25:15] <Bytram> Started receiving them at 2020-01-19 09:10AM EST
[15:25:58] <Bytram> I've received more than 60 e-mails so far and they are still coming! HELP!
[15:41:49] <Bytram> TheMightyBuzzard: Just got another e-mail!
[15:48:23] * Bytram has no idea why dev would want to updaye twitter, anyway.
[15:50:08] <TheMightyBuzzard> because we like to debug twitter functionality without having to use prod
[15:50:19] <Bytram> okaaay
[15:50:43] <Bytram> I should be getting another email any moment
[15:51:32] <Bytram> well, it looks like something happened about 25 hours ago.
[15:51:45] <Bytram> and there it is.
[16:00:41] <Bytram> Thanks a bunch for looking into it. Very much appreciated!
[16:07:07] <Bytram> and just got another email
[16:15:12] <TheMightyBuzzard> Bytram, outdated perl ssl module. fixed.
[16:16:27] <Bytram> YAYS!!!
[16:16:34] <Bytram> Ummmm...
[16:16:44] <Bytram> how did it get loaded/started?
[16:17:48] <TheMightyBuzzard> how did what get loaded/started?
[16:19:26] <Bytram> try again, the outdated perl ssl module
[16:20:10] <Bytram> IOW, things suddenly got very "noisy" and I wonder what changed to make that happen?
[16:23:36] <TheMightyBuzzard> we updated openssl back in september on dev. you should have been getting errors since then but slashd had crashed on dev.
[16:23:43] <Bytram> ahhh
[16:23:46] <Bytram> okay.
[16:24:04] <Bytram> I *just* got another email, but suspect it was still emptying its queue?
[16:24:22] <Bytram> will know in another 10 minutes! THANKS!!!
[16:27:25] <TheMightyBuzzard> email ain't instant
[16:27:51] <Bytram> nod nod; hence my qualification. I appreciate the clarification, though.