For the last few weeks, when I get logged in on my bbs, I get sent to
node 2 instead of node 1. I noticed it by reviewing my log files and
noticed that I had a log entry for node2 instead of the normal node1.
This happened quite a few weeks after upgrading to Mystic A1.12 A49
compiled 2023/04/30 on win 11 x64. This happens with no one else logged in.
If someone logs in while I'm on, the log shows node3 for them.

While I'm logged in, when I check for who's on, it shows node 1 "waiting for call" with me logged on node 2. If I do a "mystic -N1 -L", I get a "BUSY" result. (I know I'm not supposed to do that but...)

In trying to determine what's going on, I looked at:
1. Ran multiple "mis poll killbusy all" with no change.
2. Were there any duplicate mis entries? NO
3. Was there anything running on node 1? NOT THAT I COULD FIND.
4. I did shutdown mis multiple times with no change.
5. I reconfigured the number of nodes, both total and each server.
6. I've been all over the wiki with no luck.

Since it happened well after the upgrade, I don't think it was the upgrade.
I must have done something to create the issue, I'm just out of ideas. Can anyone offer any suggestions for me to check out?

Thanks for any help!

ogg
Sysop, Altair IV BBS
altairiv.ddns.net:2323

... I am NOT a tagline THIEF. I am a tagline CONSERVATIONIST.

--- Mystic BBS v1.12 A49 2023/04/30 (Windows/64)
* Origin: Altair IV BBS (1:106/1)

On 14 Jul 2023, ogg said the following...

For the last few weeks, when I get logged in on my bbs, I get sent to node 2 instead of node 1.

While I'm logged in, when I check for who's on, it shows node 1 "waiting for call" with me logged on node 2. If I do a "mystic -N1 -L", I get a "BUSY" result.

Try shutting down MIS and then deleting the file nodeinfo.now from the mystic\semaphore directory.


Jay

... Police were called to a daycare centre where a child was resisting a rest

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Northern Realms (1:229/664)

Try shutting down MIS and then deleting the file nodeinfo.now from the mystic\semaphore directory.

Jay

Should have mentioned that in the original post I did that as well. Thanks for the input!

ogg
Sysop, Altair IV BBS
altairiv.ddns.net:2323

... When all else fails, read the instructions

--- Mystic BBS v1.12 A49 2023/04/30 (Windows/64)
* Origin: Altair IV BBS (1:106/1)

On Fri, 14 Jul 2023 22:00:03 +1300, ogg wrote:

Since it happened well after the upgrade, I don't think it was the
upgrade. I must have done something to create the issue, I'm just out of ideas. Can anyone offer any suggestions for me to check out?

Hi there.

Run nodespy and try killing the ghost node. That should remove it.

--
Agency News | news.bbs.nz

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Run nodespy and try killing the ghost node. That should remove it.

--
Agency News | news.bbs.nz

Thanks Avon!

I ran nodespy and none of the 4 nodes were in use so no kill ghost node
option was available.

Additional info, when I run the /W (who's online), I see that I'm on node 2 with nobody on the others. I'm thinking of downgrading to A48 and seeing if the issue goes away.

I'll keep trying!

ogg
Sysop, Altair IV BBS
altairiv.ddns.net:2323

... Kids: They're not sleeping, they're recharging!

--- Mystic BBS v1.12 A49 2023/04/30 (Windows/64)
* Origin: Altair IV BBS (1:106/1)

Hello ogg,

On Sun Jul 16 2023 18:27:34, you wrote to Kerr Avon:

I ran nodespy and none of the 4 nodes were in use so no kill ghost
node option was available.

Additional info, when I run the /W (who's online), I see that I'm on
node 2 with nobody on the others. I'm thinking of downgrading to A48
and seeing if the issue goes away.

I'll keep trying!

FYI, I just tested this on my Mystic install, and I'm currently sitting on the node screen seeing myself logged into node 1. I'm currently using: Mystic BBS v1.12 A49 Linux/64 Compiled 2023/03/14 06:42:21.

Then I noticed you were using a newer version, so I upgraded to the latest: Mystic BBS v1.12 A49 Linux/64 Compiled 2023/04/30 11:57:00, and I get the same results. However, I see you're using the Windows 64bit version, so that's the only clear difference I see.

Before any questions, I telnetted over, and noticed your bot checker; after you hit escape twice, it says: "Detecting terminal emulation: |!botcheck1_2 TE detected." = I'm guessing there's a couple typos there, as it seems you're trying to run something called "botcheck1_2", but using the wrong pipe code or missing something there, and you need a pipe before TE in order for that second pipe code to actually work. Just with that one line, I'm going to take a wild stab at you may have a typo somewhere that's causing this. :)

Bear with me, I haven't run Mystic on Windows in over a decade..

How are you running the server (ie: what command line are you using)?

Do you have any events (see event editor) setup to run on node 1? If so, you may want to try changing those to your highest node number.. and don't forget to restart the mystic server after any changes.

Do you have a local login ("mystic -l" or something similar) running in the background? Could take a look at your task manager and see if anything odd is running besides one instance of the mystic server itself.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20230205
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hello ogg,

On Sun Jul 16 2023 18:27:34, you wrote to Kerr Avon:

I ran nodespy and none of the 4 nodes were in use so no kill ghost node option was available.

Additional info, when I run the /W (who's online), I see that I'm on node 2 with nobody on the others. I'm thinking of downgrading to A48 and seeing if the issue goes away.

I'll keep trying!

FYI, I just tested this on my Mystic install, and I'm currently sitting
on the node screen seeing myself logged into node 1. I'm currently
using: Mystic BBS v1.12 A49 Linux/64 Compiled 2023/03/14 06:42:21.

Then I noticed you were using a newer version, so I upgraded to the latest: Mystic BBS v1.12 A49 Linux/64 Compiled 2023/04/30 11:57:00, and
I get the same results. However, I see you're using the Windows 64bit version, so that's the only clear difference I see.

Before any questions, I telnetted over, and noticed your bot checker; after you hit escape twice, it says: "Detecting terminal emulation: |!botcheck1_2 TE detected." = I'm guessing there's a couple typos there, as it seems you're trying to run something called "botcheck1_2", but
using the wrong pipe code or missing something there, and you need a
pipe before TE in order for that second pipe code to actually work. Just with that one line, I'm going to take a wild stab at you may have a typo somewhere that's causing this. :)

The botcheck is an addon (smooth@phenomprod.com) that I've installed, not written. I'll get into the code and see what I can see, but thanks for the note!

Bear with me, I haven't run Mystic on Windows in over a decade..

How are you running the server (ie: what command line are you using)?

I'm using the "mis server" command. Nothing special.

Do you have any events (see event editor) setup to run on node 1? If so, you may want to try changing those to your highest node number.. and
don't forget to restart the mystic server after any changes.

No events that would specifically call out node 1.

Do you have a local login ("mystic -l" or something similar) running in the background? Could take a look at your task manager and see if
anything odd is running besides one instance of the mystic server itself.

I've been over all of the running services and nothing sticks out. As a side note, I did install Mystic on a laptop running Ubuntu just to check things
out. It ran fine with logins starting with node 1. As soon as I moved the screen, data and other files over from the windows board, I got the same node
2 issues. I suspect that the issue is with one of the "configuration" files having either some sort of corruption (maybe my creation?) or configuration issue. I just need to figure out which one.

Regards,
Nick

Thanks for the suggestions! I do appreciate it.

Scott

... It said "insert disk #3", but only two will fit...

--- Mystic BBS v1.12 A49 2023/04/30 (Windows/64)
* Origin: Altair IV BBS (1:106/1)

Hello ogg,

On Wed Jul 19 2023 10:25:04, you wrote to me:

I've been over all of the running services and nothing sticks out. As
a side note, I did install Mystic on a laptop running Ubuntu just to
check things out. It ran fine with logins starting with node 1. As
soon as I moved the screen, data and other files over from the windows board, I got the same node 2 issues. I suspect that the issue is with
one of the "configuration" files having either some sort of corruption (maybe my creation?) or configuration issue. I just need to figure
out which one.

A good place to look for that would be your mystic/data directory. I just watched my data directory, and logged in to node 1, and the only file that was created was 'chat1.dat', so if you have that file in your data directory while NOT logged into your BBS.. it's safe to try to delete that file and see if that helps.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20230205
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

A good place to look for that would be your mystic/data directory. I just watched my data directory, and logged in to node 1, and the only file
that was created was 'chat1.dat', so if you have that file in your data directory while NOT logged into your BBS.. it's safe to try to delete
that file and see if that helps.

Regards,
Nick

That did it!!!! Thank you, thank you!

I hate when I can't figure out a problem. Another one off my list!

Scott

... A penny saved is not very much

--- Mystic BBS v1.12 A49 2023/04/30 (Windows/64)
* Origin: Altair IV BBS (1:106/1)