Subj : Hub 3 Update
To : deon
From : Al
Date : Fri Apr 12 2024 08:14 am
>> I just cleared the holds on net 3 a hour ago or so.
> OK, there are probably a couple of reasons for this:
> * There is major construction going on nearby, and they are constantly taking
>my internet down for "maintenance" - and its prolonged (usually around 10hrs).
>(They are rebuilding the rail line near me, and its an 18-24 mth project while
> they move it above ground.). So I imagine this long outage is probably a
> primary reason.
> (I have a hotspot, which gets traffic when my main cable goes down, so mail
> still flows, but only outbound from me.)
> * I've taken hub down for updates.
>* I nightly backup "pauses" the container and backs up the hub, but that shoul
>only be a few mins. But that might be happing while there is a session active.
Yep, any of the above would cause sessions to fail.
> * My IPv4 link goes down (IP6 is much more reliable...)
I only have IPv4 here. That's caused by a bad actor here in the internet backbone.
> Tonight I stopped the hub from accepting inbound calls while I cleared the
> backlog - it made it easier for me to trace a problem in the logs - which is
> when I noticed the kernel killing the db... ;)
> How many failed attempts (and time) before your system puts me on hold?
The mailer doesn't actually switch mail to hold but it it stops polling after 3 failed attempts. That will happen after about 5 minutes if any of the above is going on. I delete that failed call counter in nightly maintanance and during the day I do it myself if needed.
>> Sometimes when I watch mailer sessions with hub 3 the session is very slow.
>> This could also be the cause of failures. I don't know why the session
>> progresses slowly. A lack of memory perhaps?
>Slow as in there is a delay before there are transfers? binkp by default has a
> 5 min timeout, hopefully not that slow that it times out?
I have never seen a session fail. Inbound mail session are handled by a daemon so I can only read the logs to see what is happening.
I can watch outbound mail sessions if I switch to that window. Watching connects with hub 3 looks like the session is running 300 baud. Even so I have never seen a session failure, it is just slow.
>Outbound mail bundles are built on the fly, and the DB has a lot of mail in it
>(I've never deleted anything...), but it should be seconds before mail packets
> are ready, not minutes...
> That said, I've noticed the website is slowing down, so I may need to think
> about better DB indexes and/or deleting some mail.
> To be honest, I'm surprised that memory is the issue - docker stats show it
> using < 200MB of the 512MB that I had assigned to the DB, yet the kernel was
>killing it (oom-killer). I've doubled it just in case, but I'll need to keep a
> eye on it.
It may be something other than memory, I wonder if the process that is running your mailer/tosser is getting enough cpu time to do what it needs to do?
Anyway, I think your new mailer/tosser is doing a good job although there may be more needed that you'll need to identify and sort out.
--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
