Hi,

I've toggled the "No Timeout" setting for my account (Mystic v1.12 A45 2020/08/26 (Linux/32)); but after sometime, the BBS would just boot me back out (if I was telnet'd) or back to the bash prompt (if I just use 'mystic -l'). I don't see any errors in the node?.log.

I haven't timed how long before it boots me; but I thought that the setting would prevent this.

That said, the way it booted me looks like somehow the BBS crashed (but it didn't as there aren't any errors showing).

If "No timeout" is set to true, wouldn't 1) The time on the top right stay the same? 2) If the timeout was in effect, wouldn't a message saying (along the lines of) "Sorry, you have used up all your time"?

I have my time set to 9999.

Any information appreciated.

Edmund




Edmund


... An efficient bureaucracy is the greatest threat to liberty.
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Eagle's BBS | HK (1:153/7083)

I've toggled the "No Timeout" setting for my account (Mystic v1.12 A45 2020/08/26 (Linux/32)); but after sometime, the BBS would just boot me back out (if I was telnet'd) or back to the bash prompt (if I just use 'mystic -l'). I don't see any errors in the node?.log.

The No timeout flag disables the inactivity timeout (not time per day) but there are some many possiblities as to why you might be getting disconnected, anything from a bug to running out of time, to your ISP/router killing open sockets because you're idle and it thinks they're stale (ie you would need a
telnet client if connected via telnet that sends NOOP to stay connected)...

If you are connected via ./mystic -l and it happens, that seems to point to something else not client/router related. If you ran out of time (ie minutes per day) or were removed from inactivity, then it should have printed a message or logged you out as you noted.

I don't really have a good explaination for you at the moment to be honest.

... Help! I can't find the "ANY" key.

--- Mystic BBS v1.12 A47 2021/11/06 (Windows/32)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

I haven't timed how long before it boots me; but I thought that the setting would prevent this.

I forgot to mention the latest prealpha build has an option to disable the time per day system globally, so if you have that and disable your inactivity timeout then you should be able to sit there forever so long as your router/OS doesn't disconnect a stale connection.

http://mysticbbs.com/downloads/prealpha/

... Operator, give me the number for 911

--- Mystic BBS v1.12 A47 2021/11/18 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hi g00r00,

If you are connected via ./mystic -l and it happens, that seems to point to something else not client/router related. If you ran out of time (ie minutes per day) or were removed from inactivity, then it should have printed a message or logged you out as you noted.

Just tested it out. Yes, even with the latest prealpha, the bbs just crashes to the bash prompt.

That said, I don't know if this is related but there is an error in the errors.log.

2021.19.11 12:44:36 MYSTIC 001 Cannot write to /mystic/data/chat1.dat. Code=2, PID=23521

Will followup when I find if it is this error that's being written when I get booted.

Edmund

--- Mystic BBS v1.12 A47 2021/11/18 (Linux/32)
* Origin: Eagle's BBS (1:153/7083)

Hi g00r00,

If you are connected via ./mystic -l and it happens, that seems to point to something else not client/router related. If you ran out of time (ie minutes per day) or were removed from inactivity, then it should have printed a message or logged you out as you noted.

I'd like to confirm that it is indeed true that something happens,
and the following error appears as I get booted to the prompt.

2021.19.11 13:27:30 MYSTIC 001 Cannot write to /mystic/data/chat1.dat. Code=2, PID=23556

Before this error happens, there is a chat1.dat file:

-rwxr-xr-x 1 bbs users 131 Nov 19 13:03 chat1.dat*

After this error, this file no longer exists which is probably what is supposed to happen.

Edmund

... Inside every cynical person, there is a disappointed idealist.

--- Mystic BBS v1.12 A47 2021/11/18 (Linux/32)
* Origin: Eagle's BBS (1:153/7083)

I'd like to confirm that it is indeed true that something happens,
and the following error appears as I get booted to the prompt.

2021.19.11 13:27:30 MYSTIC 001 Cannot write to /mystic/data/chat1.dat. Code=2, PID=23556

Well this is a start at least! A47 has better logging as you can see which can't hurt as we get this sorted out! :)

It looks like that file is getting removed somehow like you said which is what Code=2 means. Typically things like this end up being either a bug or permissions related when it comes to the Linux version. In this case no one else has reported anything like this that I know of, so lets start with permissions.

-rwxr-xr-x 1 bbs users 131 Nov 19 13:03 chat1.dat*

It looks like you are running the BBS as user bbs in the group users, so I would say first thing to try is: Shut everything down and do a chown to make sure the user has permissions for everything:

sudo chown -R users:bbs /mystic

Now log in as the BBS user and see if the problem goes away. If that doesn't work you could also try to do a local login as an admin to see if the problem still happens:

sudo ./mystic -l

If the problem goes away when you login as a super user then its probably permissions. If you do the super user admin it might be a good idea to do another chown afterwards just to be safe/make sure everything is owned by
the bbs user.

If any of this helps or not let me know and then we can try to figure out what we can look into next.

Thanks!

... Youth is glorious, but it isn't a career

--- Mystic BBS v1.12 A47 2021/11/18 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hi g00r00,

It looks like you are running the BBS as user bbs in the group users, so
I would say first thing to try is: Shut everything down and do a chown
to make sure the user has permissions for everything:

I've tried the following:

1) sudo ./mystic -l
Result: boots to prompt after ~4-5 minutes.

2) shutdown mis, chown -R bbs.users mystic, start mis, sudo ./mystic -l
Result: boots to prompt after approx. same time frame.

Both ways have the following in the errors.log file (w/ different pid):

2021.22.11 08:49:00 MYSTIC 002 Cannot write to /mystic/data/chat2.dat. CODE=2, PID=30423
2021.22.11 09:17:55 MYSTIC 002 Cannot write to /mystic/data/chat2.dat. CODE=2, PID=30516

That said, I do notice an event being run before 09:17:55.

09:17:53 EVENT Sending shutdown notice to node: 2
09:17:53 EVENT Resetting ghost node: 2 (Invalid server slot)
09:20:03 EVENT Running event: Poll echomail
09:20:03 EVENT Cmd: ./mis poll
09:20:03 EVENT Res: 0

So I'm guessing that there is an event on my system that's killing the node. I'm still wondering if it's related to the next event (Poll echomail).

I do have a regular event which polls my uplink; but I don't quite see why it would kill the 2nd Node (I'm currently on two nodes) and not both nodes.
So I'm assuming that's just a coincidence since it killed the node and then waited 2 minutes later before polling.

Unfortunately, I'm looking at the events in the Event editor and I don't see something which would kill just an idle node after ~ 4 to 5 minutes.
I do have Inactivity set to 300 and I do have Disable Time to Yes. So for a bit of fun, I set the Inactivity to 10 to see what happens as that's the only thing that's related to 5 minutes (300 seconds). (Yes, just grasping at straws right now)

After changing that setting, I restarted mis and logged in but after 10 seconds, nothing happens. So not sure still.

Edmund

... The dog ate my .REP packet
--- Mystic BBS v1.12 A47 2021/11/18 (Linux/32)
* Origin: Eagle's BBS (1:153/7083)

Hello Edmund,

I've tried the following:

1) sudo ./mystic -l
Result: boots to prompt after ~4-5 minutes.

I never run ./mystic -l as root. I suspect this is where permissions errors come from.

You will likely need to chown the files in your mystic directory so they are owned by the user that owns ./mystic rather than root.

Ttyl :-),
Al

... Do you like me for my brain, or my BAUD?
--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hi Alan,

I never run ./mystic -l as root. I suspect this is where permissions errors come from.

Actually, I don't run it as root, but g00r00 mentioned that I should try it to see if it makes any difference.

Edmund

... Anything is possible if you don't know what you're talking about

--- Mystic BBS v1.12 A47 2021/11/18 (Linux/32)
* Origin: Eagle's BBS (1:153/7083)

Hello Edmund,

I never run ./mystic -l as root. I suspect this is where
permissions errors come from.

Actually, I don't run it as root, but g00r00 mentioned that I should
try it to see if it makes any difference.

You should take g00r00's advice over mine.

This looks to me like a possible cause of permissions errors but I don't know what you and g00r00 have discussed.

Ttyl :-),
Al

... I strive for perfection, what I get is reality
--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

That said, I do notice an event being run before 09:17:55.

09:17:53 EVENT Sending shutdown notice to node: 2
09:17:53 EVENT Resetting ghost node: 2 (Invalid server slot)

This would be exactly what is causing the file to go missing and for the node to shutdown. Its telling us its killing the node, but we need to figure out why that is happening. I'll do some tests as soon as I can get a second.

Are you using MIS as your telnet server? And you did mention it happens in -l too and it shouldn't. This sounds like some sort of bug. Worst case scenario if I can't solve this quickly for you, I will put an option somewhere so the "ghost node check" in MIS can be disabled.

I'll get you sorted out here soon!

... Nine times out of ten the statisticians are wrong

--- Mystic BBS v1.12 A47 2021/11/18 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

09:17:53 EVENT Sending shutdown notice to node: 2
09:17:53 EVENT Resetting ghost node: 2 (Invalid server slot)

Hi there!

I had a little time to work on this during lunch and I was able to see what I think the problem was. I fixed it and I am uploading a new version as I type this.

You should be able to download it from
www.mysticbbs.com/downloads/prealpha

If you are running the latest version of A47 and have followed the instructions from update.txt when you upgraded, then you should be able to simply run:

./install replace /mystic

And it will update your BBS for you. Just make sure that you have MIS and Mystic shutdown when you do it so there are no conflicts.

I didn't have time to do any significant testing before I had to get back to work but I hope this helps solve the problem. Please let me know how it works for you if you give it a shot!

... Top secret! Burn before reading!

--- Cowbell BBS v1.12 A47 2021/11/22 (Windows/32)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hi g00r00!

I had a little time to work on this during lunch and I was able to see what I think the problem was. I fixed it and I am uploading a new
version as I type this.

That's Awesome! Thanks! Will upgrade it and test it out.

Edmund

... A Mystic asking for a hot-dog: "Make me one with everything"
--- Mystic BBS v1.12 A47 2021/11/18 (Linux/32)
* Origin: Eagle's BBS (1:153/7083)