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

--- Ezycom V3.00 01FB064B
* Origin: Deep Space Gateways BBS Running EZYCOM V3.0 (21:4/120)

Re: busy nodes
By: Datalus to Everyone on Mon Nov 16 2020 09:07 am

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?

I was seeing this a few versions ago but my Mystic A47 is running well at the moment. Try an update if there is a newer one, it might make a difference for you.

Ttyl :-),
Al

... I'm sure it's clearly explained in the Zmodem DOC's
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

By: Datalus to Everyone on Mon Nov 16 2020 09:07 am
I was seeing this a few versions ago but my Mystic A47 is running well at the moment. Try an update if there is a newer one, it might make a difference for you.

I just downloaded this a yesterday! So there isnt a newer one that I
dont believe.
Thanks Datalus

--- Ezycom V3.00 01FB064B
* Origin: Deep Space Gateways BBS Running EZYCOM V3.0 (21:4/120)

Re: busy nodes
By: Datalus to Al on Mon Nov 16 2020 11:18 am

I just downloaded this a yesterday! So there isnt a newer one that I
dont believe.

Well in that case you are upto date. If these problem continue we'll need to take a closer look and see if we can figure out why that is happening.

Ttyl :-),
Al

... Epithaph on McCoy's Gravestone: I'm dead, Jim!
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

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

Are you talking about busy BINP nodes? Because yesterday I did notice that one or more of my FTNs wouldn't poll out because of 'busy nodes'.

Mystic says that if theres an issue, it deletes the busy files after 24hours - and my FTNs have since been polling as normal, but... I think I saw an issue too.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

By: Datalus to Al on Mon Nov 16 2020 11:18 am

I just downloaded this a yesterday! So there isnt a newer one that I
dont believe.

Well in that case you are upto date. If these problem continue we'll need to take a closer look and see if we can figure out why that is happening.
Ttyl :-),
Al

yes we need to find out why its doing it
Thanks Datalus

--- Ezycom V3.00 01FB064B
* Origin: Deep Space Gateways BBS Running EZYCOM V3.0 (21:4/120)

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

Yes same except when doing the killbusy thing it came back as soon as
it tried to send again.

Are you talking about busy BINP nodes? Because yesterday I did notice that one or more of my FTNs wouldn't poll out because of 'busy nodes'.
saw an issue too.

So I dont know whats up. I dont know if this in fact is true either
but I downloaded A46 and set it up andnext thing I know I was
deleteing all my hard drives, It was sending files Black Panther it
sent him 20 files that werent suppost to be sent so who ever needs to
check the mysticbbs files, I was getting all kinds of code symbols in
the message setup area, Just to be safe it probily need checking. Id
hate for someone else to lose over 5 years of files ect.
Datalus

--- Ezycom V3.00 01FB064B
* Origin: Deep Space Gateways BBS Running EZYCOM V3.0 (21:4/120)

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)

On 17 Nov 2020, Datalus said the following...

I just downloaded this a yesterday! So there isnt a newer one that I
dont believe.

Great, so we're all on the same page (or alpha). I did my experiment with a quick script change - just did a blind 10 second wait (Linux: sleep 10)
between polls and no more busy messages on my script ;) I could make it
fancier (add a busy loop waiting for it to stop saying busy), but the 10 seconds more than does it. The logs show most messages finish within 2
seconds. It's a Pi3 doing it under a 32-bit version of Linux & mystic and it polls 64-bit systems (my points) which are much faster. Just letting the Pi
run slower does it ;)
So I say again, look at your scripts ;)

--- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)