When a user hangs-up without logging out, he gets stuck in the system -
logged in constantly until the sysop uses Nodespy to terminate the user's logged-in status.

Is there a way to make these "hang-ups" self-terminate? I mean without the sysop having to use Nodespy & do it for them?

If so, please share..

But if not, is there a parameter that can be used with Nodespy, so it can be automatically added to the end of a log-in script?

So like user logs in on node1, then hangs-up without logging out,
Then, in that case, Mystic exits with error #2 (for example)
At the end of the script, if error = 2 {nodespy -terminate node1}

Does someone have something like this going on?

--- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
* Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)

When a user hangs-up without logging out, he gets stuck in the system - logged in constantly until the sysop uses Nodespy to terminate the user's logged-in status.

In my experience this doesn't happen unless a user is stuck in a door that isn't working. I think there's some sort of no-activity timeout you can set (which is on by default?) that'll automatically kick a user at some point in time.

Are users getting stuck at a specific place?

--- Mystic BBS v1.12 A44 2020/01/16 (Linux/64)
* Origin: monterey bbs (21:1/168)

Are users getting stuck at a specific place?

On my BBS, where I'm now working with the latest alpha for Linux, if I close the terminal while at the "Add Onliner?" prompt, it does it - then I have to kill the session with Nodespy. I guess the easy answer to that would be
"Don't close the terminal while at the Add Oneliner prompt!" :)

I use Alcoholiday BBS every day, and sometimes I have to hang up manually
(for various reasons) usually while reading/posting messages. When that happens, I always have to get the sysop to fix it with Nodespy.

That's why I was thinking, as a precaution, it might be convenient to automatically zap everyone with nodespy every time Mystic exits.

--- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
* Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)

On my BBS, where I'm now working with the latest alpha for Linux, if I close the terminal while at the "Add Onliner?" prompt, it does it - then
I have to kill the session with Nodespy. I guess the easy answer to that would be "Don't close the terminal while at the Add Oneliner prompt!" :)

Interesting, I'll try to repro. I don't think I've run into having stuck
nodes yet. Maybe I've been lucky?

Is your "Add Oneliner" prompt part of a door or is it the built in oneliner bits of mystic?

--- Mystic BBS v1.12 A44 2020/01/16 (Linux/64)
* Origin: monterey bbs (21:1/168)

On my BBS, where I'm now working with the latest alpha for Linux, if close the terminal while at the "Add Onliner?" prompt, it does it - t I have to kill the session with Nodespy. I guess the easy answer to t would be "Don't close the terminal while at the Add Oneliner prompt!"

I'll tell I have occassional stuck nodes, mostly when I overrun in a script
and can't kill it. I would suggest that when a node drops connection, Mystic will usually kill the ghost in due time. Might take a few, but I seem to
think this is working. So you might need to do some investrigation to
pinpoint what's causing the issue.

CAVEAT: I had a ton of stuck nodes in Windows Mystic A43. Linux is rock solid.

|19|15ÚÄ|16|07´ |08De|07ad|15be|07a|08tz b|07b|15s
|07ÀÄÙÃÄ¿ |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
|11þ |07À|19|15Ä|16|07Ù |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
|12ð|15A|07n|08al|07o|15g|12ð |08:>.|13F|05dn |131|08:|13305|08/|132|08.
|08:>.|15S|08ci |1577|08:|151|08/|15131|08.
|08:>.|11T|03qw |111337|08:|113|08/|1113|08.

--- Mystic BBS v1.12 A44 2020/01/24 (Linux/64)
* Origin: deadbeatz.org (21:2/123)

CAVEAT: I had a ton of stuck nodes in Windows Mystic A43. Linux is rock solid.

Ah, yes, I too run linux. Perhaps we aren't successfully detecting dropped carrier in other environments.

--- Mystic BBS v1.12 A44 2020/01/16 (Linux/64)
* Origin: monterey bbs (21:1/168)

CAVEAT: I had a ton of stuck nodes in Windows Mystic A43. Linux is ro solid.

Ah, yes, I too run linux. Perhaps we aren't successfully detecting
dropped carrier in other environments.

Maybe, I think he's running Linux. I was running WIndows 7/32 for a few
months until I went back to Linux.

Cheers,

|19|15ÚÄ|16|07´ |08De|07ad|15be|07a|08tz b|07b|15s
|07ÀÄÙÃÄ¿ |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
|11þ |07À|19|15Ä|16|07Ù |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
|12ð|15A|07n|08al|07o|15g|12ð |08:>.|13F|05dn |131|08:|13305|08/|132|08.
|08:>.|15S|08ci |1577|08:|151|08/|15131|08.
|08:>.|11T|03qw |111337|08:|113|08/|1113|08.

--- Mystic BBS v1.12 A44 2020/01/24 (Linux/64)
* Origin: deadbeatz.org (21:2/123)

Is your "Add Oneliner" prompt part of a door or is it the built in oneliner bits of mystic?

It's the built-in Mystic oneliners. I hadn't done anything with the fresh install other than a couple quick settings changes.

--- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
* Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)

On my BBS, where I'm now working with the latest alpha for Linux, if I close the terminal while at the "Add Onliner?" prompt, it does it - then

Are you using an MPL program for oneliners?

--- Mystic BBS v1.12 A44 2020/01/27 (Linux/64)
* Origin: Sector 7 (21:1/108)

CAVEAT: I had a ton of stuck nodes in Windows Mystic A43. Linux is rock solid.

Any idea how to reproduce that in Windows? I don't really have issues on either platform although my BBS runs on Linux so Windows is only just local testing. I do get them when I do something dumb and kill the process or something, but I don't know any other way to have it happen.

There was a problem with uploads catching dropped connections though that I recently fixed.

--- Mystic BBS v1.12 A44 2020/01/27 (Linux/64)
* Origin: Sector 7 (21:1/108)

CAVEAT: I had a ton of stuck nodes in Windows Mystic A43. Linux is ro solid.

Ah, yes, I too run linux. Perhaps we aren't successfully detecting
dropped carrier in other environments.

There was a bug with transfer protocols during upload that I recently fixed, but I think that may have even applied to Linux too. Thats the only thing I know about. Hopefully we can pinpoint the other issues if there are.

--- Mystic BBS v1.12 A44 2020/01/27 (Linux/64)
* Origin: Sector 7 (21:1/108)

Any idea how to reproduce that in Windows? I don't really have issues on either platform although my BBS runs on Linux so Windows is only just local testing. I do get them when I do something dumb and kill the process or something, but I don't know any other way to have it happen.

I still have my Windows 7 VM so I'll see if I can make it work. I had a ton
of issues with that VM. It may be a VM issue. One particular issue I had with WIndows 7 and Mystic in a VM is that the Keypressed() function would return true every time regardless if any key was pressed. If you then captured it
with char, extended = bbs.getkey() right after the keypressed(), it would
block as if no key was pressed. It's the primary reason I switched back to Linux.

I had some really weird behavior like the node1-5 logs would just fill up and the nodes would have ghosts. I bet it was due to bots connecting before I
could get up my bot killer. I couldn't get the bot killer to work in Windows due to the keypressed issue and timing out.

I asked around but the only people running keypressed() and botcheckers were all written in MPL. All my code was MPY.

Again, I'll take a look as I'm curious now.

|19|15ÚÄ|16|07´ |08De|07ad|15be|07a|08tz b|07b|15s
|07ÀÄÙÃÄ¿ |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
|11þ |07À|19|15Ä|16|07Ù |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
|12ð|15A|07n|08al|07o|15g|12ð |08:>.|13F|05dn |131|08:|13305|08/|132|08.
|08:>.|15S|08ci |1577|08:|151|08/|15131|08.
|08:>.|11T|03qw |111337|08:|113|08/|1113|08.

--- Mystic BBS v1.12 A44 2020/01/24 (Linux/64)
* Origin: deadbeatz.org (21:2/123)

On my BBS, where I'm now working with the latest alpha for Linux, if close the terminal while at the "Add Onliner?" prompt, it does it - t

Are you using an MPL program for oneliners?

No, this is the stock Mystic oneliners. This was on a very fresh install with hardly anything changed. Specifically, it's the latest alpha for Linux 64 Bit.

I did it twice to be sure I'm not extra crazy. Not a big deal but give it a
try if you get a chance.

I'm assuming that closing the terminal would cause the same reaction as a
user hanging-up - if not, then maybe it's just a local login issue.

--- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
* Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)

I'm assuming that closing the terminal would cause the same reaction as a user hanging-up - if not, then maybe it's just a local login issue.

No, its not and this is exactly why its happening.

When you force a terminal to close, it doesn't tell the applications running within it to shutdown. You are essentially forcefully killing Mystic when
you do that.

--- Mystic BBS v1.12 A44 2020/01/28 (Linux/64)
* Origin: Sector 7 (21:1/108)

I'm assuming that closing the terminal would cause the same reaction user hanging-up - if not, then maybe it's just a local login issue.

No, its not and this is exactly why its happening.

When you force a terminal to close, it doesn't tell the applications running within it to shutdown. You are essentially forcefully killing Mystic when you do that.

Hey just an update to this, I did some quick Googling and it seems like I can trap whenever you click "X" to shutdown a terminal in Linux.

Assuming that is true and I can trap that event I will make it so that Mystic does not get forcefully killed and end up with a ghost node in that case.

I'll do my testing and see if I can get a reasonable solution out for the next version!

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)

I can trap whenever you click "X" to shutdown a terminal in Linux.

I appreciate it, and that will be useful. But I was trying to expose a
similar "ghosting" issue that I've been experiencing with Alcoholiday. I use that BBS like crazy, and sometimes we have connection lag, and it gets so severe that sometimes I need to hang-up manually. In those cases, 3/4ths of
the time I get ghosted & I end up emailing Zero Reader requesting to have him kill the session for me. <- that's the bigger deal.

I'll post back with better details next time that happens - I can't remember
if it happens while reading or posting a message - but it's definitely one of those.

--- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
* Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)

cases, 3/4ths of the time I get ghosted & I end up emailing Zero Reader requesting to have him kill the session for me. <- that's the bigger
deal.

How long do you stay ghosted? What OS is Alcoholiday?

I have to admit I was playing some game on InkTwo and it locked up on me. I
had to hangup and it ghosted me for about 5 minutes but it eventually
released. I'm just curious if you are giving Mystic time to reach the inactivity timeout that the BBS has set. I assume that will be the deciding factor of whether or not you are actually connected. Now if you're in a door that might not happen.

|19|15ÚÄ|16|07´ |08De|07ad|15be|07a|08tz b|07b|15s
|07ÀÄÙÃÄ¿ |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
|11þ |07À|19|15Ä|16|07Ù |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
|12ð|15A|07n|08al|07o|15g|12ð |08:>.|13F|05dn |131|08:|13305|08/|132|08.
|08:>.|15S|08ci |1577|08:|151|08/|15131|08.
|08:>.|11T|03qw |111337|08:|113|08/|1113|08.

--- Mystic BBS v1.12 A44 2020/01/28 (Linux/64)
* Origin: deadbeatz.org (21:2/123)

I can trap whenever you click "X" to shutdown a terminal in Linux.

I appreciate it, and that will be useful. But I was trying to expose a similar "ghosting" issue that I've been experiencing with Alcoholiday. I

Unfortunately bad news. Its already is trapping that. I am able to click X
in Linux and it shuts down properly so I can't say what is going on on your side.

I did a load test of the latest build in both Windows and Linux for hours, with a minimum of 10 connections at a time up to 25 constantly connecting and dropping. I wasn't able to get a ghost node on either Windows or Linux after hours of running it.

I am using A44 though, but I don't think I had a single ghost node in the 4 months I had the BBS exposed on port 23 before I took it down for a while.

I really have no idea what could be happening.

--- Mystic BBS v1.12 A44 2020/01/29 (Linux/64)
* Origin: Sector 7 (21:1/108)

reach the inactivity timeout that the BBS has set. I assume that will be the deciding factor of whether or not you are actually connected. Now if you're in a door that might not happen.

Mystic has a watchdog process on door processes in Linux so in theory it should eventually be able to sort out that stuff if something locks up.

But like you said sometimes it takes a little bit of time. And it seems some people are having some issues? I can't figure out how to reproduce any of it and I've spent many hours trying.

--- Mystic BBS v1.12 A44 2020/01/29 (Linux/64)
* Origin: Sector 7 (21:1/108)

How long do you stay ghosted? What OS is Alcoholiday?

I'm not sure of the exact OS distro, but it's Linux on a Pi. As far as the Mystic version goes, this has been happening for at least the past 2 years (probably longer.)

eventually released. I'm just curious if you are giving Mystic time to reach the inactivity timeout that the BBS has set. I assume that will be

I've been ghosted on Alcoholiday for several days, even for a week one time while the sysop was on vacation.

Has this been an issue in past versions of Mystic? I'm going to ask the sysop about his exact OS & Mystic version and I'll re-post on this topic when I get those details.

--- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
* Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)