I have found even this version of A37 needs the looping to keep running. Something (hackers?) kills it or stops it's running so it doesn't show up in the tasks and has to be restarted. So those old lopping scripts are needed again with A37. Will check my logs to see if it was shutdown somehow. eventsignal.txt only shows:
Dec 08 08:25:06 MIS Received 17
Dec 08 08:27:51 MIS Received 17
Dec 08 08:34:06 MIS Received 15
Not sure what log would tell me what shut it down. Is there one?

--- Mystic BBS v1.12 A37 2017/12/07 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

Dec 08 08:34:06 MIS Received 15
Not sure what log would tell me what shut it down. Is there one?

Linux signal 15 is a SIGTERM, which is a signal to shut down the application... so its absolutely getting a shutdown signal from something/somewhere.

I think using "strace" on MIS and running it as a non-daemon might expose where that signal is coming from. I have seen this issue before and this is one of two reasons that log file is being captured right now.

--- Mystic BBS v1.12 A37 2017/12/09 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

bcw142 wrote to g00r00 <=-

I have found even this version of A37 needs the looping to keep
running. Something (hackers?) kills it or stops it's running so it
doesn't show up in the tasks and has to be restarted. So those old
lopping scripts are needed again with A37. Will check my logs to see if
it was shutdown somehow. eventsignal.txt only shows:
Dec 08 08:25:06 MIS Received 17
Dec 08 08:27:51 MIS Received 17
Dec 08 08:34:06 MIS Received 15
Not sure what log would tell me what shut it down. Is there one?

I still run my monitoring system with A36 (had to tweak it to only look for mis and restart it with the right options).


... Have you checked your smoke detector batteries & Fire Ext, LATELY?!
___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A36 2017/12/04 (Raspberry Pi/32)
* Origin: The Bridge - bridge.vkradio.com (21:1/143)