-
-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Not all required Python modules are available" - "Missing module: None" #1984
Comments
|
Do you have the requirements installed for py3.6 but not py3.10. just install them for 3.10? (Use pip3.10 alias so you Target the correct site install dir) |
|
And if you have multiple pythons installed make sure your setting/using the one you actually want. Lots of way to do this for better or worse. And to do it outside of system python |
|
I uninstalled Python 3.10, right now there's only 3.6 installed. sabnzbd is not starting, as explained above. This is NOT about getting sabnzbd to run with 3.10, but about it failing to start with 3.6. |
|
Install the requirements? Use ppa? |
|
and just fyi, if your trying to run from git/source |
|
@anonvoy It seems something else is indeed wrong. But to know what, we need to know the whole error. print("Missing module:", e.name)With: print(e) |
@Safihre I did that, and now the error message reads: I meanwhile have tried to install python 3.10.0 with pyenv as suggested above, and that worked. Also the import of the required modules, starting sabnzbd, updating to the latest commit and running sabnzbd with it. It's been running for several hours now, and everything seems to be ok. The only error messages I get are those regarding server SSL ciphers already discussed in another issue and worked on. So thanks to @thezoggy for the tip. I still can't get it to start with my system python 3.6.12, something's apparently broken there. But since I got it to run with pyenv-python 3.10.0, I'd still like to know what's wrong, but it's less important now. |
|
Py3.6 is not supported for latest code. It will toss up verbiage saying so |
I know. That's why, as I wrote at the very beginning of this issue, I'm on commit 0d29603 when running sabnzbd with python 3.6.12, the last commit that will run with 3.6 and won't toss up said verbiage. |
|
The FWIW: no problem on my old Ubuntu with python 3.6: |
|
We artificial stopped supporting 3.6 with our version check. None of the actual modules we use dropped 3.6 that I'm aware of. |
guessit is version 3.4.3 installed by pip. |
|
Ah, yes Guessit broke 3.6 compatibility in one the 3.4.x releases. See here: guessit-io/guessit#715 Maybe try an older guessit, |
I can't get sabnzbd to start anymore. I'm running it from source, have done so for years, and I'm on commit 0d29603. That's the last commit working with Python 3.6, and I'm on that because my OS is OpenSUSE Leap 15.2, where the official Python 3 version is 3.6.12. (Same on Leap 15.3 btw.)
I had installed Python 3.10 from some SUSE python repository, but couldn't get sabnzbd to run with that because of missing modules from the requirements list. There was no pip for that Python 3.10, so I could not install them like described at https://sabnzbd.org/wiki/installation/install-off-modules, and I don't know any other way. (A symlink perhaps, but there's no point in trying that now when the program won't start.)
With Python 3.6, sabnzbd started and ran fine all the time, until I made the apparent mistake of running python3 -m pip install -r requirements.txt -U again as described. pip installed several modules, and then I couldn't get sabnzbd to start any more. I start it as usual with python3 ~/.sabnzbd/SABnzbd.py -d -f /home/abc/.sabnzbd/sabnzbd.ini (plus a & at the end if starting in a shell), and the result I get is:
So something is happening very early. All the required modules are there, and if I remove any of them for testing purposes, the error message changes and says that the removed module is missing. I did remove all the .pyc files as suggested, didn't help. I've removed all of the required modules and added them back, and I have most of them in the linux distribution's version now, except for a few like sabyenc that I had to get with pip. That also didn't help, sabnzbd still does not start. A system reboot did not help either.
So my guess is that something is wrong with the Python modules, but I don't know what it is. The last log entries are reflecting the time sabnzbd was still running normally. I do have an sabnzbd.error.log from the first time the start failed (after pip going through requirements.txt), and that says:
I'm not quite sure what is causing the problem or how to proceed. Any suggestions? Any way to get more helpful messages, logs etc.?
The text was updated successfully, but these errors were encountered: