Hi All,

I've installed Mystic BBS on my little VPS to replace GoldEd+ and have access to FidoNet from any place in the world. I seems to be working fine except for one thing... Every now and then MIS crashes with segmentation fault, and
after that I have to delete mis.bys semaphore and restart it. But it looks
like some kind of internal session counter is not getting reset and after a
few crashes I cannot connect to it anymore, getting only BUSY response.
I had to increase simultaneous connection count several times already to be able to read echoes, but I believe, this will have its limits. I'm the only user of this setup and I use it only to read messages. How can I reset open sessions counter? Console commands will be appreciated, because in this case I'll be able to
write a simple bash script to clean everything and restart MIS.

Thank you.

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: twixed BBS (1:275/98)

@ AM> I've installed Mystic BBS on my little VPS to replace GoldEd+ and have

access to FidoNet from any place in the world. I seems to be working
fine except for one thing... Every now and then MIS crashes with segmentation fault, and after that I have to delete mis.bys semaphore
and restart it. But it looks like some kind of internal session counter

You need to upgrade to the latest version. A36 added a new server and A37/A38 were spent working out the kinks. With A39 it should be relatively stable at this point. No one is reporting crashing (yet).

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

On 04/25/18, g00r00 said the following...

No one is reporting crashing (yet).

I still 216 anytime a python script tries to call msg_open() but I'm pretty sure that's something unique to my python setup.

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Subcarrier BBS (1:249/400)

No one is reporting crashing (yet).

I still 216 anytime a python script tries to call msg_open() but I'm pretty sure that's something unique to my python setup.

Yeah I don't know exactly how to remedy that. No one else has reported it to my knowledge.

The only time I was able to see a crash is when there was a mismatch of 32/64 bit Mystic and/or Python files somewhere. In that case it does exactly what you've described.

I don't remember what you're running but have you ever tried downloading a fresh Ubuntu 18.04 or something and trying it? Mystic Python should work
"out of the box" with that.

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

Hi g00r00,

fine except for one thing... Every now and then MIS crashes with segmentation fault, and after that I have to delete mis.bys semaphore and restart it. But it looks like some kind of internal session count

You need to upgrade to the latest version. A36 added a new server and A37/A38 were spent working out the kinks. With A39 it should be relatively stable at this point. No one is reporting crashing (yet).

I will update eventually, but for now I've disabled telnet server, leaving
only RLogin access to BBS. 24 hours without crashes is a huge progress.(:

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: twixed BBS (1:275/98)

On 04/26/18, g00r00 said the following...

I don't remember what you're running but have you ever tried downloading
a fresh Ubuntu 18.04 or something and trying it? Mystic Python should work "out of the box" with that.

I share the setup running the BBS so I can't make sweeping changes to the OS, though since it's running Profile 17 Gentoo I imagine it's some compile flag
or security policy like system-wide position independent executables that it doesn't like. I should test it with Ubuntu in a VM but I fully expect it will work fine there.

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Subcarrier BBS (1:249/400)

I will update eventually, but for now I've disabled telnet server,
leaving only RLogin access to BBS. 24 hours without crashes is a huge progress.(:

Okay, well you're reporting crashes that have been fixed in the newer
versions. If you upgrade you'll have endless uptime. :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

a fresh Ubuntu 18.04 or something and trying it? Mystic Python should work "out of the box" with that.

Ubuntu 18.04?? New version I didn't know was out....

Regards

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: The New Frontier ][ - thenewfrontier2.hop2.org (1:226/16)

On 05/02/18, Charles Stephenson said the following...

a fresh Ubuntu 18.04 or something and trying it? Mystic Python shoul work "out of the box" with that.

Ubuntu 18.04?? New version I didn't know was out....

heh yep it is on their page:
Ubuntu 18.04 LTS out now!

If you are running an earlier version it should still run no issues really.

Cheers!
Pequito

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Twinkle BBS # (1:317/2)

On 05/02/18, Charles Stephenson said the following...

a fresh Ubuntu 18.04 or something and trying it? Mystic Python shoul work "out of the box" with that.

Ubuntu 18.04?? New version I didn't know was out....

Yup. Ubuntu 18.04 LTS was released last week. :)


---

Black Panther
a.k.a. Dan Richter
Sysop - Castle Rock BBS (RCS)
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
The sparrows are flying again....

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (1:317/3)

On 05/02/18, Christopher Malo said the following...

Ubuntu 18.04?? New version I didn't know was out....

heh yep it is on their page:
Ubuntu 18.04 LTS out now!

I'll be getting it ASAP!

Thanks

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: The New Frontier ][ - thenewfrontier2.hop2.org (1:226/16)