Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.bbs.mystic    |    Mystic Sysops are mystical nerds...    |    11,847 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 10,322 of 11,847    |
|    Edmund Wong to All    |
|    Re: No Timeout setting    |
|    22 Nov 21 09:36:25    |
      From: nospam.Edmund.Wong@f7083.n153.z1.fidonet.org              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.              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              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca