#dev | Logs for 2021-01-11
« return
[23:52:40] <Bytram> Oh, right. good!
[23:52:33] * Bytram is fully capable of creating^W revealing new error
[23:52:06] <TheMightyBuzzard> headache was a lack of caffeine headache. kidney was the prollem. mostly sorted now.
[23:51:54] <Bytram> =blame
[23:51:38] <TheMightyBuzzard> use xzless if you really need to peruse it instead of waiting on shiny new errors that are bound to crop up.
[23:51:35] <Bytram> TheMightyBuzzard: Thanks again for handling the certs! I hope your headache is abating?!
[23:50:57] <Bytram> ;^)
[23:50:46] <TheMightyBuzzard> don't unzip it. i like it much better at 21M than 1.9G
[23:48:48] <Bytram> Ahh! "log rotate" that was the term I was trying to remember!
[23:48:09] * Bytram could prolly unzip it (the log, that is)
[23:40:32] <TheMightyBuzzard> too late, zipping up the current log
[23:40:23] <Bytram> gotta look, give me a bit to get back on'
[23:40:03] <TheMightyBuzzard> what apache error?
[23:39:44] <Bytram> One common manifestation were errors like expecting INT for a comparison bu the provided value (provided in the log) was certainly a string.
[23:38:16] <Bytram> the apache error log was all new to me, and at times recording a message every 3-5 seconds. Long lines and word wrap made it difficult to follow along.
[23:34:31] <chromas> anything good in the log?
[23:34:07] <SedBot> <Bytram> Then, just the size of each log file could itself be a clue as to how things were going.
[23:34:06] <Bytram> s/^The/Then/
[23:33:51] <Bytram> The, just the size of each log file could itself be a clue as to how things were going.
[23:32:56] <Bytram> speaking of which, IIRC, we were up to something like 1.2 GB in that apache error log. I'm surprised there is no, what's the term? rollover on the log each day?
[23:32:53] <chromas> can't adjust the log level?
[23:32:25] <TheMightyBuzzard> hits about a meg of text every five minutes to give you an idea of the verbosity
[23:31:34] <Bytram> k
[23:31:28] <TheMightyBuzzard> nothing in any other log
[23:31:18] <TheMightyBuzzard> not unless i have logging running
[23:30:42] <Bytram> Maybe there's something in some other log that correlates?
[23:30:25] <Bytram> all or nothing? Why am I not surprised? Thanks. Would it help any if we mention every time we get one?
[23:28:55] <TheMightyBuzzard> Bytram, varnish doesn't log by default. have to explicitly tell it to and it's very verbose.
[21:55:22] <Bytram> Edit story, make change, clicked update, ~10sec delay, got 503 (varnish error), clicked back in my browser, clicked update again, another delay, another 503. Closed lab. Reopened edit from story, corrected same, clicked update, another delay, and another 503. Gave up, went back to refresh original story intending to try editing from a fresh source... and saw the change HAD been made.
[21:51:34] <Bytram> TheMightyBuzzard: FYI, repeatedly got 503s while trying to post a correction to a story. Happened around 2021.01.11 12:24 ET
[04:35:38] -!- requerdanos [requerdanos!~requerdan@Soylent/Staff/Editor/requerdanos] has joined #dev
[04:31:39] -!- requerdanos has quit [Ping timeout: 265 seconds]