1. Forum
  2. FSXNet
  3. FSX MYS

  • Can't Initialize Python

    From mobbyg@21:1/101 to All on Thu Mar 25 14:10:24 2021
    Python was working up to a couple days ago. I was able to run my scripts, but now, I get "Can't initialize Python".

    I'm running A47 on a Pi3 with the latest Raspbian.
    I didn't have the paths to Python in the settings before, and it ran fine.
    Then this error. I added the paths and still get it. I have rebooted the Pi, and checked the log, which shows nothing.

    The only thing that has changed is I started setting up fsxNet. Anyone have
    any thoughts?

    |04---- |15Rich Lawrence, KB2MOB
    |14//// |15SysOp of Radio Freqs & Geeks BBS
    |01--v|10/// |07-Ham/Shortwav Radio, Tabletop Gaming and General Geekery- |11\\|02xx/ |08mobbyg@gmail.com

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From xqtr@21:1/111 to mobbyg on Thu Mar 25 09:13:29 2021
    I'm running A47 on a Pi3 with the latest Raspbian.
    I didn't have the paths to Python in the settings before, and it ran fine. Then this error. I added the paths and still get it. I have rebooted the P

    A47 needs the complete path+filename for the files libpython2.7.so and libpython3.8.so (or what ever version you use). Make sure you have the correct ones.

    For example in my system i have these two paths:
    /usr/local/lib/libpython2.7.so
    and
    /lib/x86_x64-linux-gnu/libpython3.8.so

    :: XQTR :: Another Droid BBS :: andr01d.zapto.org:9999 :: xqtr@gmx.com

    --- Mystic BBS v1.12 A47 2020/11/23 (Raspberry Pi/32)
    * Origin: Another Droid BBS # andr01d.zapto.org:9999 (21:1/111)
  • From bcw142@21:1/145 to mobbyg on Thu Mar 25 04:54:33 2021
    On 25 Mar 2021, mobbyg said the following...

    I'm running A47 on a Pi3 with the latest Raspbian.
    I didn't have the paths to Python in the settings before, and it ran
    fine. Then this error. I added the paths and still get it. I have
    rebooted the Pi, and checked the log, which shows nothing.

    First check the path in General it should show what's after the => when you type at the command line:
    ldconfig -p | grep libpython
    That needs to match and many things take a restart of mystic, That isn't a total reboot, on command line in mystic root type:
    sudo killall mis #wait a few seconds for it to shutdown then
    sudo ./mis daemon #or whatever you normally start it with,
    Then there is a test script (*,mpy) in scripts you can try or whatever you normally run in python under mystic (Mystic-DOS can run that from scripts).

    --- Mystic BBS v1.12 A47 2021/02/12 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)