Hi G00r00,

I am trying to start "mystic.exe -cfg" and it just displays BUSY then exits. I tried bringing everything down, killing mis2.bsy, same thing. Works fine under linux/64 just Win32 is doing it. Just for fun I tried "fidopoll killbusy", same. Help!


.- Keep the faith, --------------------------------------------------.
| |
| Ben aka cMech Web: http|ftp|binkp|telnet://cmech.dynip.com |
| Email: fido4cmech(at)lusfiber.net |
| Home page: http://cmech.dynip.com/homepage/ | `----------- WildCat! Board 24/7 +1-337-984-4794 any BAUD 8,N,1 ---'

... Make friends with SysOps: Page them at 3am.
--- GoldED+/LNX v1.1.5-b20170303 ... via Mystic BBS!
* Origin: FSXNet - Positronium #2: telnet://cmech.dynip.com:2323 (21:2/120)

I am trying to start "mystic.exe -cfg" and it just displays BUSY then exits. I tried bringing everything down, killing mis2.bsy, same thing. Works fine under linux/64 just Win32 is doing it. Just for fun I tried "fidopoll killbusy", same. Help!

Load nodespy, press enter on the node and select "remove ghost user"

or delete chat*.dat in your DATA directory.

If you are using the "X" on the window to shut down Mystic, that can create problems where Mystic still thinks a user is logged in.

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

* An ongoing debate between g00r00 and Cmech rages on ...

I am trying to start "mystic.exe -cfg" and it just displays BUSY

Load nodespy, press enter on the node and select "remove ghost user"
or delete chat*.dat in your DATA directory.

All 8 lines showed "Logging In" but I killed the ghost user on each and good to

go, thanks!

If you are using the "X" on the window to shut down Mystic, that can create problems where Mystic still thinks a user is logged in.

I do not :)


.- Keep the faith, --------------------------------------------------.
| |
| Ben aka cMech Web: http|ftp|binkp|telnet://cmech.dynip.com |
| Email: fido4cmech(at)lusfiber.net |
| Home page: http://cmech.dynip.com/homepage/ | `----------- WildCat! Board 24/7 +1-337-984-4794 any BAUD 8,N,1 ---'

... We dump Silverfoot, and we get SON of Silverfoot...Only in TEXAS!!! ;*)
--- GoldED+/LNX v1.1.5-b20170303 ... via Mystic BBS!
* Origin: FSXNet - Positronium #2: telnet://cmech.dynip.com:2323 (21:2/120)

On 06/25/17, Cmech pondered and said...

Hi G00r00,

I am trying to start "mystic.exe -cfg" and it just displays BUSY then exits. I tried bringing everything down, killing mis2.bsy, same thing. Works fine under linux/64 just Win32 is doing it. Just for fun I tried "fidopoll killbusy", same. Help!

Check your now auto blocked in badip.txt
Otherwise this message looks like all nodes are active and there is no free port to connect to.

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

* An ongoing debate between Avon and Cmech rages on ...

I am trying to start "mystic.exe -cfg" and it just displays BUSY

Otherwise this message looks like all nodes are active and there is no free port to connect to.

Yes they were all "Logging In" so I killed all the ghosts and now back up :) Telnet on MIS2 ...


.- Keep the faith, --------------------------------------------------.
| |
| Ben aka cMech Web: http|ftp|binkp|telnet://cmech.dynip.com |
| Email: fido4cmech(at)lusfiber.net |
| Home page: http://cmech.dynip.com/homepage/ | `----------- WildCat! Board 24/7 +1-337-984-4794 any BAUD 8,N,1 ---'

... La Quinta - Spanish term meaning "Motel next to a Denny's".
--- GoldED+/LNX v1.1.5-b20170303 ... via Mystic BBS!
* Origin: FSXNet - Positronium #2: telnet://cmech.dynip.com:2323 (21:2/120)

If you are using the "X" on the window to shut down Mystic, that can create problems where Mystic still thinks a user is logged in.

I do not :)

Okay thanks let me know if it happens again.

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

g00r00 wrote to Cmech <=-

Okay thanks let me know if it happens again.

I didn't read all this thread, but I was having similar issues with A34
on the Pi. I've since downgraded back to A33 (I think? see below :> ) I
didn't have the time to look into it more, so reverting back was the
best option for me at the time.

I copied the new exe's and all was fine, I was able to telnet in fine.
Later I tried to telnet in and could not connect. Nodespy said all
nodes were logging in. So I killed the ghosts and started it back up.
Later I tried to telnet in again and could not connect. Same deal,
nodespy showed all nodes logging in. After killing ghosts and did
notice that it said it could not bind 0.0.0.0/23 or something similar.
I think I had to reboot the pi once or twice because just killing the
ghosts didn't clear the issue.

After this happened a few times, I put A33 back and haven't had a
problem since. I'll try A35 and see if it continues. I'll have some
time over this coming long weekend, so maybe I can test more.

Kev

___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A33 (Raspberry Pi/32)
* Origin: Razor's Domain 3.141592... (21:1/162)