1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • mis shutsdown without my instruction

    From Balky@21:1/192 to All on Saturday, July 08, 2017 16:54:04
    Hi,

    It seems that mis shutsdown without my instruction. I've updated to the
    recent Mystic alpha, and I haven't experienced this problem before. What
    could be wrong? The following are the last lines in my mis log:

    Jul 06 10:54:20 0 Connect: 63.142.222.220 (63.142.222.220.nwinternet.com)
    Jul 06 10:54:24 Shutting down
    Jul 08 16:49:45 0 Opening socket on 0.0.0.0:23

    --- Mystic BBS v1.12 A34 (Linux/64)
    * Origin: A 90's Manila BBS telnet://a90smanilabbs.ddns.net (21:1/192)
  • From bcw142@21:1/145.2 to Balky on Saturday, July 08, 2017 08:48:22
    On 07/08/17, Balky said the following...
    It seems that mis shutsdown without my instruction. I've updated to the recent Mystic alpha, and I haven't experienced this problem before. What could be wrong? The following are the last lines in my mis log:

    Jul 06 10:54:20 0 Connect: 63.142.222.220 (63.142.222.220.nwinternet.com) Jul 06 10:54:24 Shutting down
    Jul 08 16:49:45 0 Opening socket on 0.0.0.0:23

    That log doesn't show what happened, it shows a 4 second connection from Washington state. Check your other logs like server_telnet.log & node logs to see if they note anything to cause it. It doesn't look like my log which
    mostly says:
    May 13 15:21:04 Starting MIS in daemon mode
    May 13 15:21:04 MIS startup complete
    May 13 15:21:54 MIS received SIGTERM; shutting down
    May 13 15:21:54 MIS shutdown complete
    For each time I bring it up and down again while checking things and making changes. 'MIS startup complete' shows normal running for mine. SIGTERM is the normal shutdown for Mystic mis with something like 'sudo killall mis' using daemon mode (normal run for Linux).

    --- Mystic BBS v1.12 A33 (Linux/64)
    * Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)
  • From Balky@21:1/192 to bcw142 on Tuesday, July 11, 2017 12:13:38
    On 07/08/17, bcw142 said the following...
    Jul 06 10:54:20 0 Connect: 63.142.222.220 (63.142.222.220.nwinternet. Jul 06 10:54:24 Shutting down
    Jul 08 16:49:45 0 Opening socket on 0.0.0.0:23

    That log doesn't show what happened, it shows a 4 second connection from Washington state. Check your other logs like server_telnet.log & node
    logs to see if they note anything to cause it. It doesn't look like my
    log which mostly says:

    Hi. It appears that I mistook my mis.log as my server_telnet.log. The log
    lines I quoted above are from my server_telnet.log. I am currently testing a script to restart Mystic should it stop listening on port 23. Hopefully, it will work.

    --- Mystic BBS v1.12 A34 (Linux/64)
    * Origin: A 90's Manila BBS telnet://a90smanilabbs.ddns.net (21:1/192)