Hi,
I've read some posts about this before, but as I'm kind of a n00b to Mystic
I'm still feeling my way around somewhat. Anyhow, it acts like all the nodes are full (saying BUSY,) when in fact they are all open. Typing fidopoll killbusy all helps _sometimes_, but then only for a few minutes at others.
My only defense right now is to make a full backup several times a day and restore it when this happens because I have no clue what is causing it. Actually now that I think about it's not just a telnet thing because it
throws the same error even on a local login.

Regards,
Steve Smith
SloaneBBS.com

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Sloane BBS (21:4/112)

Hi,
I've read some posts about this before, but as I'm kind of a n00b to Mystic I'm still feeling my way around somewhat. Anyhow, it acts like
all the nodes are full (saying BUSY,) when in fact they are all open. Typing fidopoll killbusy all helps _sometimes_, but then only for a few minutes at others. My only defense right now is to make a full backup several times a day and restore it when this happens because I have no clue what is causing it. Actually now that I think about it's not just a telnet thing because it throws the same error even on a local login.

Not saying this is the answer but do you have iplocation blocking setup or at least country blocking on? And your telnet port on something other than 23? You could be getting hit with port scanning and they're taking up all the nodes.

--- Mystic BBS v1.12 A38 2018/01/01 (Raspberry Pi/32)
* Origin: Digital Wurmhole | digitalwurmhole.ddns.net:2323 (21:4/113)

Not saying this is the answer but do you have iplocation blocking setup
or at least country blocking on? And your telnet port on something other than 23? You could be getting hit with port scanning and they're taking
up all the nodes.

Well that is a very good point. It is on port 23 and it gets hammered constantly. I do have country blocking and ip blacklisting on but I need to tighten those up. Thanks for your help.

Regards,
thewoose

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Sloane BBS (21:4/112)

I've read some posts about this before, but as I'm kind of a n00b to Mystic I'm still feeling my way around somewhat. Anyhow, it acts like
all the nodes are full (saying BUSY,) when in fact they are all open. Typing fidopoll killbusy all helps _sometimes_, but then only for a few

No, fidopoll killbusy is completely unrelated to what you're describing :)

You want to run nodespy and press ENTER on the nodes and remove them, or just delete "chat*.dat" from data, but its much safer using Nodespy.

The #1 reason this happens from my experience is people clicking "X" to close their BBS node or shutting their BBS down while logged in.

Some people in Linux are reporting some issues where nodes get stuck but I am not able to see it happen here to fix it yet.

--- Mystic BBS v1.12 A39 2018/01/15 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

No, fidopoll killbusy is completely unrelated to what you're describing
:)

You want to run nodespy and press ENTER on the nodes and remove them, or just delete "chat*.dat" from data, but its much safer using Nodespy.

The #1 reason this happens from my experience is people clicking "X" to close their BBS node or shutting their BBS down while logged in.

Some people in Linux are reporting some issues where nodes get stuck but
I am not able to see it happen here to fix it yet.

Well thank you for that g00r00 ... actually this morning it happened again,
and after unsuccessfully using fidopoll killbusy I tried nodespy. This
worked, although in the process I discovered it had blacklisted my IP. After whitelisting it everything is working fine again :)

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Sloane BBS (21:4/112)