On 16 Nov 2020, Datalus said the following...
111
Hey Guys,
anyone using A47 have this problem of busy nodes? I have used the mis killbusy all command and it kills the busy node problem but when it
ties to send mail again it comes back. Any suggestions?
Thanks Datalus
So that was the original message. I too see that busy node issue, but I
suspect it's my own polling scripts that are doing it. In my case I poll my feeds (Agency & Necronomicon) which generally works, but then I poll my points which will perhaps be busy as I poll from both addresses. I suspect I need to add some busy & retry checks in to the polling script. The other thing to try is polling one at a time or allowing some wait for each to finish (seconds).
I poll the system as 21:1/145 (which works fine), but then as 80:603/0 which will usually times out with that busy message. I'm sure that it's what I am doing that causes it since I'm in control of all of the ones except the original feeds. If I got busy from the feeds I'd change when I polled or try
to work in some retry method. What I see there is Agency mostly goes through and I get some busy messages from Necronomicon.
Anyway, look to your polling scripts as I'm sure that's most of the cause on mine ;) We need some lessons in better polling script handling from Avon who seems the best at it.
--- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)