OK so I came home last night and check my board and after I run my bat file for
my interbbs league I notice that it won't connect to the hub saying it is
busy.

So I trying polling FSXNet and it says it is busy. Then I notice that that mutil starts to run mailin and it says it is waiting for busy nodes. So I shut down mystic, reboot the computer and same problem.

Solution: I deleted all busy semaphores from the echomail out directories and
cleaned out the semaphore directory and tried running mutil mailin. I errored out on one packet. Checked the packet (looked OK but moved it) then ran mutil mailin again and it tossed everything else that was in my echomail in directory. Started up mystic server and all was good again. So one bad packet mucked up everything.
Jeff

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/32)
* Origin: Communication Connection 77:1/170 (77:1/170)

So I trying polling FSXNet and it says it is busy. Then I notice that
that mutil starts to run mailin and it says it is waiting for busy
nodes. So I shut down mystic, reboot the computer and same problem.

If for some reason there is a crash or the computer is shutdown or the program is at all stopped while its doing something, those busy files can get stuck there. They should "expire" after some time (I think it might be 1 day or something?) but you can manually clean it up as you found!

There is an easier way than manually removing them though. You can run "mis poll killbusy" and it will automatically remove busy files for you.

I can't remember if there were any issues with the version you are running that might have led to this, but you could also try upgrading to the latest version as well if you see it happen again.

--- Mystic BBS v1.12 A47 2021/06/14 (Windows/32)
* Origin: Sector 7 | Mystic WHQ (77:1/138)

my interbbs league I notice that it won't connect to the hub saying it is busy.

So I trying polling FSXNet and it says it is busy. Then I notice that
that mutil starts to run mailin and it says it is waiting for busy
nodes. So I shut down mystic, reboot the computer and same problem

I had the same issue here, I pulled the offending pkt and after removing all bsy files and restarting mystic all incoming files were parsed.


G00R00 I saved the pkt and if you are interested in looking at it, I'll post it for you.



|08-- ()|06_.-.|07 |08-% |10Freeside BBS |08%-|15
Ratz |12.|06-|04"|06 -,_( )|08__) |02freeside|08.|02bbs|08.|02io|08:|0223|08

--- Mystic BBS v1.12 A47 2021/03/16 (Windows/32)
* Origin: Freeside BBS - freeside.bbs.io:23 (77:1/121)

here it is.

https://1drv.ms/u/s!Ao5314L44bDcha5A9SlMpjOmaR8wlw?e=GQB9ed



|08-- ()|06_.-.|07 |08-% |10Freeside BBS |08%-|15
Ratz |12.|06-|04"|06 -,_( )|08__) |02freeside|08.|02bbs|08.|02io|08:|0223|08

--- Mystic BBS v1.12 A47 2021/03/16 (Windows/32)
* Origin: Freeside BBS - freeside.bbs.io:23 (77:1/121)

If for some reason there is a crash or the computer is shutdown or the program is at all stopped while its doing something, those busy files
can get stuck there. They should "expire" after some time (I think it might be 1 day or something?) but you can manually clean it up as you found!

There is an easier way than manually removing them though. You can run "mis poll killbusy" and it will automatically remove busy files for you.

I can't remember if there were any issues with the version you are
running that might have led to this, but you could also try upgrading to the latest version as well if you see it happen again.

First thank you for all your time and effort you put into this software, I know
I and many other really appreciate it. I did have someone else tell me to upgrade as they had a similar issue with a bad packet causing the same problem and have not had the issue since upgrading. (You have already fixed the problem
and you didn't know it. ;) ) So I will be upgrading after I get back from vacation this week.
Jeff

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/32)
* Origin: Communication Connection 77:1/170 (77:1/170)

I and many other really appreciate it. I did have someone else tell me
to upgrade as they had a similar issue with a bad packet causing the
same problem and have not had the issue since upgrading. (You have already fixed the problem

Thanks for the kind words! :)

I may have fixed it but I can't remember if there was something specific I did.

The only thing I can think of is that there was a bug in the BINKD mailer that I had to make a work-around in Mystic for that
could cause some sort of lockup, and they may not have fixed that problem on their end. I may have fixed other things too but I can't say for sure!

Current version has been running very well though for me at least. That's a sign that its time to add some new stuff and break things ;)

--- Mystic BBS v1.12 A47 2021/06/18 (Windows/32)
* Origin: Sector 7 | Mystic WHQ (77:1/138)