Subj : Re: No Timeout setting
To : g00r00
From : Edmund Wong
Date : Mon Nov 22 2021 09:36 am
Hi g00r00,
g0> It looks like you are running the BBS as user bbs in the group users, so
g0> I would say first thing to try is: Shut everything down and do a chown
g0> 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.
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)
