Hi,

I am experience some random freezes (happening every 2-3 days) and leaving my SSH server unresponsive. The Telnet one works however.

When I cycle mis, I get this message upon mis exit:

An unhandled exception occurred at $0000000000413927:
EInOutError: Invalid file handle
$0000000000413927

The mis log have this line as well:

+ 2019.02.27 22:58:11 SSH Flush error Timeout Timeout during flush, no data could be written before the timeout of 5 seconds expired

Cheers!

|15 ß Þ |15StackFault |08<|03.|11.|15P|11h|03EN|11o|15M|11.|03.|08>
|11 Ý ß |11The Bottomless Abyss BBS
|03 ß Ýß |03ssh|08.|072222 |08/ |03telnet|08.|072023 |08/ |03https
|08 ÜþÞ |08bbs|07.|08bottomlessabyss|07.|08net

--- Mystic BBS v1.12 A42 2019/02/01 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (21:1/172)

The mis log have this line as well:

+ 2019.02.27 22:58:11 SSH Flush error Timeout Timeout during flush, no data could be written before the timeout of 5 seconds expired

Thanks I will take a look at it, and also enable SSH on my BBS and start
using that.

--- Mystic BBS v1.12 A43 2019/02/26 (Linux/64)
* Origin: Sector 7 (21:1/108)

I am experience some random freezes (happening every 2-3 days) and
leaving my SSH server unresponsive. The Telnet one works however.

I already found one issue where a critical section wasn't exited properly on
a flush error. I am not sure this was the problem but it seems like a good candidate.

I've fixed it up and I will try to recompile the Linux/Windows versions in an hour or two.

--- Mystic BBS v1.12 A43 2019/02/26 (Linux/64)
* Origin: Sector 7 (21:1/108)

I am experience some random freezes (happening every 2-3 days) and leaving my SSH server unresponsive. The Telnet one works however.

I already found one issue where a critical section wasn't exited
properly on a flush error. I am not sure this was the problem but it seems like a good candidate.

Excellent. It might take some time before we know if it fixed it since it
only crashes randomly. Maybe when a user does not exit cleanly or something.

|15 ß Þ |15StackFault |08<|03.|11.|15P|11h|03EN|11o|15M|11.|03.|08>
|11 Ý ß |11The Bottomless Abyss BBS
|03 ß Ýß |03ssh|08.|072222 |08/ |03telnet|08.|072023 |08/ |03https
|08 ÜþÞ |08bbs|07.|08bottomlessabyss|07.|08net

--- Mystic BBS v1.12 A42 2019/02/01 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (21:1/172)

I already found one issue where a critical section wasn't exited properly on a flush error. I am not sure this was the problem but it seems like a good candidate.

Excellent. It might take some time before we know if it fixed it since it only crashes randomly. Maybe when a user does not exit cleanly or something.

Yep that is exactly what I think it is. I suspect a user would disconnect just as the server was trying to flush data causing the flush error.

Mystic is supposed to just close the connection in that case, but the bug prevented the server from exiting a critical section, and that in turn made the SSH server thread get stuck in a locked state.

I switched my BBS over to exclusively use SSH so I will probably see it too if there are any SSH issues remaining. Its been up I think over a month now getting hammered on standard ports with no crashes, so I am counting on this being fixed... can't break the uptime streak! lol

--- Mystic BBS v1.12 A43 2019/02/27 (Linux/64)
* Origin: Sector 7 (21:1/108)