TID: Mystic BBS 1.12 A49
MSGID: 1:106/1 e56e88b5
TZUTC: -0500
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)
SEEN-BY: 1/123 15/0 19/38 50 90/1 105/81 106/1 201 987 123/131 124/5014
SEEN-BY: 124/5016 129/305 130/330 153/7715 218/700 226/30 227/114
SEEN-BY: 229/110 112 113 206 275 307 317 400 426 428 452 470 550 664
SEEN-BY: 229/700 266/512 280/464 282/1038 291/111 292/854 317/3 320/219
SEEN-BY: 322/757 342/200 387/21 25 26 396/45 460/58 633/280 712/848
SEEN-BY: 5075/35
PATH: 106/1 396/45 229/426