g00r00, or anyone who may be able to help:

I'm still trying to find a way to log in on 2 nodes at once.

g00r00 reminded me to set the ACS level for multiple logins in the login settings, something I totally missed, but I set it to u1 (that's me) and I still can't get the 2nd login to happen - this might be due to some non-Mystic circumstance, but I'm not sure.

I log in to Mystic on a node with Netrunner (Linux Mystic Linux Netrunner) and then I try to log in with a 2nd instance of Netrunner, and the Netrunner terminal says "BUSY" in the top left corner then automatically disconnects.

I'm sure this is due to some error on my part - and I'm checking things, but I'll take any other tips anyone may have for this.

Thanks.

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

On 25 Mar 2020 at 02:13p, Aaron Thomas pondered and said...

g00r00, or anyone who may be able to help:

I'm still trying to find a way to log in on 2 nodes at once.

Hi Aaron.

I'd also check your Telnet server setting, and have a look at the DUPE IP Limit. There you may want to increase that and/or just set it to 0 to
disable. I suspect that may do the trick :)

Best, Paul

--- Mystic BBS v1.12 A46 2020/03/18 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

g00r00, or anyone who may be able to help:

I'm still trying to find a way to log in on 2 nodes at once.

g00r00 reminded me to set the ACS level for multiple logins in the login settings, something I totally missed, but I set it to u1 (that's me) and
I still can't get the 2nd login to happen - this might be due to some non-Mystic circumstance, but I'm not sure.

I log in to Mystic on a node with Netrunner (Linux Mystic Linux
Netrunner) and then I try to log in with a 2nd instance of Netrunner,
and the Netrunner terminal says "BUSY" in the top left corner then automatically disconnects.

One thing to check would be your Server Options > Max BBS Nodes

--- Mystic BBS v1.12 A46 2020/03/22 (Windows/64)
* Origin: Sector 7 (1:129/215)

I'd also check your Telnet server setting, and have a look at the DUPE IP Limit. There you may want to increase that and/or just set it to 0 to

Thanks Paul. I did try with it set to 5, and I tried with it set to 0,
but it's still giving me the "BUSY" message in the top left corner of the screen.

Do you happen to know where the "BUSY" message is coming from? Does that sound like Mystic, Netrunner, or a message from my server?

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

One thing to check would be your Server Options > Max BBS Nodes

Thank you. I have it set to 3, which seems like enough, but I will try increasing it.

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

Do you happen to know where the "BUSY" message is coming from? Does that sound like Mystic, Netrunner, or a message from my server?

I get that in mystic sometimes

Rick

--- Mystic BBS v1.12 A46 2020/03/22 (Windows/32)
* Origin: Abacus BBS (1:340/202)

One thing to check would be your Server Options > Max BBS Nodes

Thank you. I have it set to 3, which seems like enough, but I will try increasing it.

Ok next step I would suggest is restarting your computer (this is of course optional, but sometimes turning it off and on again helps!)

But then with the BBS offline carefully delete "chat*.dat" from your DATA folder. Sometimes that data can get stuck there if there is a crash or a shutdown for some reason. For example, since I moved my BBS to my laptop I sometimes shutdown or crash my OS (thanks to latest Win 10 update) which will sometimes leave an old chat*.dat file that needs to be removed.

Basically that file flags a node as in-use.

--- Mystic BBS v1.12 A46 2020/03/22 (Windows/64)
* Origin: Sector 7 (1:129/215)

One thing to check would be your Server Options > Max BBS Nodes

Thank you. I have it set to 3, which seems like enough, but I will try increasing it.

Sorry I forgot in the other message but another situation when BUSY can be an issue is in Linux when you don't have your file access rights correct so
Mystic cannot access the data to work.

--- Mystic BBS v1.12 A46 2020/03/22 (Windows/64)
* Origin: Sector 7 (1:129/215)

But then with the BBS offline carefully delete "chat*.dat" from your DATA folder. Sometimes that data can get stuck there if there is a crash or a

Thank you!

That just solved both of my issues. 1) I'm able to log in on more than 1 node now and 2) I'm logged in on the 1st available node now.

Awesome!

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

Thank you!

That just solved both of my issues. 1) I'm able to log in on more than 1 node now and 2) I'm logged in on the 1st available node now.

I figured it might be an issue where a node was stuck and it was "you" online which would have caused both of those issues! Great to hear!

--- Mystic BBS v1.12 A46 2020/03/26 (Windows/64)
* Origin: Sector 7 (1:129/215)