I know i read something on this somewhere, but I dont recall solution.

Since moving to linux, I regularly am getting multiple instances of MIS running, not sure what is causing it, but usually when it happens it takes all of mystic down.

Rolling back to mystic A33/Linux 64 seems to have resolved this problem for now.

Scott Miller
---Quickshot
----Troybbs.com

--- Mystic BBS v1.12 A33 (Linux/64)
* Origin: Troy's Den % troybbs.com (21:2/134)

On 08/12/17, Zero Reader said the following...

On 08/12/17, quickshot said the following...

Yep... same here. I rolled back a few versions and haven't had a issues. It's not just you!

what is the process to rollback?

Well, in my case I just grabbed the binaries from a backup I had. I
think A32 may be the last version that didn't have that issue?

I fixed the issue by using MIS2. I still run MIS for the ftp service tho.

--- Mystic BBS v1.12 A34 (Linux/64)
* Origin: Cyberia BBS | cyberia.darktech.org | San Jose, CA (21:1/120)

On 08/15/17, Gryphon said the following...

I fixed the issue by using MIS2. I still run MIS for the ftp service
tho.

I'm not sure why, but MIS2 was tossing up an error 213 when a user connected.
I think someone else here has also reported that.

Going back a few versions and MIS2 works fine. I haven't really spent a lot
of time sussing it out, so it very well could be an issue with my configuration.

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

On 08/16/17, Zero Reader said the following...

I'm not sure why, but MIS2 was tossing up an error 213 when a user connected. I think someone else here has also reported that.

Going back a few versions and MIS2 works fine. I haven't really spent a lot of time sussing it out, so it very well could be an issue with my configuration.

Might try A32 or A33, A31 has some bugs too. A32 is more stable than A31 and A33 has the MSGID bug fixed. A34 is right out, it doesn't really work right, crashes or never boots (on the Pi).

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

On 08/14/17, quickshot said the following...

Since moving to linux, I regularly am getting multiple instances of M running, not sure what is causing it, but usually when it happens it takes all of mystic down.

Rolling back to mystic A33/Linux 64 seems to have resolved this problem for now.

Odd that it made a difference for you, I run it without problems but only on point systems - one of which gets no traffic and the other (this one) little traffic. It's my main system that I do most things with, but I haven't seen a problem with mis running multiple times. Still I do reboot at least one a
week to update the Win10 side of this dual boot setup (otherwise the updates take forever when I try to boot Win10). A33 seems to be the best on the Pi,
A34 seems OK under Ubuntu 14.04 or 16.04 32 or 64 bit, all seem fine here.
Good that A33 runs OK as that's the first one to offer correct MSGID handling.

--- Mystic BBS v1.12 A34 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)