1. Forum
  2. fsxNet
  3. FSX MYS

  • Node Issue

    From Accession@21:1/200 to fuzion on Sun Dec 28 13:58:02 2025
    Hey fuzion!

    On Sun, 28 Dec 2025 17:20:28 +0000, you wrote:

    I managed to locate a rogue "mis" task running in the background apps on
    the server. It was waaaaay down in the task manager, so I didn't notice
    it before. After forcing a shutdown, everything seems to be playing
    nicely again and the node logging is back to normal.

    Sounds like a ghost node. Someone logged off or hung up wierd, or while hanging up an event ran or something (like message tossing/scanning, or a poll), and the process stayed alive.

    chat1.dat can be deleted manually if it's causing issues, and just as well, someone else mentioned using nodespy to kill the ghost node. Both tend to have a similar result. Your method of stopping and restarting mis will also do the same (clear all nodes, etc).

    Glad you figured it out and got it back to normal!

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    --- GoldED+/LNX 1.1.5-b20250409
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)
  • From fuzion@21:1/215 to Accession on Mon Dec 29 15:59:37 2025
    Hi Nick,

    Sounds like a ghost node. Someone logged off or hung up wierd, or while hanging up an event ran or something (like message tossing/scanning, or
    a poll), and the process stayed alive.

    Yeah, it was a bit of a random one this time. When this has happened in the past, we get a dead "mystic" process hanging around and it slows the server down which is usually a tell tale sign.

    With this one being a "mis" process hovering in the background, it was easy
    to miss (no pun intended). At least I know what to look out for next time, every day is a school day as they say. :)

    Cheers!

    Darren

    ... hO! hO! hO!

    --- Mystic BBS v1.12 A48 (Windows/64)
    * Origin: Retro32 BBS (21:1/215)
  • From neo67@21:2/136 to fuzion on Thu Jan 22 22:14:20 2026
    I managed to locate a rogue "mis" task running in the background apps on the server. It was waaaaay down in the task manager, so I didn't notice
    it before. After forcing a shutdown, everything seems to be playing
    nicely again and the node logging is back to normal.
    Hi fuzion,

    iy you have this issues again and I think, y'r running mystic on Windwos:

    Powershell: Get-Process mis -ErrorAction SilentlyContinue | Select-Object Id, ProcessName, StartTime, Path

    CMD: tasklist /FI "IMAGENAME eq mis.exe"
    or
    CMD: wmic process where "name='mis.exe'" get ProcessId,ParentProcessId,CommandLine,ExecutablePath,CreationDate

    normal result:
    PS C:\mystic> Get-Process mis -ErrorAction SilentlyContinue | Select-Object Id, ProcessName, StartTime, Path

    Id ProcessName StartTime Path
    -- ----------- --------- ----
    5724 mis

    have fun & greez
    neo67

    --- Mystic BBS v1.12 A48 (Windows/64)
    * Origin: -= The News BBS | bbs.dosnetz.de:3232 =- (21:2/136)