Hey All! Sorry I have been MIA all this month -- work has been crazy busy so
I have not had much chance to keep up with the BBS scene.

On top of that there seems to be some issue with running message import processes via Mystic.

I keep getting the following error for both "Toss FDN/TIC Files" and
"Importing Echomail" processes, it keeps saying:

"Waiting for Busy nodes" and sits there until it times out and ends up with "Cannot import. Some nodes are BUSY"

I tried both of the following to try and get it out busy node status but they did not seem to work:

sudo rm /mystic/semaphore/mutil.bsy
rm /mystic/semaphore/nodeinfo.now

Any suggestions or advice would be greatly appreciated as right now I am no longer able to process messages for Mystic Island BBS.

Hope everyone is doing well and will try and catch up with you all again once
I can get this issue sorted =)

-LockeDown

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)

Any suggestions or advice would be greatly appreciated as right now I am no longer able to process messages for Mystic Island BBS.

Clear out all of the .bsy and .csy files from all of your outbound folders (outbound, outbound.04d for scinet, etc...).

|15frank |08// |15netsurge
|07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://diskshop.ca/scinet

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)

On 23 Aug 2019, Netsurge said the following...

Any suggestions or advice would be greatly appreciated as right now I no longer able to process messages for Mystic Island BBS.

Clear out all of the .bsy and .csy files from all of your outbound
folders (outbound, outbound.04d for scinet, etc...).

Looks like I am working again! So odd -- All I did was the fidopoll KILLBUSY ALL and it works again :/

I swear I tried that already when I first noticed this issue a week or so
back but least it seems to be working again.

Thanks Frank!

---
|15LockeDown |08(Mickey Frklic) |08[|10mystic|09island|08.|07strangled|08.|07net|08]

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Mystic Island BBS [mysticisland.strangled.net] (21:2/148)

Looks like I am working again! So odd -- All I did was the fidopoll KILLBUSY ALL and it works again :/

I swear I tried that already when I first noticed this issue a week or so back but least it seems to be working again.

Thanks Frank!

No worries. James should implement a kill old busy option like binkd has, if the file is older than X, automatically delete it.

|15frank |08// |15netsurge
|07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://diskshop.ca/scinet

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)

On 22 Aug 2019 at 10:57p, LockeDown pondered and said...

Looks like I am working again! So odd -- All I did was the fidopoll KILLBUSY ALL and it works again :/

Yep that's the best command to use to solve the issue - and it did :)

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 08-23-19 00:20, LockeDown wrote to All <=-

I tried both of the following to try and get it out busy node status
but they did not seem to work:

sudo rm /mystic/semaphore/mutil.bsy
rm /mystic/semaphore/nodeinfo.now

try:

cd /mystic
./fidopoll killbusy


... ...and we had to chisel taglines into the walls of the cave.
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)