-
Notifications
You must be signed in to change notification settings - Fork 278
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
Update to 0.2.9 makes medusa fail to start ext/adba no module named configparser #5137
Comments
@sharkykh eeh i included backports? |
How do you start medusa? |
@p0psicles Possibly related... Old |
I start medusa as a systemd user service. Python version is 2.7.15 Not old pyc files (I moved my old install directory and cloned a brand new directory to test before I posted the issue...that had the same problem, so then I checked out the previous release and everything works again) |
Here is the unit file that I use to launch Medusa as a systemd user service. You can see the options that I pass to Medusa in the ExecStart line, in case that is relevant to the issue. [Unit] [Service] Type=forking [Install] |
I was just able to reproduce... kind of. I removed
from pkgutil import extend_path
__path__ = extend_path(__path__, __name__)
|
I git cloned a new copy from Master and then checked the file:
Looks okay to me. I changed my systemd unit file as shown:
Same problem, here is the systemd log on attempted start:
|
I also tried launching it from the command line, to eliminate any unknown systemd interactions. Same error:
|
@jtwill |
Well done! commit 9068899 fixed the issue and Medusa is running fine for me now at release v0.2.9 + that commit. |
Thank you for helping to debug this! Hopefully we'll be able to fix master soon. |
Hmm, just upgraded Medusa and ran into this problem, any idea when it will be in the master branch? |
Well hotfix it. In the mean time, please try to use the branch @sharkykh provided. I think we should be able to release a hotfix by tomorrow. |
@p0psicles @sharkykh Still can't start Medusa after a pull
|
Seriously Python? What now? @Rouzax On a side note, I never really run Python scripts like that, can you try running it like this? |
The compiled python could be the case, will give it a try when I have the chance. Also tested with python.exe but with the same result. |
@sharkykh, that did not help
|
It looks like my git pull was not working because it saw local files (that I didn't create and I've always been on Master)
After doing the following it works.
During start it still gives
But it now works. |
Good to know, thanks :) Edit: Actually I was just able to confirm that's exactly the case. |
@sharkykh you're absolutely right, I had Subliminal installed and forgot about it. BTW: Is there a list pf current python modules Medusa is depended on? |
You're welcome.
It's possible a
Medusa still vendors all of its dependencies. Note: The lists are from the |
thanks, I'm thinking about clearing out my Python installation as it has been around and upgraded since Sickbeard. |
Describe the bug
I upgraded to 0.2.9 from 0.2.8 and Medusa would no longer start. The problem seems to be
related to adba. It tries to load an external module configparser import ConfigParser but it fails
to find the module and exits.
To Reproduce
Start medusa after upgrading to 0.2.9
Expected behavior
Medusa should start as usual instead of failing and exiting.
Medusa (please complete the following information):
Logs:
Additional context
I'm guessing the problem is related to this adba commit:
#4822
The text was updated successfully, but these errors were encountered: