Subj : Re: Mystic BBS Windows Server Wont Start To : Nicholas Boel From : Shane O'Neill Date : Sun Jan 21 2018 08:41 pm On Sunday, January 21, 2018 at 11:54:06 AM UTC-7, Nicholas Boel wrote: > Hello, > > On Sun, 21 Jan 2018 15:56:42 GMT, Palkat72 wrote: > > p> I have setup and got working Mystic BBS for Windows v1112a38 how ever > p> twice now it has after about a day stopped working. When I go to restart > p> the server program its window will pop up for a quick 1/2 second then > p> close.  The nodespy will work, the config > p> utility will work but not the actual "mis.exe SERVER". > > p> I have tried to replace the data, msgs, menus etc folders with backups > p> of when it was working. I even tried to replace the mystic.dat file in > p> the root folder with a working copy and still it wont work. > > p> I have found that I have to start with a fresh install of Mystic then > p> copy over my data, msg, menus, logs folders along with the mystic.dat > p> file then it will work like nothing happened. > > p> This is a pain so I would love to know if anyone knows what is causing > p> my initial problem where the mis.exe program wont start the server all > p> of a sudden. > > p> Currently I am running it on a windows 7 32bit environment, the first > p> time this issue happened I was running it on a windows 10 64 bit > p> environment for what that is worth. > > p> Thanks for ANY help! > > The fact that mis.exe is stopping at some point is a matter on it's own, and > something should be mentioned in the logs as to why it shut down (try using > debug loglevel). > > But as for restarting, if mis.exe is shut down unexpectedly, take a look for > mis.bsy in your semaphore subdirectory and delete it before restarting. > > Regards, > Nick So it happened again, this time I was actually in the server window and hit the ESC key and confirmed yes SHUT DOWN. It shut down like normal but would not start backup. I then went into the semaphore folder per your suggestion and did delete the mis. bsy and then it DID start back up. Thank you for that! After I got the server to run again I did shut it down two more times with no issue and each time I notice it did NOT leave behind the mis.bsy file. So why sometimes does it leave it behind? I did set my logging level to 3 also. Below is a sample of the MIS log and you will notice between the two log entry's that when I shut down the server at + 2018.01.21 21:14:00 (this is the time I saw on my clock I shut it down) there is no "Event system stopped", "Manager shutdown complete" entry. How ever the second part of the attached log you will see after I got the server to start again (deleting the mis.bsy) then I shut it down right away it did log the "Event system stopped", "Manager shutdown complete" were shut down. I was also able to restart and shut down a few more times after with no issue. ......I hope that all makes sense.... -=-=-=-=-=-=[ LOG FILE SNIPPET ]=-=-=-=-=-=- --------------------- Mystic v1.12 A38 2018/01/01 Sun, Jan 21 2018 (loglevel 3) + 2018.01.21 15:48:35 MANAGER Starting event system + 2018.01.21 15:48:35 MANAGER Starting 1 server(s) + 2018.01.21 15:48:35 TELNET Listening on IPV4 port 6502 using interface "0.0.0.0" + 2018.01.21 15:48:35 TELNET Listening on IPV6 port 6502 using interface "::" + 2018.01.21 15:48:35 EVENT Starting 0 event(s) + 2018.01.21 15:48:35 SENDMAILStarted. Relaying to: mail.***********.com + 2018.01.21 15:49:46 TELNET > Connect on slot 1/5 + 2018.01.21 15:49:46 TELNET 1-Address *********** + 2018.01.21 15:49:46 TELNET 1-HostName ***********.net + 2018.01.21 15:49:46 TELNET 1-Creating terminal process + 2018.01.21 15:50:07 TELNET 1-Closing terminal process + 2018.01.21 18:14:55 TELNET > Connect on slot 1/5 + 2018.01.21 18:14:55 TELNET 1-Address *********** + 2018.01.21 18:14:55 TELNET 1-HostName ***********.net + 2018.01.21 18:14:55 TELNET 1-Creating terminal process + 2018.01.21 18:15:09 TELNET 1-Closing terminal process --------------------- Mystic v1.12 A38 2018/01/01 Sun, Jan 21 2018 (loglevel 3) + 2018.01.21 21:15:09 MANAGER Starting event system + 2018.01.21 21:15:09 MANAGER Starting 1 server(s) + 2018.01.21 21:15:09 TELNET Listening on IPV4 port 6502 using interface "0.0.0.0" + 2018.01.21 21:15:09 TELNET Listening on IPV6 port 6502 using interface "::" + 2018.01.21 21:15:10 EVENT Starting 0 event(s) + 2018.01.21 21:15:10 SENDMAILStarted. Relaying to: mail.***********.com + 2018.01.21 21:15:51 MANAGER Server shutdown received from console + 2018.01.21 21:15:51 MANAGER Shutdown: EVENT + 2018.01.21 21:15:51 MANAGER Shutdown: SENDMAIL + 2018.01.21 21:15:51 MANAGER Shutdown: TELNET + 2018.01.21 21:15:51 MANAGER Waiting for servers to stop (up to 60 seconds) + 2018.01.21 21:15:51 SENDMAILShutting down + 2018.01.21 21:15:51 EVENT Event system stopped + 2018.01.21 21:15:52 MANAGER Shutdown complete --- SoupGate-Win32 v1.05 * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3) .