#soylent | Logs for 2025-01-18
« return
[08:04:40] <janrinok> chromas, there was a short break in contact with the site yesterday evening for me - about the same time mrpg had his read error. I was getting a 500 backend fetch error. It seems to happen periodically (weekly?) perhaps when a specific job is running.
[08:05:46] <janrinok> ...or kolie restarted irc to make it use the updated certificates.
[08:06:01] <chromas> if he'd restarted it you would have left irc
[08:06:30] <chromas> I don't recall noticing any burps but I haven't looked at the site much
[08:08:52] <janrinok> yeah, mine was a site break not an irc break.
[08:09:23] <chromas> are there any weekly cron jobs?
[08:10:03] <janrinok> I would imagine so but I don't have any specifics.
[08:11:05] <janrinok> It might also be triggered by something using a specific amount of memory rather than at a set time.
[08:12:35] <chromas> I wonder if there's anything in the logs. maybe something's being oom killed and restarted
[08:13:52] <janrinok> last time kolie looked he didn't find anything in the container logs, so perhaps it is something that is meant to happen but the action is taking more resources than expected.
[08:14:25] <chromas> do all the logs from inside each container get exported to some central system?
[08:14:40] <janrinok> don't know
[08:15:12] <chromas> you're not running an instance of my bot on there are you? that would kill it for sure
[08:16:37] <janrinok> lol - I don't think so.
[12:58:04] -!- jje has quit [Quit: ZNC - https://znc.in]
[12:58:26] -!- jje [jje!jje@ddjffrbpjin.info] has joined #soylent
[15:30:53] -!- jje has quit [Quit: ZNC - https://znc.in]
[15:31:13] -!- jje [jje!jje@ddjffrbpjin.info] has joined #soylent
[19:35:32] <chromas> nginx is weird
[19:35:52] <janrinok> it is "different"
[19:36:01] <chromas> if I put in a rule to deny a specific page (x.html) then it becomes a 403 error
[19:36:21] <chromas> if I put in a rule to specifically allow an ip range then it becomes a 404
[19:36:54] <janrinok> Having used it I prefer it over Apache but it has a different way of working
[19:37:57] <janrinok> Unless you have to use it, and if you already know Apache, then stick with what you know. I started with nginx and that is what I am used to. However, I am now switching over to GO's built in server.
[19:38:43] <chromas> Mostly I'm using it as a front-end to other servers, so I should probably replace it with a trendy modern alternative like caddy
[19:52:28] <janrinok> It is very good for that purpose.