Hi folks, since upgrading to A34, I've had issues with MIS becoming unresponsive periodically. I run on a Pi, in daemon mode. The last time this happened I checked the PIDs and was unable to kill one of the MIS processes with killall/kill commands.

This seems to be happening every few hours. I haven't changed my system since upgrading to A34. I may try rolling back to the older version I was using (A32), and see if the problem persists.

Has anyone else noticed this? It could be my Pi, but I've never seen this
until the recent upgrade. Been running on the Pi with zero issues since late 2015. Could it be file system corruption?

-ZR (Alcoholiday BBS)

|15z|07E|08RO |15r|07E|08ADER

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: ACiD Telnet HQ / blackflag.acid.org (21:1/112)

zero reader wrote to All <=-

This seems to be happening every few hours. I haven't changed my system since upgrading to A34. I may try rolling back to the older version I
was using (A32), and see if the problem persists.

Has anyone else noticed this? It could be my Pi, but I've never seen
this until the recent upgrade. Been running on the Pi with zero issues since late 2015. Could it be file system corruption?

I was experiencing the same with A34 and have gone back to what i had
before. After a few hours the nodes would all show as logging in on
nodespy and I was unable to connect. Killing ghosts did not always fix
the issue.

Kev


___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A33 (Raspberry Pi/32)
* Origin: Razor's Domain 3.141592... (21:1/162)

Hi folks, since upgrading to A34, I've had issues with MIS becoming unresponsive periodically. I run on a Pi, in daemon mode. The last time this happened I checked the PIDs and was unable to kill one of the MIS processes with killall/kill commands.

Have you tried MIS2 at all?

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

I was experiencing the same with A34 and have gone back to what i had before. After a few hours the nodes would all show as logging in on nodespy and I was unable to connect. Killing ghosts did not always fix
the issue.

Did you try MIS2?

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

On 06/26/17, g00r00 said the following...

I was experiencing the same with A34 and have gone back to what i had before. After a few hours the nodes would all show as logging in on nodespy and I was unable to connect. Killing ghosts did not always fi the issue.

Did you try MIS2?

I haven't tried MIS2 yet, but I might as well. This is what my processes
looked like when I got home tonight and it was jammed:

pi@raspberrypi:~$ ps -ef | grep mis
pi 3127 1 0 Jun25 ? 00:01:42 ./mis -d
pi 4947 3127 0 Jun25 ? 00:01:02 ./mis -d
pi 7941 3127 0 10:17 ? 00:00:25 ./mis -d
pi 8434 3127 0 03:36 ? 00:00:46 ./mis -d
pi 8702 8659 0 18:25 pts/2 00:00:00 grep mis

Checking my telnet.log, my system was getting hammered by a few IPs right before this happened, then at 10:17, the same timestamp as one of those PIDs
up there, the log indicates: Jun 26 10:17:11 Shutting down

Anyway, I'll check out MIS2. I haven't played with that in a while.

-ZR

--- Mystic BBS v1.12 A34 (Raspberry Pi/32)
* Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)

On 06/26/17, g00r00 said the following...

Did you try MIS2?

What does "Error 214: Shutting Down" indicate? That's what MIS2 reports when a user connects to the board. Configuration issue on my end maybe?

-ZR

--- Mystic BBS v1.12 A34 (Raspberry Pi/32)
* Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)

I haven't tried MIS2 yet, but I might as well. This is what my processes looked like when I got home tonight and it was jammed:

Give it a try. Since you're on Pi it might not be great since I am stuck on a Pi 1 right now, so its very difficult to test it (because it takes forever to compile).

On intel-based systems, MIS2 is light years ahead of MIS.

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

Hi folks, since upgrading to A34, I've had issues with MIS becoming unresponsive periodically. I run on a Pi, in daemon mode. The last time this happened I checked the PIDs and was unable to kill one of the MIS processes with killall/kill commands.

I'm using A33 on my Pi without problems, it has the QWK/QWKE MSGID problem fixed so it's a good version to run if you want to go back a level.

--- Mystic BBS v1.12 A33 (Linux/64)
* Origin: Workpoint (21:1/145.3)

g00r00 wrote to bl00d <=-

I was experiencing the same with A34 and have gone back to what i had before. After a few hours the nodes would all show as logging in on

Did you try MIS2?

No, but I'll have some time this weekend, so I'll try to upgrade again
and use MIS2 along with MIS and see how it works out.

Kev

___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A33 (Raspberry Pi/32)
* Origin: Razor's Domain 3.141592... (21:1/162)