So just all of the sudden, out of the blue, I am now seeing this error on the Status Screen: Resetting ghost node: 1 (Inactive client slot).

This is really weird since I haven't changed or messed with anything other than adding some file bases and such.

Anyone else seen this?

-Scuz(TX!)

--- Mystic BBS v1.12 A48 (Windows/32)
* Origin: |08He|04X|08eD|07 - Mystic - | hexedbbs.com:1337 (21:1/248)

On 30 Mar 2025, Scuz said the following...

So just all of the sudden, out of the blue, I am now seeing this error
on the Status Screen: Resetting ghost node: 1 (Inactive client slot).

This is really weird since I haven't changed or messed with anything
other than adding some file bases and such.

Anyone else seen this?

These notes are from when I had strange issues with one of my nodes:

When there's a "locked" node that you can't log into, try these fixes:

1. Run Nodespy and try deleting the node there. Press enter on the offending
node number and an option menu will pop up.

2. Make sure there are NO other "mis" instances running in the background.

3. Without being logged in, check for any "chat??.dat" files that correspond to the offending node.

I had "node 1" that I couldn't log into despite trying to clear it by numbers 1 or 2 for over one month. Number 3 took care of it immediately. By deleting \mystic\data\chat1.dat, I was able to immediately log in and was on node1.

One of these may take care of it. Please respond and let us know what took care of it so I can add to my notes!

|11ogg
|11SysOp, Altair IV BBS
|11altairiv.ddns.net:2323

... Diplomacy is saying 'Nice Doggy' until you find a rock.

--- Mystic BBS v1.12 A49 2024/05/29 (Windows/64)
* Origin: Altair IV BBS (21:2/147)

So just all of the sudden, out of the blue, I am now seeing this error on Status Screen: Resetting ghost node: 1 (Inactive client slot).

This is really weird since I haven't changed or messed with anything other adding some file bases and such.

Anyone else seen this?

Yeah, I get these all the time. As far as I know its some bot connection which hangs on the detecting terminal type.

oP!

... Anything not nailed down is a cat toy...

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: TheForze - bbs.theforze.eu:23 (21:3/126)

One of these may take care of it. Please respond and let us know what took care of it so I can add to my notes!

Thanks for the information. I had checked all of the mentioned, but unfortunatly I'm still getting the error. It may have something to do with that lightning strike the other day. I noticed that I also cannot access shares from Mystic on my server. Drives are mapped and working find, but Mystic just will not recognize them now. Also that error, from the logs says that it does not have access to the \data directory. Which it does, so something has gotten corrupted and i will see what i can find after work tonight.

-Scuz(TX!)

--- Mystic BBS v1.12 A48 (Windows/32)
* Origin: |08He|04X|08eD|07 - Mystic - | hexedbbs.com:1337 (21:1/248)