#soylent | Logs for 2025-01-06

« return
[01:24:26] -!- plenty [plenty!~plenty@130.195.uym.jz] has joined #soylent
[01:24:55] <plenty> No shame in being stupid. khallow defends elmo defending trump.
[01:25:33] -!- plenty has quit [Client Quit]
[01:26:05] <kyonko> cornucopeia
[11:10:33] -!- plentywood [plentywood!~plentywoo@208.85.or.woz] has joined #soylent
[11:33:10] <plentywood> =asub https://eu.usatoday.com
[11:33:20] <plentywood> =submit https://eu.usatoday.com
[11:45:22] <plentywood> Well, if we don't want any more subs, just say so.
[11:49:04] <janrinok> try submitting them on the correct channel
[12:00:15] <plentywood> Messed-up site you are running here.
[12:01:32] -!- plentywood has quit [Quit: Client closed]
[12:25:02] <janrinok> =submit https://www.technologyreview.com
[12:25:57] <janrinok> chromas, kick the bots please
[13:19:29] -!- chromas [chromas!~chromas@Soylent/Staph/Infector/chromas] has joined #soylent
[13:19:29] -!- mode/#soylent [+v chromas] by Imogen
[13:20:57] <chromas> Happy velvet rope day
[13:21:40] <Ingar> it's a BDSM holiday ?
[13:29:52] <chromas> Biggus Dickus Soylent Meniscus
[13:55:07] <drussell> Just and FYI, but I just got a 500 Internal Server Error, then no server response at all for a minute, even trying to just load the main page in another tab, the it went back to normal...
[13:55:18] <drussell> Was someone just restarting something?
[13:55:44] <drussell> It seems normal now, regardless.... so just an FYI.
[13:57:11] <Ingar> welcome to my internet connection of the past two months
[13:57:25] <Ingar> (my ISP is doind "upgrades")
[13:58:24] <drussell> LOL
[13:58:36] <drussell> (That wouldn't explain a 500 Internal Server Error, though)
[14:00:15] <chromas> Maybe they're secretly piping you through a broken proxy
[14:04:52] <janrinok> drussell, it has done that before and I have experienced it. However, as you say it cleared itself. There is nothing in the logs that can explain it. None of the containers appeared to have restarted themselves.
[14:10:06] <janrinok> there is also a similar problem on dev - perhaps there are some clues on that system. On dev it is a problem with the 'varnish' cache which isn't restarting itself.
[14:12:18] <janrinok> The problem definitely exists as it killed one of my bots at just before 1456 which seems to tie in with what you saw.
[14:13:25] <janrinok> chromas, can you check the bots please
[14:14:02] <janrinok> ah - it has sprung back into life again
[14:56:39] <Ingar> that's what she said
[20:34:21] -!- plentywood [plentywood!~plentywoo@185.191.rvo.qz] has joined #soylent
[20:36:49] <plentywood> Nothing works? Or is this normal?
[20:41:20] <plentywood> Trump announces tariffs on New York real estate, and health insurance. Prices expected to rise.
[20:50:15] -!- plentywood has quit [Quit: Client closed]
[21:33:34] <kolie> I've never been around when its doing its daily 500 dance
[21:33:53] <kolie> I think it has to be one of the perl cleanup tasks or something.
[21:34:07] -!- soylentil42 [soylentil42!~soylentil@177.107.kgp.n] has joined #soylent
[21:34:21] -!- soylentil42 has quit [Client Quit]
[21:41:57] <kolie> dev doesn't hjave a problem with varnish
[21:42:04] <kolie> varnish is reporting the backend isn't responding.
[21:45:07] <kolie> rehash container itself is offline.
[21:49:32] <kolie> getting a weird error in rehash-dev, nothing changed so not sure what happened, im rebuilding the container.
[21:53:36] <kolie> Something with the network connecting the database and the rehash got out of sync.
[21:53:50] <kolie> everything back in line now
[22:04:21] <drussell> Yeah, it does seem like it is just a temporary, transient thing, as if the backend just gets very, very busy for a moment or something...
[22:04:42] <drussell> It seems to come right back to life a minute or two later and seems fine.
[22:05:34] <drussell> Some clean-up task or something just overloading something for a moment seems likely.
[22:09:13] <kolie> Yea they seem to happen like right before I'm up around 1400 UTC
[22:26:37] <drussell> Of course...
[22:27:07] <drussell> Things always like to break, or make funny noises while thumbing their nose at you precisely when you are not looking! ;)
[22:27:31] -!- plentywood [plentywood!~plentywoo@45.250.nso.qgq] has joined #soylent
[22:27:40] -!- plentywood has quit [Client Quit]
[22:28:01] -!- plentywood [plentywood!~plentywoo@146.70.nwh.jli] has joined #soylent
[22:28:06] <drussell> Of course, since it is a very short-lived, transient / intermittent issue, those are always extra pesky to try to diagnose...
[22:29:51] <plentywood> Like trying to figure out who is deleting comments? Oh, feature, not a bug!
[22:32:45] <plentywood> Are any Soylentils on Bluesky?
[22:34:34] <plentywood> =submit https://www.rawstory.com
[22:35:10] -!- plentywood has quit [Quit: Client closed]
[23:01:25] -!- chromas has quit [Ping timeout: 272 seconds]
[23:01:39] -!- chromas [chromas!~chromas@Soylent/Staph/Infector/chromas] has joined #soylent
[23:01:39] -!- mode/#soylent [+v chromas] by Imogen