[00:01] <tomreyn> i.e. the live installer still deviates in more ways from the result the d-i would provide. the bug tracker has more details, but i'm not going into those now. ;-)
[08:52] <lordievader> Good morning
[11:57] <AlecTaylor> hi
[11:57] <AlecTaylor> I'm thinking to move from Ubuntu Server. It's a little heavy, and whenever I login it needs upgrades then it needs a reboot. What's a better solution, maybe something with livepatch and auto updates?
[14:13] <Ussat> https://www.phoronix.com/scan.php?page=news_item&px=Debian-AH-Archive-Removal
[14:13] <Ussat> srsly
[23:04] <keithzg[m]> Hmmmm, I'm suddenly (as of a few hours ago) getting no mails actually delivered on our mailserver with "delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)", everything's still in the postfix queue just not actually ending up in people's Maildirs, and amavisd does seem to be running . . .
[23:17] <sarnold> keithzg[m]: what process did you expect to be listening on port 10024? does that process have logs?
[23:25] <sdeziel> keithzg: what's in the logs regarding amavis?
[23:30] <keithzg[m]> sdeziel: Nothing that seemed like any sort of failure, but about 20min ago I restarted amavis and about 2min after that everything started working again, so all's well that ends well?
[23:31] <sdeziel> keithzg[m]: I've never seen amavisd vanish so I'd be a little worried
[23:31] <sdeziel> maybe OOM reaped it?
[23:31] <keithzg[m]> sarnold: 'twas indeed amavis on that port, and as far as I can tell it didn't really log any errors anywhere
[23:32] <sarnold> :(
[23:34] <keithzg[m]> sdeziel: Yeah it is indeed concerning; I'd be tempted to point fingers at the postfix update but that seems to be purely coincidental timing since it hadn't actually been pulled down by unattended-upgrades yet.
[23:34] <sdeziel> keithzg[m]: amavis is the process listening on that socket so it can't be postfix's fault
[23:35] <sdeziel> this is the "ingestion" port IIRC
[23:38] <keithzg[m]> sdeziel I was thinking in terms of "postfix isn't actually trying to send to 10024 it just thinks it is", but yeah doesn't appear to have been the problem.
[23:38] <sarnold> you got a connection refused error
[23:38] <sarnold> that's a nice and concrete thing to work with :)
[23:41] <keithzg[m]> Yeah and it does seem to have pointed me in the right direction since restarting amavis solved things for now. Tomorrow Keith will get to worry about the Why and if it might happen again, heh.
[23:43] <sarnold> :D