Hello There,

I think this was once discussed but don't recall specifics.

I have a new Fido downlink that runs Mystic A35. He recently switched Mystic over from W32 version to Linux (Debian) version. Now he has the following issue.

In his words:

"./mutil import.ini (and i'm making a mutil.ini since i have to check all these
paths) has been saying 'Cannot import. Some nodes are BUSY" then WORKING.. then FATAL because it won't import.

This happens when no one is using a node."

I recall some discussion about ghost nodes and/or undeleted .bsy files. I already explained to him the need to check for stale undeleted .bsy files.

Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128)

On 11/10/17, Jeff Smith pondered and said...

"./mutil import.ini (and i'm making a mutil.ini since i have to check
all these paths) has been saying 'Cannot import. Some nodes are BUSY" then WORKING.. then FATAL because it won't import.

Fidopoll killbusy all

That will sort it :)

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

I recall some discussion about ghost nodes and/or undeleted .bsy files.
I already explained to him the need to check for stale undeleted .bsy files.

If he used kill -9 or CTRL+Z or anything to stop a process incorrectly, it will leave all of the BSY files intact. They cannot be managed when the software is abruptly shutdown. This is the primary cause of that issue.

Usually running "fidopoll killbusy all" when nothing is running will clean up the BSY files.

--- Mystic BBS v1.12 A36 2017/11/10 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)