Hello all,

I keep seeing mention of bugs and issues with IBOL. I'm trying to clear
these bugs as best I can. If I could get some definitive reports of issues, which include the IBOL version used and associated platforms, I'd appreciate it. You can post them here or you can email me at the email address
includedin the sysop.txt file in the archive.

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

Getting an error 216 crash of the Mystic node immediately upon accessing the message base here. Both IBOL01 and 02.
Other mpys that access the message bases also crash, including g00r00's own demo, so I don't think it's particular to IBOL.
Linux/64 and Python 2.7

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)

Getting an error 216 crash of the Mystic node immediately upon accessing the message base here. Both IBOL01 and 02.
Other mpys that access the message bases also crash, including g00r00's own demo, so I don't think it's particular to IBOL.
Linux/64 and Python 2.7

Are you using 32-bit Python with 64-bit Mystic or vice versa by chance? The only way I've been able to reproduce this crash (outside of A37) has been when 32-bit and 64-bit Mystic and Python mixed together. That makes it crash constantly.

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

On 01/16/18, g00r00 said the following...

Getting an error 216 crash of the Mystic node immediately upon access the message base here. Both IBOL01 and 02.
Other mpys that access the message bases also crash, including g00r00 own demo, so I don't think it's particular to IBOL.
Linux/64 and Python 2.7

Are you using 32-bit Python with 64-bit Mystic or vice versa by chance? The only way I've been able to reproduce this crash (outside of A37) has been when 32-bit and 64-bit Mystic and Python mixed together. That
makes it crash constantly.

This is something will check cause the demo mail one from the distribution
also crashes mine instant.

Cheers!
Pequito

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Twinkle BBS # (21:1/126)

On 01/16/18, g00r00 considered the following...

Are you using 32-bit Python with 64-bit Mystic or vice versa by chance? The only way I've been able to reproduce this crash (outside of A37) has

I had them mixed, ( I had just installed the InterBBS version), and had to install the 32-bit version of Python.Still crashes as soon as you access the menu item. Both 32-bit versions of Mystic and Python, on a 64-bit machine.

Mick

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Central Ontario Remote (21:1/156)

Are you using 32-bit Python with 64-bit Mystic or vice versa by chanc The only way I've been able to reproduce this crash (outside of A37) been when 32-bit and 64-bit Mystic and Python mixed together. That makes it crash constantly.

This is something will check cause the demo mail one from the
distribution also crashes mine instant.

Yep they all crash if those versions are mixed. I had it happen on my OSX machine for some reason. It took me a while to figure out the package
manager installed the 32-bit version.

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

On 01/16/18, g00r00 said the following...

Are you using 32-bit Python with 64-bit Mystic or vice versa by chance? The only way I've been able to reproduce this crash (outside of A37) has been when 32-bit and 64-bit Mystic and Python mixed together.

No, it's all 64-bit:
$ file mystic
mystic: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.4.0, stripped $ file /usr/bin/python
/usr/bin/python: symbolic link to python2.7
$ file /usr/bin/python2.7
/usr/bin/python2.7: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, stripped

I might just be missing some feature or module Mystic is expecting but there are no logs to indicate what it might be.

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)

On 01/16/18, g00r00 said the following...

Are you using 32-bit Python with 64-bit Mystic or vice versa by The only way I've been able to reproduce this crash (outside of been when 32-bit and 64-bit Mystic and Python mixed together. T makes it crash constantly.

This is something will check cause the demo mail one from the distribution also crashes mine instant.

Yep they all crash if those versions are mixed. I had it happen on my
OSX machine for some reason. It took me a while to figure out the
package manager installed the 32-bit version.

--- Mystic BBS v1.12 A39 2018/01/16 (Windows/32)

I have the 64 bit with 64 mystic was able to verify when I write a small py file to check which was installed. Still crashes on mailread.mpy with 216 (dcing the person using it mainly me only).

Cheers!
Pequito

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Twinkle BBS # (21:1/126)

I might just be missing some feature or module Mystic is expecting but there are no logs to indicate what it might be.

When does it crash for you? Do all programs crash or just that one?

I assume it wouldn't matter but Mystic doesn't shell out and run Python, its embedded (ie /bin/python isn't used by Mystic) so the interpreter isn't what its looking for or what it uses. What it does is it tries to load libpython2.7.so.1.0. If it can't find it, it logs it. If the single function fails to load it files, it logs it. There really isn't anything to log that isn't already logged.

Are you using an out of the box Linux distro? Maybe I can install that distro and try it? I still cannot find any issue with any of the Windows, Linux, or OSX VMwares I have.

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

On 01/17/18, g00r00 said the following...

When does it crash for you? Do all programs crash or just that one?

It crashes when it attempts to access a messagebase and the only log message it leaves is the error 216. Otherwise MPYs work just fine.

libpython2.7.so.1.0

$ file /usr/lib64/libpython2.7.so.1.0
/usr/lib64/libpython2.7.so.1.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped

Are you using an out of the box Linux distro? Maybe I can install that distro and try it?

It's a 64-bit Profile 17.0 Gentoo system. Not exactly what one would call an out of the box distro, but the 2.7 py setup is stock.

Some fiddling with msgread.mpy has narrowed down the crash to the msg_seek call. The msg_open call immediately before that seems to succeed but as I'm not familiar with the properties of that call all I did was check the raw value
of the variable, which seems to be a reference since it's always 1 for the first base opened and increments by 1 for each thereafter.

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)

On 01/15/18, Gryphon said the following...

I keep seeing mention of bugs and issues with IBOL. I'm trying to clear these bugs as best I can. If I could get some definitive reports of issues, which include the IBOL version used and associated platforms,
I'd appreciate it. You can post them here or you can email me at the email address includedin the sysop.txt file in the archive.

Well, from my side I can only report that on my system running Windows,
the ANSI gets broken when you see it over a telnet session. When you log on locally the ANSI is seen fine.

----
Regards from Nighthawk - AKA Flavio Bessa
Sysop of Saturn's Orbit BBS - Rio de Janeiro, Brazil
fcbessa@gmail.com - saturnsorbit.hopto.org

--- Mystic BBS v1.12 A38 2018/01/01 (macOS/64)
* Origin: Chiron, orbiting Saturn - Brazil (21:1/146.1)

On 01/28/18, Nighthawk said the following...

Well, from my side I can only report that on my system running Windows, the ANSI gets broken when you see it over a telnet session.
When you log on locally the ANSI is seen fine.

I have the same issue as Nighthawk. Locally it displays fine but logging in using Netrunner each line looks like it starts 20-25 columns in. It's
something in how it displays, rather than the .ans file. I renamed them both
to .bak and tried with no ansi file as well as with a custom one.

-=>Richard Miles<=-
-=>Captain Obvious<=-
-=>bbs.shadowscope.com<=-

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (21:1/157)