Good afternoon Gents,

I've recently setup a dedicated Debian Linux 10 server for Mystic BBS. I installed everything using apt-get and did not custom compile anything. My Mystic system is running extremely well and no issues have been encountered with the standard configuration, however when attempting to add any add-ons such as ThreatSentry, as one example, I'm unable to execute the Python script.

I recieve the following error message during login to Mystic (being called
from the "startup.mpx" script for ThreatSentry. (This occurs for all custom python scripts)

Error seen prior to logging into the BBS:
Python 2.7 32-bit not detected, press a key.

'sudo apt-get install python' shows the following output:
"python is already the newest version (2.7.16-1)

I'm assuming by default Debian Linux 10 installs Python 64-bit instead of Python 32bit.

Can someone inform me the best way to deal with this? I would like run these Python add-ons for Mystic, the system is dedicated to Mystic only so I have
no concerns running Python 32-bit, however I honestly don't know the proper resolution.

Thanks in advance for your anyone's assistance with this!

-Dejavu

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/32)
* Origin: 1984 BBS | 1984BBS.NET | Washington, DC (21:3/114)

Good afternoon Gents,

...is this a boys' club thing?

Error seen prior to logging into the BBS:
Python 2.7 32-bit not detected, press a key.

Did you follow the directions on the mysticbbs wiki? wiki.mysticbbs.com/doku.php?id=python_install

There's even a bit about Ubuntu issues that can sometimes crop up. I used it, though I don't know if it solved my issue (and I also wound up on 2.7.18
rather than 2.7.15).

Beyond that, I'd be inclined to run "which python" and see what comes up, if
I was trying to diagnose the problem.

For me, the problem that I got stuck on the longest was getting Python to
_do_ anything, rather than just not give errors. And I think that was caused
by having scripts in the old location, rather than under the themes directory structure.

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Storm BBS (21:2/108)

On 16 Jun 2020, Adept said the following...

Good afternoon Gents,

...is this a boys' club thing?

My apologizes, good evening Ladies :) I'll correct that moving forward.

Error seen prior to logging into the BBS:
Python 2.7 32-bit not detected, press a key.

Did you follow the directions on the mysticbbs wiki? wiki.mysticbbs.com/doku.php?id=python_install

Apparently not well enough. I'll go back and RTFM once again.

There's even a bit about Ubuntu issues that can sometimes crop up. I
used it, though I don't know if it solved my issue (and I also wound up
on 2.7.18 rather than 2.7.15).

That's my first issue, I choose to use Debian 10 verus Ubuntu...

Beyond that, I'd be inclined to run "which python" and see what comes
up, if I was trying to diagnose the problem.

'which python' isn't very helpful, output is:
'/usr/bin/python'

For me, the problem that I got stuck on the longest was getting Python to _do_ anything, rather than just not give errors. And I think that was caused by having scripts in the old location, rather than under the
themes directory structure.

I resolved the issue of /mystic/scripts, versus where they should be in /mystic/themes/default/scripts/ a few days ago. I don't understand why all
the instructions indicate you put the scripts in /mystic/scripts/? It
doesn't help the new Mystic users. Unfortunately moving the scripts to the proper scripts directory doesn't resolve the issue of the scripts not
executing at all. In my case the system is screaming there is no Python installed.

Thanks for the response, I'll RTFM again and see if there is something I overlooked.

-Dejavu

Ad> --- Mystic BBS v1.12 A45 2020/02/18
(Linux/64) Ad> * Origin: Storm BBS (21:2/108)

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/32)
* Origin: 1984 BBS [1984bbs.net] Washington, DC (21:3/114)

'which python' isn't very helpful, output is:
'/usr/bin/python'

How about python --version? Mostly I'm wondering if it's going to a Python 3 install or something.

Other than that, I was wondering if you had the various files mentioned on
the wiki, since that's my next best guess. Or had 32-bit Mystic with 64-bit python, etc.

/mystic/themes/default/scripts/ a few days ago. I don't understand why all the instructions indicate you put the scripts in /mystic/scripts/?
It doesn't help the new Mystic users. Unfortunately moving the

Yeah. The change happened when going from A44 to A45, and since it's mostly just g00r00 with editing access, it's something that'd take time to deal
with, and he's working on various development issues.

I'd certainly edit some minor wiki entries if I had access, but I imagine
it'd probably be more hassle than it's worth to add users who might do light changes.

Thanks for the response, I'll RTFM again and see if there is something I overlooked.

Good luck!

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Storm BBS (21:2/108)

On 16 Jun 2020, Adept said the following...

'which python' isn't very helpful, output is:
'/usr/bin/python'

How about python --version? Mostly I'm wondering if it's going to a
Python 3 install or something.

Re-reading the RFTM helped. I have to be completely honest the problem is
now resolved, however I don't know what the root cause was. I fixed it using the information on the URL you provided.

I ran 'ldconfig -p | grep libpython' and nothing returned.

I ran 'sudo apt-get update && sudo apt-get install libpython2.7' and then looked at 'ldconfig -p | grep libpython' again and saw it on the system.

I enabled one of the python scripts that wasn't running and it came to life.

Thank you for pointing me back to that wiki reference, I really appreciate
it. I wish I knew what the problem is, however I'm not going to spend a
bunch of cycles on it and if I am going to go down that path I'm going to identify the requirements for the python scripts next time to understand if I should be installing Python 32 or Python 64, as well as Ubuntu or Debian
Linux and start over. (In worst case scenerio)

Other than that, I was wondering if you had the various files mentioned
on the wiki, since that's my next best guess. Or had 32-bit Mystic with 64-bit python, etc.

/mystic/themes/default/scripts/ a few days ago. I don't understand w all the instructions indicate you put the scripts in /mystic/scripts/ It doesn't help the new Mystic users. Unfortunately moving the

Yeah. The change happened when going from A44 to A45, and since it's mostly just g00r00 with editing access, it's something that'd take time to deal with, and he's working on various development issues.

I'd certainly edit some minor wiki entries if
I had access, but I imagine Ad> it'd probably be more hassle than it's worth to add users who might do Ad> light changes.


I agree that would be a good thing for some other folks to have access to in order to keep things updates. A lot of times the folks that originally
wrote it won't necessarily be doing it again on a new version and then folks will be following improper directions. I am seeing that as a very common thread with everything I've done so far, and my documentation for what I have done to overcome it is null. :/ I would be one of those persons updating
the information as well.

Thanks for the response, I'll RTFM again and see if there is somethin
overlooked. Ad> Ad> Good luck! Ad> Ad> --- Mystic BBS v1.12 A45

2020/02/18 (Linux/64)

* Origin: Storm BBS (21:2/108)

Thanks again for the save!

-Dejavu

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/32)
* Origin: 1984 BBS [1984bbs.net] Washington, DC (21:3/114)

Adept,
Completely different topic and probably should go to another message area,
can you let me know how I can request all the mail from hub for a specific
time period?

I'm new here so I only have a couple hundred messages on my board, however
when I log into other boards there are thousands of messages in some of the fsxnet areas that I haven't seen.

I'd like to pull down all the mail that's available. I've read the RTFM 25 times and I don't know what I'm doing wrong. I thought it was the %RESCAN request but I must not be holding my head the right way or something :)

-Dejavu

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/32)
* Origin: 1984 BBS [1984bbs.net] Washington, DC (21:3/114)

Re-reading the RFTM helped. I have to be completely honest the problem
is now resolved, however I don't know what the root cause was. I fixed
it using the information on the URL you provided.

Yeah, I was pretty much the same when I managed to make it work. I know it
was one of a set of things, but figuring out exactly what in that set was necessary just doesn't seem worth it.

Regardless, I'm glad you got it working. And, realistically, it's probably,
"go find that wiki page again and follow the directions. And make sure the script directory is the right one." appears to be a fairly decent plan for
the time being.

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Storm BBS (21:2/108)

Completely different topic and probably should go to another message
area, can you let me know how I can request all the mail from hub for a specific time period?

I don't know. I had kind of assumed that it didn't work that way -- that you get a feed, and the feed saves various messages for your BBS, and you poll
for it.

I wouldn't doubt that there'd be a way to get them all in there somehow (I mean, if you can use QWK to get messages from a BBS, and can import QWK packets, I'd assume that you could combine those to get all the messages onto
a BBS.).

25 times and I don't know what I'm doing wrong. I thought it was the %RESCAN request but I must not be holding my head the right way or something :)

Yeah, sadly I'm no help. :) Not something I've tried to do. Heck, I already wonder about the 10k messages in the general sub and if I should do anything about that.

But I've barely messed around with messages, beyond getting things setup for FSXnet and FIDOnet. Hopefully someone else can chime in.

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Storm BBS (21:2/108)

Re: Re: Debian Linux 10 w/Python 64-bit - Mystic scripts require Python 32
By: dejavu to Adept on Tue Jun 16 2020 12:39 am

Hi Jeff,

I'd like to pull down all the mail that's available. I've read the RTFM 25 times and I don't know what I'm doing wrong. I thought it was the %RESCAN request but I must not be holding my head the right way or something :)

I can help you with that - each hub is different. But I'm your hub, so I can give you specifics. :)

I did netmail you - hopefully you saw it. I saw messages from you to 21:3/10 (which doesnt exist) - and they looked like areafix messages. You should be addressing them to areafix@21:3/100, with your password as the Subject.

In the body of the message, you can put your commands - %HELP will give you a help message.

%RESCAN is the command to "resend" message, and here is the except from the help:

%RESCAN 541.LOCAL <- Rescan area
%RESCAN OS2.* <- same
%RESCAN linux.develop.ger 200 <- Rescan the last 200 mails
%RESCAN linux.develop.ger 30 days <- Rescan mails for last 30 days

Yell out if you are stuck...

...δεσ∩

... I broke a mirror & got 7 years of bad luck; my lawyer thinks he can get me 5.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)