I just noticed that when I try to connect to the Mystic BBS via telnet, I am unable to connect. In the term program, either SyncTerm, Nodespy, or Windows telnet, the screen will be blank until it times out. If I open the node windows, and hit Alt-V, it is showing the logon screen.

I'm not sure if this will help or not, but here is a snipet from my SyncTerm log file:

---------------
Jan 11 03:19:10 Log opened
Telnet Info RX: WILL Echo
Telnet Info TX: DO Echo
Telnet Info RX: WILL Suppress Go Ahead
Telnet Info TX: DO Suppress Go Ahead
Telnet Info RX: DO Terminal Type
Telnet Info TX: WILL Terminal Type
Telnet Info RX: DO Binary Transmission
Telnet Info TX: WILL Binary Transmission
Jan 11 03:21:35 Log closed
---------------

Mystic logs don't help much either:

----------------------------------------
Jan 11 2017 02:35 Connect from 67.61.69.56 (67-61-69-56.cpe.cableone.net)
Jan 11 2017 02:40 Inactivity timeout 9636 9336
Jan 11 2017 02:40 Normal Exit (0)
----------------------------------------

Any idea as to why this is happening? I'm not sure if I set something up
wrong or what.

Thanks in advance.


Dan Richter
aka Black Panther
Sysop - Castle Rock BBS

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Castle Rock BBS - Rio Rancho, NM (21:1/186)

On 01/11/17, Black Panther said the following...

I just noticed that when I try to connect to the Mystic BBS via telnet,
I am unable to connect. In the term program, either SyncTerm, Nodespy,
or Windows telnet, the screen will be blank until it times out. If I
open the node windows, and hit Alt-V, it is showing the logon screen.

I'm not sure if this will help or not, but here is a snipet from my SyncTerm log file:

Have you closed mis and relaunched to see if it corrects the issue?

+- $s.s$s.s$ ----------------------------------------+
| $ý"$$$"ý$ twinklebbs.homeip.net |
| .$$$. winkle BBS twinklebbs.homeip.net:8080 |
+-- .$$$$$. -----------------------------------------+
$ý"~"ý$ Christopher Malo aka Pequito!

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Twinkle BBS (21:1/126)

On 01/11/17, Black Panther said the following...

I just noticed that when I try to connect to the Mystic BBS via telnet,
I am unable to connect. In the term program, either SyncTerm, Nodespy,
or Windows telnet, the screen will be blank until it times out. If I
open the node windows, and hit Alt-V, it is showing the logon screen.

I tried it too at port 23:

Escape sequence is CTRL+].
Connecting to castlero.synchro.net port 23.
Connected.

and it just sits there. I suspect mis is hung, please try a restart of mis. There's a chance you'll get this message even when telnet is down as binkp is it's own server. I think it's ESC in the shell running mis for Windows. If
you used a batch file loop it should restart itself at that point. Something the BOTs have been doing lately is causing hangs even in Linux sometimes. Generally Linux just slows down some rather than a total hang. Windows seems
to hang.

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

On 01/11/17, Black Panther said the following...

I just noticed that when I try to connect to the Mystic BBS via telnet,
I am unable to connect. In the term program, either SyncTerm, Nodespy,
or Windows telnet, the screen will be blank until it times out. If I
open the node windows, and hit Alt-V, it is showing the logon screen.

I'm not sure if this will help or not, but here is a snipet from my SyncTerm log file:

---------------
Jan 11 03:19:10 Log opened
Telnet Info RX: WILL Echo
Telnet Info TX: DO Echo
Telnet Info RX: WILL Suppress Go Ahead
Telnet Info TX: DO Suppress Go Ahead
Telnet Info RX: DO Terminal Type
Telnet Info TX: WILL Terminal Type
Telnet Info RX: DO Binary Transmission
Telnet Info TX: WILL Binary Transmission
Jan 11 03:21:35 Log closed
---------------

Mystic logs don't help much either:

----------------------------------------
Jan 11 2017 02:35 Connect from 67.61.69.56 (67-61-69-56.cpe.cableone.net) Jan 11 2017 02:40 Inactivity timeout 9636 9336
Jan 11 2017 02:40 Normal Exit (0)
----------------------------------------

Any idea as to why this is happening? I'm not sure if I set something up wrong or what.

Thanks in advance.

Personally, I would shut down MIS or MIS2 (whichever you run) and restart it. You may need to clear all the semaphore flags tho.

"No matter where you go, there you are!" - Buckaroo Bonzai

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX (21:1/120)

On 01/11/17, Pequito said the following...

I just noticed that when I try to connect to the Mystic BBS via telne I am unable to connect. In the term program, either SyncTerm, Nodespy or Windows telnet, the screen will be blank until it times out. If I open the node windows, and hit Alt-V, it is showing the logon screen.

Have you closed mis and relaunched to see if it corrects the issue?

Yes, I've restarted it quite a few times. I've even tried using MIS2 for telnet, and it does the same thing.


Dan Richter
aka Black Panther
Sysop - Castle Rock BBS

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Castle Rock BBS - Rio Rancho, NM (21:1/186)

On 01/11/17, bcw142 said the following...

I just noticed that when I try to connect to the Mystic BBS via telne I am unable to connect. In the term program, either SyncTerm, Nodespy or Windows telnet, the screen will be blank until it times out. If I open the node windows, and hit Alt-V, it is showing the logon screen.

and it just sits there. I suspect mis is hung, please try a restart of mis. There's a chance you'll get this message even when telnet is down
as binkp is it's own server. I think it's ESC in the shell running mis

I've restarted MIS multiple times, and even tried MIS2 for telnet, with the same results. The binkp server is working fine.

for Windows. If you used a batch file loop it should restart itself at

As of right now, I'm not using any batch files to run it. I didn't have any problems when running Mystic under linux.

that point. Something the BOTs have been doing lately is causing hangs even in Linux sometimes. Generally Linux just slows down some rather
than a total hang. Windows seems to hang.

I've noticed there are a lot of bots hitting the port, but they are only
tying up the node for a short time. Usually there are less than three nodes busy at any given time.

Thanks,


Dan Richter
aka Black Panther
Sysop - Castle Rock BBS

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Castle Rock BBS - Rio Rancho, NM (21:1/186)

On 01/11/17, Gryphon said the following...

I just noticed that when I try to connect to the Mystic BBS via telne I am unable to connect. In the term program, either SyncTerm, Nodespy or Windows telnet, the screen will be blank until it times out. If I open the node windows, and hit Alt-V, it is showing the logon screen.

Personally, I would shut down MIS or MIS2 (whichever you run) and
restart it. You may need to clear all the semaphore flags tho.

I've tried that multiple times. I even tried MIS2 to see if that made a difference and it didn't. The only semaphore file in the directory is nodeinfo.now, but I've run fidopoll killbusy to clear any others.


Dan Richter
aka Black Panther
Sysop - Castle Rock BBS

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Castle Rock BBS - Rio Rancho, NM (21:1/186)

I just noticed that when I try to connect to the Mystic BBS via telnet,
I am unable to connect. In the term program, either SyncTerm, Nodespy,
or Windows telnet, the screen will be blank until it times out. If I
open the node windows, and hit Alt-V, it is showing the logon screen.

After shutting down MIS today, I noticed I'm getting the following error
during "Shutting down servers: TELNET"

Runtime error 216 at $000000010000FFD6
Runtime error 216 at $000000010000FFD6
$0000000010000FFD6

I don't know if this is related to the telnet issue or not, but I thought I'd put it out there.

Thanks,


Dan Richter
aka Black Panther
Sysop - Castle Rock BBS

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Castle Rock BBS - Rio Rancho, NM (21:1/186)

On 01/11/17, Black Panther said the following...

On 01/11/17, Pequito said the following...

I just noticed that when I try to connect to the Mystic BBS via I am unable to connect. In the term program, either SyncTerm, No or Windows telnet, the screen will be blank until it times out. open the node windows, and hit Alt-V, it is showing the logon sc

Have you closed mis and relaunched to see if it corrects the issue?

Yes, I've restarted it quite a few times. I've even tried using MIS2 for telnet, and it does the same thing.

Question if you run it outside daemon mode and show the screen does it show
the port getting locked and used by mis or unable to secure the port already
in use? If this is the case might want to check what other apps are using
the port or snagged it when mis crashed.

Also you might wanna close mis and make sure all bsy files are removed from \mystic\semaphore.

Possible just reboot the machine and see if the port clears if this is the
case or see if you can free it up from the app that has taken it.

Cheers!
Pequito

+- $s.s$s.s$ ----------------------------------------+
| $ý"$$$"ý$ twinklebbs.homeip.net |
| .$$$. winkle BBS twinklebbs.homeip.net:8080 |
+-- .$$$$$. -----------------------------------------+
$ý"~"ý$ Christopher Malo aka Pequito!

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Twinkle BBS (21:1/126)

On 01/11/17, Pequito said the following...

Question if you run it outside daemon mode and show the screen does it show the port getting locked and used by mis or unable to secure the
port already in use? If this is the case might want to check what other apps are using the port or snagged it when mis crashed.

Also you might wanna close mis and make sure all bsy files are removed from \mystic\semaphore.

It is showing that it's it's locking the port. I was checking that as well.

Possible just reboot the machine and see if the port clears if this is
the case or see if you can free it up from the app that has taken it.

After rebooting, I still had the issue. I was playing around in the modem
with unlocking ports, and it still wasn't working. I then noticed that you
were logging into the board, so I must have done something to get it working right. I'm just not sure what it was... :)

Thanks,


Dan Richter
aka Black Panther
Sysop - Castle Rock BBS

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Castle Rock BBS - Rio Rancho, NM (21:1/186)

On 01/11/17, Black Panther said the following...

On 01/11/17, Pequito said the following...

Question if you run it outside daemon mode and show the screen does i show the port getting locked and used by mis or unable to secure the port already in use? If this is the case might want to check what ot apps are using the port or snagged it when mis crashed.

Also you might wanna close mis and make sure all bsy files are remove from \mystic\semaphore.

It is showing that it's it's locking the port. I was checking that as well.

Yeah had that happen before when using windows and once while using nix.

Possible just reboot the machine and see if the port clears if this i the case or see if you can free it up from the app that has taken it.

After rebooting, I still had the issue. I was playing around in the modem with unlocking ports, and it still wasn't working. I then noticed that
you were logging into the board, so I must have done something to get it working right. I'm just not sure what it was... :)

Thanks,

Yep I created a new account. I see you kind of started over so created the account, let me know if you want or need some help setting up MRC. =)

Cheers!
Pequito

+- $s.s$s.s$ ----------------------------------------+
| $ý"$$$"ý$ twinklebbs.homeip.net |
| .$$$. winkle BBS twinklebbs.homeip.net:8080 |
+-- .$$$$$. -----------------------------------------+
$ý"~"ý$ Christopher Malo aka Pequito!

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Twinkle BBS (21:1/126)

On 01/11/17, Black Panther said the following...

On 01/11/17, Gryphon said the following...

I just noticed that when I try to connect to the Mystic BBS via I am unable to connect. In the term program, either SyncTerm, No or Windows telnet, the screen will be blank until it times out. open the node windows, and hit Alt-V, it is showing the logon sc

Personally, I would shut down MIS or MIS2 (whichever you run) and restart it. You may need to clear all the semaphore flags tho.

I've tried that multiple times. I even tried MIS2 to see if that made a difference and it didn't. The only semaphore file in the directory is nodeinfo.now, but I've run fidopoll killbusy to clear any others.

Are you trying to connect from the same box that runs the BBS? Are there
maybe some firewall issues?

"No matter where you go, there you are!" - Buckaroo Bonzai

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX (21:1/120)

On 01/12/17, Gryphon said the following...

I've tried that multiple times. I even tried MIS2 to see if that made difference and it didn't. The only semaphore file in the directory is nodeinfo.now, but I've run fidopoll killbusy to clear any others.

Are you trying to connect from the same box that runs the BBS? Are there maybe some firewall issues?

Turns out, Windows was blocking the ports. I needed to convince it to let me take care of those ports. Took awhile, but it finally agreed. :)

Thanks,


Dan Richter
aka Black Panther
Sysop - Castle Rock BBS

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Castle Rock BBS - Rio Rancho, NM (21:1/186)