itself and noticed in 'top' that mis was eating up 100% of my CPU. I bounced the mis service and now it's hovering around 5ish percent of CPU. There's nothing in error.log and nothing interesting in mis.log. Any ideas?

If this is an ongoing problem you could consider upgrading to the latest test versions and we can go from there if the problem persists.

Were any users "stuck" online?

Hi g00r00,

Yeah, it's back up to 100% again for some reason, though I'm able to use the BBS for now. Nothing in any mystic logs or in syslog, for that matter.

No users stuck online. I'm on alpha 36, 32 bit linux. So I should upgrade,
huh? I can give that a shot.

--- Mystic BBS v1.12 A36 2017/12/03 (Linux/32)
* Origin: lo fidelity bbs (21:2/142)

On 12/22/17, esc said the following...

itself and noticed in 'top' that mis was eating up 100% of my CP bounced the mis service and now it's hovering around 5ish percen CPU. There's nothing in error.log and nothing interesting in mis Any ideas?

If this is an ongoing problem you could consider upgrading to the lat test versions and we can go from there if the problem persists.

Were any users "stuck" online?

Hi g00r00,

Yeah, it's back up to 100% again for some reason, though I'm able to use the BBS for now. Nothing in any mystic logs or in syslog, for that
matter.

No users stuck online. I'm on alpha 36, 32 bit linux. So I should
upgrade, huh? I can give that a shot.

Curious you are only loading MIS now with A37 I think the late A36. g00r00 changed the name of mis2 to mis and removed mis v1 all together. I ask this due to the possibility of you using both mis/mis2 still and the events had
been transfered to the new mis so only one instance was needed. :)

Cheers!
Pequito

--- Mystic BBS v1.12 A37 2017/12/16 (Linux/64)
* Origin: Twinkle BBS # (21:1/126)

Curious you are only loading MIS now with A37 I think the late A36. g00r00 changed the name of mis2 to mis and removed mis v1 all together.
I ask this due to the possibility of you using both mis/mis2 still and
the events had been transfered to the new mis so only one instance was needed. :)

Hi Pequito, thanks :) I actually completely killed the vm slice where the mis/mis2 configuration issues lived. I then moved to install a fresh a36. I just now upgraded to a37, and I'm keeping an eye open for the .bsy file issue
I ran into before. Fingers crossed...

--- Mystic BBS v1.12 A37 2017/12/21 (Linux/32)
* Origin: lo fidelity bbs (21:2/142)

Hi Pequito, thanks :) I actually completely killed the vm slice where the mis/mis2 configuration issues lived. I then moved to install a fresh
a36. I just now upgraded to a37, and I'm keeping an eye open for the
.bsy file issue I ran into before. Fingers crossed...

Now that you have the latest version of A37 you will see a lot of extra logging...

There will be a "busylog.txt" in the root Mystic directory (or should be) and that will allow us to match up every create/remove of a BSY file so we can at least see where it happens, if it happens.

There will also be .mem files created so if you have a crash it can (hopefully) tell me an estimated line in the code where it happened. I'll also add in any additional logging I can surrounding any issue you're having if needed and I can update the prealpha site instantly.

The downsides with the latest prealphas are that I accidentally compiled it with BINKP debug logging so those BINKP logs get pretty cluttered. The binaries are also up to 10 times the size they normally are, and things in general will run a little slower... but it should go a long way to help me resolve your issues.

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