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)

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)