1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • Mystic process

    From Immortal@21:1/185 to All on Thursday, September 14, 2017 19:56:43
    Hey guys,

    My Ubuntu VM was running at near 100% cpu usage for over an hour for no apparent reason. I had a mystic process running utilizing like 96% cpu resources. Mis and Mis2 are up and idling, nobody is online, nothing going
    on. What is this mystic process?

    After rebooting, the process is gone and its back to normal.

    Immortal

    --- Mystic BBS v1.12 A35 (Linux/64)
    * Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)
  • From bcw142@21:1/145.3 to Immortal on Friday, September 15, 2017 06:35:42
    On 09/14/17, Immortal said the following...

    My Ubuntu VM was running at near 100% cpu usage for over an hour for no apparent reason. I had a mystic process running utilizing like 96% cpu resources. Mis and Mis2 are up and idling, nobody is online, nothing going on. What is this mystic process?

    For me it was extra mis copies in endless loops as near as I can figure. They weren't working, but were using up CPU time like crazy. I've switched over to mis2 for telnet and that disappeared. The drawback is no country blocking.

    --- Mystic BBS v1.12 A35 (Linux/64)
    * Origin: Workpoint (21:1/145.3)
  • From g00r00@21:1/108 to Immortal on Sunday, October 22, 2017 15:32:42
    My Ubuntu VM was running at near 100% cpu usage for over an hour for no apparent reason. I had a mystic process running utilizing like 96% cpu resources. Mis and Mis2 are up and idling, nobody is online, nothing going on. What is this mystic process?

    A35 changed the way Mystic does shutdowns. If you can look at the Sysop log and see the last person online and see what they were doing last that would
    be helpful.

    There are still some situations where Mystic does not properly shut down the node it seems.

    If its too much to handle A34 should not have this issue, but that doesn't really help me pinpoint the issue if everyone goes back :)

    --- Mystic BBS v1.12 A36 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From bcw142@21:1/145.2 to g00r00 on Sunday, October 22, 2017 17:09:43
    On 10/22/17, g00r00 said the following...
    A35 changed the way Mystic does shutdowns. If you can look at the Sysop log and see the last person online and see what they were doing last
    that would be helpful.

    I've had this problem on both the Pi and Ubuntu x64, but there is nothing I'd call a Sysop log to check. There is biglogs.txt, mutil.log, errors.log, fidopoll.log, mis2.log, mis.log, node?.log, server_binkp.log, server_nntp.log, server_pop3.log, server_smtp.log, server_telnet.log. So look through the various node?.logs to try and find it or the telnet.log?

    --- Mystic BBS v1.12 A35 (Linux/64)
    * Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)
  • From g00r00@21:1/108 to bcw142 on Sunday, October 22, 2017 20:45:18
    A35 changed the way Mystic does shutdowns. If you can look at the Sy log and see the last person online and see what they were doing last that would be helpful.

    I've had this problem on both the Pi and Ubuntu x64, but there is
    nothing I'd call a Sysop log to check. There is biglogs.txt, mutil.log,

    What we want to see is what the user was last doing when they logged out or dropped connection, so this would be found in "nodeX.log".

    There is a place (or places) within the BBS that if the connection is lost it will lock the node and use 100% CPU. I need to figure out where these places are. This is specific only to A35 and beyond, as the shutdown process has completely been changed.

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