Mystic BBS on Pi 1 100% CPU load

[gertk]

Hi,

Fiddling with Mystic BBS on the Pi (1) to serve some old computers the good old BBS feeling.
I enabled telnet access and added 4 (USB) serial ports which also spawn a (local) telnet session when a return is received on the serial input.

Alas the Pi seems 100% occupied even when Mystic BBS is idle.
Any ideas ? The BBS system itself works fine just the load is constant 100%

[Andyroo]

Start with

Code: Select all

top

to see what is actually eating up the CPU use - it maybe one rogue task or lots of them eating up little bits.

If you have never used this see https://www.booleanworld.com/guide-linux-top-command/ for a walkthrough

The other option is 'htop' but I think you will need to install that with something like:

Code: Select all

sudo apt-get install htop

Then you can do a Google or DDG for the process but it may be that the Pi is either under powered or out of memory.

[gertk]

Hi Andyroo,

Alas, it is definitely 'mis' which is eating up all the CPU,
Memory seems to be no problem:

Code: Select all

top - 14:04:29 up 16:10,  1 user,  load average: 1.11, 1.16, 1.11
Tasks:  66 total,   2 running,  41 sleeping,   0 stopped,   0 zombie
%Cpu(s):  1.3 us, 71.1 sy, 27.4 ni,  0.0 id,  0.0 wa,  0.0 hi,  0.3 si,  0.0 st
KiB Mem :   443868 total,   255064 free,    24300 used,   164504 buff/cache
KiB Swap:   102396 total,   102396 free,        0 used.   364964 avail Mem 

  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND      
  243 mystic    30  10   26528   2640   2148 R 96.5  0.6 960:30.81 mis          
11437 pi        20   0    8100   3240   2784 R  2.8  0.7   0:00.28 top          
11208 pi        20   0   11644   3904   3144 S  0.6  0.9   0:00.62 sshd         
   80 root      20   0       0      0      0 I  0.3  0.0   0:02.50 kworker/u2:2 

[Andyroo]

Not good as the author is not currently supporting anything but the Wiki

There is a note in 1.12 36 Alpha about 100% CPU http://wiki.mysticbbs.com/doku.php?id=whats_new_112 but not sure thats relevant:

+ In Unix versions, Mystic will now "watchdog" any door process. If the connection is lost, Mystic will immediately send a SIGTERM signal to the process and shut itself down. This will fix the "DOSEMU 100% cpu" problem both on the DOSEMU side and the Mystic side.

A few thoughts (all basic I'm afraid):

1) Try a clean OS image with latest updates (if you have not done this)
2) Double check the installation process was / is OK - going by this for Ubuntu its not a one click install https://groups.google.com/forum/#!topic ... 2tJbUEjxSk
3) Try only one USB port to start with (esp if you have different device types)

[gertk]

Well... I found my mistake

I started the mystic BBS server on boot in server mode (on a headless system) while I should have started it in daemon mode.

That seems to have cured the problem, now it it is hardly registering in top ..

Thanks for the tips though.