Sickchill: Local branch is ahead of master. Automatic update not possible.

Created on 6 Sep 2020  ·  80Comments  ·  Source: SickChill/SickChill

Branch/Commit: master/99336df163c7e776c7931d864e84d1f0f83afe4d
OS: Raspibian
Browser: Safari
What you did: Try to update
What happened: Local branch is ahead of master. Automatic update not possible.
What you expected: update
Logs:

2020-09-05 19:36:01 WARNING WEBSERVER-HOME :: Local branch is ahead of master. Automatic update not possible. 2020-09-05 19:35:58 INFO WEBSERVER-HOME :: Checking for updates using GIT
Fixed Question

Most helpful comment

Also, please forgive me if I seem short over the next few days. I will be helping hundreds of users and trying to get all of our packages updated while taking care of a 1 month old baby :neckbeard:

All 80 comments

Issue-Label Bot is automatically applying the label Bug / Issue to this issue, with a confidence of 0.89. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

Have you tried reading the news in the past week?

Python3 code has been merged into master. I intentionally created a continuity break in the commit history with a force push so that users would not be automatically updated to python3 code while their service files were pointing to python2 (which would cause it to not even start up)

The python2 code still works, but will receive no more updates.

This way, users can stay on python2 until they manually intervene and get everything working on python3 because the updater will refuse to update.
This also gives time for 3rd party maintainers to update their respective apps for specific devices.

Synology is being updated as we speak, there is a new Windows installer already, git will still work (but it is no longer the preferred install method)

Ideally we can get all users switched over to a pure pip install or using docker and eliminate a ton of issues, because everyone will have a system operating the same way.

If someone needs some specific help feel free to ask.

If anyone would like to help updating the wiki with new information, as well as a new page specifically for this situation that would be appreciated.

Also, please forgive me if I seem short over the next few days. I will be helping hundreds of users and trying to get all of our packages updated while taking care of a 1 month old baby :neckbeard:

Well I hadn't run SickChill in a week and imagine my surprise when it failed to work and I found your pointer to the news with an age of 48mins. As glad as I am for the move to python 3 I did not have a straightforward upgrade using the SickChillInstaller you just posted, I'll post about the issues there. I hope the errors were of my own making and as daft as it sounds I couldn't find the discord url anywhere, not even in the Wiki or FAQ.

PS congratulations on the baby.

current window installer downloads a portable version of git and installs to a temp folder then tries to run from C:\SickChill\git and fails with file not found. using installer .55

@snapperhead windows installer is fixed 0.5.7

@snapperhead windows installer is fixed 0.5.7
wont start after install i dont think python install is ending up in sickchill dir as it looks like thats where its expected to be.

@snapperhead windows installer is fixed 0.5.7
wont start after install i dont think python install is ending up in sickchill dir as it looks like thats where its expected to be.

Have a look here.
https://github.com/SickChill/SickChillInstaller/issues/27
This was for the first updated installer I 'used' 0.5.4
It might be the python path or it might be that the nssm service needs editing.
W̶h̶e̶n̶ ̶y̶o̶u̶ ̶f̶i̶g̶u̶r̶e̶ ̶o̶u̶t̶ ̶w̶h̶i̶c̶h̶ ̶i̶t̶ ̶i̶s̶ ̶p̶l̶e̶a̶s̶e̶ ̶p̶o̶s̶t̶ ̶a̶n̶ ̶i̶s̶s̶u̶e̶ ̶o̶n̶ ̶t̶h̶e̶ ̶S̶i̶c̶k̶C̶h̶i̶l̶l̶I̶n̶s̶t̶a̶l̶l̶e̶r̶ ̶p̶a̶g̶e̶ ̶
̶h̶t̶t̶p̶s̶:̶/̶/̶g̶i̶t̶h̶u̶b̶.̶c̶o̶m̶/̶S̶i̶c̶k̶C̶h̶i̶l̶l̶/̶S̶i̶c̶k̶C̶h̶i̶l̶l̶I̶n̶s̶t̶a̶l̶l̶e̶r̶
0.5.7 works 100% (so long as you haven't installed python3 manually, if so uninstall python3 first).

It might be the python path or it might be that the nssm service needs editing.
When you figure out which it is please post an issue on the SickChillInstaller page
https://github.com/SickChill/SickChillInstaller

turns out it didn't like my existing install of python3 once i uninstalled python3 and re-ran installer everything is up and running now.

Just wanted to confirm that Installer v0.5.7 worked for me no problems. I am running on Windows 10 v2004

Here is my full process.

  1. Stop SickChill service.
  2. Backup everything in C:\SickChill to C:\SickChill.old
  3. Add / Remove Programs and uninstall SickChill (Do not delete your database and settings)
  4. I confirmed the only thing remaining in C:\SickChill was my Data folder
  5. Run SickChillInstaller.exe v0.5.7

The installer restarted my service and I confirmed it is running again, and I confirmed that embedded Git and Python are in C:\SickChill

I've been testing 0.5.7 with miigotu on discord and I too failed to uninstall my existing python 3 which causing the install to fail. I then doubled down and uninstalled SickChill which broke python so I had to run a repair before uninstalling.

Also there is one current gotcha wrt the image cache location changing (posters and banners and backgrounds).
old location was
C:\SickChill\Data\gui\slick\cache\images
new location is
C:\SickChill\SickChillsickchill\gui\slick\cache\images
The solution is to either copy the contents of \images and \images\thumbnails to the new location or run a Mass Update on all shows to redownload them.

Also there is one current gotcha wrt the image cache location changing (posters and banners and backgrounds).

Thanks for this I had not noticed it yet.

It made more sense to me to have this in the old Data folder and not under the repository folder.... I will move mine, but can any of the Devs confirm if this is intentional?

No it is supposed to be symlinked into the data folder, but I'm exhausted so I'll get to it when I can lol

A baby always comes first! Enjoy him or her, sleep (if you are allowed) and SC comes last ...

Just wanted to confirm that Installer v0.5.7 worked for me no problems. I am running on Windows 10 v2004

Here is my full process.

  1. Stop SickChill service.
  2. Backup everything in C:\SickChill to C:\SickChill.old
  3. Add / Remove Programs and uninstall SickChill (Do not delete your database and settings)
  4. I confirmed the only thing remaining in C:\SickChill was my Data folder
  5. Run SickChillInstaller.exe v0.5.7

The installer restarted my service and I confirmed it is running again, and I confirmed that embedded Git and Python are in C:\SickChill

Just followed those steps but no folder C:\SickChill\Python3 was created, because I already have Python 3.8 installed on my system (I think) and I cannot uninstall it since I have other things that rely on this default installation. I had to copy the folder from C:\Python38 to C:\SickChill\ and rename it to C:\SickChill\Python3 to get the service to start.

when you say synology is being updated as we speak, do you mean Docker? And will it be as simple as updating docker itself or is there more we need to do with linuxserver-sickrage? Please help those like myself with Docker/linuxserver-sickrage and what we need to do instructions wise somewhere. I myself have python3 installed on my synology but not sure what else needs to be done. thank you!

Love your work @miigotu
Get some sleep!!!

@miigotu FYI - I tried the windows installer yesterday, but it failed because I already had SC installed. There was no uninstaller. Just wanted to mention it since you're referring to the installer earlier.

@Tiwas You did not have it in your Windows Settings -> Apps -> Apps & Features list?
I can find it there and click the Uninstall button.

On my current system I have only ever installed via some form of the SickChillInstaller.exe - maybe you are different.

@Tiwas You did not have it in your Windows Settings -> Apps -> Apps & Features list?
I can find it there and click the Uninstall button.

On my current system I have only ever installed via some form of the SickChillInstaller.exe - maybe you are different.

@havoc77 It's in the list, but it refers to an uninstall executable that doesn't exist.

having issues getting the new installer to work:

pip install sickchill
Defaulting to user installation because normal site-packages is not writeable
ERROR: Could not find a version that satisfies the requirement sickchill (from versions: none)
ERROR: No matching distribution found for sickchill

I checked my python3 version and it set to 3.5.2 which should work...

I have no idea about Python version compatibility and have never used pip... but but in the news page of my SickChill server from 2020-08-06 it says:

Make sure you have python3.5+ installed on your system. There are tons of changes already, all for the better.

A newer post from 2020-08-31 says

I am going to do my best to wait a week from today before I merge develop to master.
When this happens, if you are using docker, pip, etc everything will be seemless.

For everyone else, make a backup first, as you may need to restore the backup after manually updating and you do not want to lose any data.

If you are using git install, your updater is going to fail/error and you will need to make sure you have python3.6+
installed and manually update your service file to use python3, and then do a git pull.
Source installs will need to have python3.6+ installed and update your service file, and copy in the new source manually.
A windows installer update will be released, that uses pip as the base install. Windows will need to uninstall and reinstall with the new installer.

The newer post does mention python3.6+ though, if that helps?

updated to python3 to 3.8.5, and still not working

@FGOD1983 your pip is still using python2.7 (pip -V will show this)

Check pip3 -V

pip3 install -U sickchill

@Manfred73 BenJV took the python3 package down to fix it. You don't do anything manually on syno
https://github.com/SickChill/SickChill/issues/6697

@Manfred73 BenJV took the python3 package down to fix it. You don't do anything manually on syno

6697

So when this is fixed, all I need to do is install the package? And this will then install new version of sickchill with Python3 and also convert the old db?

The db does not need converted. It will install SC with python3 and use your existing data (make a backup just in case of your db and config.ini ALWAYS)
You might need to uninstall the old package and install the new one

@cbinder4 you can move them, it is a bit different on windows and I was tired. Either you copy them or they will be re-cached in 24 hours.

The message is just telling you that I intentionally made the updater error that way so that it did not automatically update you and break your install all by itself.

For SickChill on Synology sickbeard-custom is no longer a viable package. We run strictly under python3.6+ now.

Stay with the current version you have until the new syno package is made/merged, directly on synocommunity.
https://github.com/SynoCommunity/spksrc/pull/4161

If that package is not merged soon, I will again provide a package right in our Org.

You could go there and like/comment on the PR, or contact Synology maintainers by other means (forums?) And ask for it to me merged.

The message is just telling you that I intentionally made the updater error that way so that it did not automatically update you and break your install all by itself.

For SickChill on Synology sickbeard-custom is no longer a viable package. We run strictly under python3.6+ now.

Stay with the current version you have until the new syno package is made/merged, directly on synocommunity.
SynoCommunity/spksrc#4161

If that package is not merged soon, I will again provide a package right in our Org.

You could go there and like/comment on the PR, or contact Synology maintainers by other means (forums?) And ask for it to me merged.

Thank you so much @miigotu . So I do nothing and I wait and I update the SickBeard Custom Package whenever it is available on Synocommunity. Crystal Clear !

Thank you so much @miigotu . So I do nothing and I wait and I update the SickBeard Custom Package whenever it is available on Synocommunity. Crystal Clear !

You will install the "sickchill" package by Nyaran once it is merged.

Make sure you make a backup from the old install, and restore it in the new install.

@Manfred73 no, it is not a replacement for SC. It is a different fork and we do not talk about competing forks here.

Thank you so much @miigotu . So I do nothing and I wait and I update the SickBeard Custom Package whenever it is available on Synocommunity. Crystal Clear !

You will install the "sickchill" package by Nyaran once it is merged.

Make sure you make a backup from the old install, and restore it in the new install.

OK clear, thanks.
By The Way, could you please tell me how to backup the Settings (I believe the Config.ini). Where do I find this file ?

OK clear, thanks.
By The Way, could you please tell me how to backup the Settings (I believe the Config.ini). Where do I find this file ?

Use Sickchill backup function under settings.

OK clear, thanks.
By The Way, could you please tell me how to backup the Settings (I believe the Config.ini). Where do I find this file ?

Use Sickchill backup function under settings.

I understand this saves the DB but we need to save the setting too don't we ?

I understand this saves the DB but we need to save the setting too don't we ?

It backs up the DB yes. It also backs up the
sickchill.db
config.ini
failed.db
cache.db
And lots of image files.

And movies.db if you have it =P

Syno package built for testing: https://github.com/SynoCommunity/spksrc/pull/4161#issuecomment-690940177

@FGOD1983 your pip is still using python2.7 (pip -V will show this)

Check pip3 -V

pip3 install -U sickchill

thanks for this I upgraded without issues

htpc@htpc-media-server:/opt/sickchill$ sudo service sickchill status
● sickchill.service - SickChill Daemon
     Loaded: loaded (/etc/systemd/system/sickchill.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2020-09-12 20:08:43 EDT; 5s ago
    Process: 2841513 ExecStart=/usr/bin/python3.8 /home/htpc/.local/bin/SickChill.py --daemon --nolaunch --datadir=/opt/sickchill (code=exited, status=0/SUCCESS)
      Tasks: 15 (limit: 9451)
     Memory: 108.3M
     CGroup: /system.slice/sickchill.service
             └─2841520 /usr/bin/python3.8 /home/htpc/.local/bin/SickChill.py --daemon --nolaunch --datadir=/opt/sickchill

Sep 12 20:08:40 htpc-media-server systemd[1]: Starting SickChill Daemon...
Sep 12 20:08:43 htpc-media-server systemd[1]: Started SickChill Daemon.
Sep 12 20:08:43 htpc-media-server python3.8[2841520]: /home/htpc/.local/lib/python3.8/site-packages/sickchill/locale
Sep 12 20:08:43 htpc-media-server python3.8[2841520]: /home/htpc/.local/lib/python3.8/site-packages/sickchill/locale
Sep 12 20:08:43 htpc-media-server python3.8[2841520]: /home/htpc/.local/lib/python3.8/site-packages/sickchill/locale

ok so I will have to find out how I installed sickchill on Syno and then do it again once you awesome guys complete it. thank you :)
I did the BenjV install last time and then again for dsm 6 (I had lost everything and had to do it again) I will look for the tutorial again.

ok so I will have to find out how I installed sickchill on Syno and then do it again once you awesome guys complete it. thank you :)
I did the BenjV install last time and then again for dsm 6 (I had lost everything and had to do it again) I will look for the tutorial again.

Oh I see the new spk, i will install that after the I update my python. Thank you.

ok so I will have to find out how I installed sickchill on Syno and then do it again once you awesome guys complete it. thank you :)
I did the BenjV install last time and then again for dsm 6 (I had lost everything and had to do it again) I will look for the tutorial again.

Oh I see the new spk, i will install that after the I update my python. Thank you.

Backup it up.
deleted older Chill
used spk mentioned above.
install and run (took time)
restored
profit
???

Thank you you guys, too this slow guy some time but I got it.
And congrats on the baby, I have a pandemic baby too. having kids in this time is tough. respect.

oke, to fix my issues with python I took the easy way and reinstalled my whole server.

I'm getting to the point now that the install worked of sickchill and it is now installed in .local/lib/python3.8/site-packages/sickchill (?) after doing the pip3 install -U sickchill command... but I can't seem to find the service yet and what files do I need to take from my old install and move to the new location in order to get everything back to the old state?

When you install with pip you have to edit one of the service files in contrib and install the service. It is not automatically set as a service (pip support is brand new for us)

That was what i was thinking, as that is the normal way, but there is no contrib folder in the SickChill folder under .local/lib/python3.8/site-packages/sickchill
Screenshot_20200914-203854

Thx, maybe I'm a bit slow here, but I still miss a lot of files in this folder... Should the whole thing still run from my old /opt/sickchill folder? Or from the new folder under the python directory? Because in the python directory I don't have the db files and SickChill.py as you can see in my picture...

Am I missing something? Should I copy over my old folder to the new python location?

Oke, got it working again from the /opt/SickChill directory and restored my setup from there.

But pure out of curiosity, what is the python SickChill folder used for, if the main data dir that still updates and holds the program/data files is used by the systemd service?

Thx for the help and your patience btw 🙂

You need to edit the systemd service to work with a pip install. By default SC uses a datadir in the home dir of the user running it (~/sickchill)

I saw this zip https://github.com/SynoCommunity/spksrc/files/5213640/sickchill_noarch-all_20200913-0.zip
But this is not the finished version yet? Or is this one safe to install already? I didn't see any update in the Syno Community yet. Better to wait for that one?

_UPDATE 1:_
I notice a new 1.0 version from BenJV so backed up with a script I use: it creates a tar.gz file with all the content from SICKCHILL_FILES_TO_BACKUP.

APPSTORE_LOCATION='/volume1/@appstore'
BACKUP_LOCATION="/volume7/Backup/SYNOLOGY"

SICKCHILL_PATH="$APPSTORE_LOCATION/sickchill/var"
SICKCHILL_BACKUP_PATH="$BACKUP_LOCATION/SickChill"
SICKCHILL_PREFIX="SickChill"
SICKCHILL_FILES_TO_BACKUP=("$SICKCHILL_PATH/config.ini" "$SICKCHILL_PATH/cache.db" "$SICKCHILL_PATH/sickbeard.db" "$SICKCHILL_PATH/cache" "$SICKCHILL_PATH/failed.db")

Then uninstalled the old 1.2 package, reinstalled the new 1.0 with Python 3.

After that I ran the restore script which extracts everyting from the backup tar.gz file to the same locations.

Then started SickChill, but it didn't start. The sickchill.log shows the following:

2020-09-25 21:46:56 ERROR :: MAIN :: Fatal error executing query with db.action in database /volume1/@appstore/sickchill/var/cache.db: near "?": syntax error`

So I restarted the Synology, now SickChill starts, and the config seems to have been restored from the backup, but all the shows are gone.

What am I missing here? I noticed in the previous version of sickchill 1.2 it was named sickbeard.db, but the new version is named sickchill.db. Can I just rename my old sickbeard.db to sickchill.db? What about the cache.db (that's what the error message complains about).

_UPDATE 2:_
I guess I just answered my own question ;-) Renaming sickbeard.db to sickchill.db: and there are my shows again. Not sure why it complained about cache.db though. Also, what is sickchill.db.v44 used for?

@Manfred73 https://github.com/SynoCommunity/spksrc/pull/4161 is done they just haven't merged it yet.

For those interested in a generic update/restore script for some of these applications like SickChill that you have running on your Synology: https://github.com/Manfred73/SynologyBackupRestoreScripts.

@miigotu So we need the new package available (merged) in SynoCommunity repo or can it be installed already manually? Thanks!

You can wait until de package is available on SynoCommunity, or install manually the package. Is provided on PR's first post.

I did the upgrade now as average user ;) and may be it helps:

  • create backup file with SickBeard Custom UI
  • uninstall SickBeard Custom app with DSM UI
  • download version from PR#4161 by @Nyaran (sickchill_noarch-all_20200920-0.tar.gz)
  • extract sickchill_noarch-all_20200920-0.spk from above .tar.gz
  • install spk with DSM UI (manual install) with no changes to the options
  • open SickChill UI with provided link after SickChill was automatically started (port 8081)
  • restore the backup file with SickChill UI
  • [optional] verify with SSH that files where copied to /volume1/@appstore/sickchill/var/data/restore
  • restart SickChill --> it shows shutdown succeeded, but stuck at start
  • open the link with port 8083 (like was in the previous config.ini) and SickChill is there :)
  • change the port to 8081 to have the valid link from DSM
  • the database was restored with new name sickchill.db --> no need to rename from sickbeard.db manually

Now i see all the shows in SickChill but the posters (images) are not there, only this sickchill image instead:
image
How can i solve this? Thanks!

@miigotu So we need the new package available (merged) in SynoCommunity repo or can it be installed already manually? Thanks!

I did it manually last week. Got the spk from BenjV

Do not use benjv package, or promote it here. We have an official package ready to be merged into synocommunity with real commit and change history.

@anb0s force refresh on all shows or wait for the show updater to run. All images will be back within 24 hours.

@miigotu thanks, "Mass update"--> select "Update" for all shows --> "Submit" and now images are updated :)

Is there a documented procedure for properly updating from git? I'm on master right now and still seeing the update message.

I had this problem; I went the manual method because I'm installed directly into Linux (Ubuntu) My process was simply:

  • backup system using WebUI backup method
  • stop SickChill
  • uninstall SickChill using method documented in Wiki (moved install folder for additional backup in case of stuff going sideways)
  • installed using manual method (also in Wiki)
  • once started, restore from backup (SickChill required a restart)
  • small exception: restart failed from web - sickchill restarted, but webUI was not responsive, required restarting again from Command line (SSH in my case).
  • mass update meta data

Afterwards, everything is working normally and as expected.

I'll note that I did this because the old version I was running would not update metadata for new episodes; this has been an ongoing problem that I haven't found time to do a root-cause analysis on; however, once updated, one of the problematic series, that never seemed to update metadata automatically, was able to update metadata; though it was manual in this case, it's a good sign.

Thanks everyone who posted in this bug, I hope my comment helps someone else moving forward.

I apparently lost my previous post somewhere, trying again.

I wanted to chime in and thank @MystikIncarnate for the nudge in the right direction.
In the end, backup all of my settings and just pulling a fresh version from git solved my problems.
Luckily the restore process is easy-peasy so once I had the new install using Python 3 I just had to restore my old settings.

Thanks again for all the work!

@anb0s @miigotu I noticed the files are actually part of the backup, just probably not where SickChill expects them (in /SickBeard/gui/slick/cache/). I restored them manually and they immediately appeared in the UI.

Hi, did the upgrade fine on synology by manually installing the package but getting this error on the logs: 2020-10-15 11:47:03 Unable to open /root: PermissionError(13, 'Permission denied') / [Errno 13] Permission denied: '/root'

Despite the fact that I have sc-download with read/write everywhere
Thanks

Hi, did the upgrade fine on synology by manually installing the package but getting this error on the logs: 2020-10-15 11:47:03 Unable to open /root: PermissionError(13, 'Permission denied') / [Errno 13] Permission denied: '/root'

Despite the fact that I have sc-download with read/write everywhere
Thanks

Maybe you installed the wrong package? Did you use the one from the Nyarans's PR on synocommunity, right?

Yep I used the one from https://github.com/SynoCommunity/spksrc/pull/4161
Everything seems to be working ok even with that warning.
I cleared and it didn't appear again

Branch/Commit: master/99336df163c7e776c7931d864e84d1f0f83afe4d
OS: Raspibian
Browser: Safari
What you did: Try to update
What happened: Local branch is ahead of master. Automatic update not possible.
What you expected: update
Logs:

2020-09-05 19:36:01 WARNING WEBSERVER-HOME :: Local branch is ahead of master. Automatic update not possible. 2020-09-05 19:35:58 INFO WEBSERVER-HOME :: Checking for updates using GIT

Sorry for my lack of knowledge. I researched before posting here but I didn't find a solution. I'm using Raspbian and I don't know how to update to use python3. I already looked and python is installed on my system, I just don't know how to make it work with sickchill

@rafaelrosars - You can backup your current settings/db, remove SickChill, then re-install from scratch (and restore your backup).
Once you're on Py3, you should be able to use the updater again.

@rafaelrosars : installing python3 on Raspbian is pretty easy, you can google a guide, that's the only prerequisite you really need. for the sake of having things in once space, it should be as easy as running "sudo apt install python3", and the package manager should take care of the rest. The command "python --version" should tell you what is currently default.

When you have python sorted, you can follow my procedure above and that will do the trick; in summary, back up your config from the sickchill web ui (configure (gear icon), backup) then rebase your sickchill install (wipe it first for cleanliness), then perform the initial setup and restore from backup. It's pretty easy overall. The fellows at sickchill have made it relatively painless to get done. Good luck.

to be fair, I'm just restating what pat said, but more verbose for clarity.

As someone who has read up on the subject, the above confuses me. It's my understanding that a git installation of SickChill is recommended against by the maintainers and as such unsupported. It's not even listed as an installation method on the wiki anymore, only Docker and pip installs. So I would like the SickChill maintainers to clarity on this please.

As someone who has read up on the subject, the above confuses me. It's my understanding that a git installation of SickChill is recommended against by the maintainers and as such unsupported. It's not even listed as an installation method on the wiki anymore, only Docker and pip installs. So I would like the SickChill maintainers to clarity on this please.

Huh? Git or pip is the preferred method. Docker uses the git method anyway. SOURCE installs are discouraged.

What's the procedure to update SickChill on a Synology NAS.
I'm using this package:
image

What's the procedure to update SickChill on a Synology NAS.
I'm using this package:
image

https://github.com/SynoCommunity/spksrc/pull/4161

Huh? Git or pip is the preferred method. Docker uses the git method anyway. SOURCE installs are discouraged.

Then I completely misunderstood that part. I guess I'll use git then, but without Docker. Thanks for clarifying.

I had this problem; I went the manual method because I'm installed directly into Linux (Ubuntu) My process was simply:

* backup system using WebUI backup method

* stop SickChill

* uninstall SickChill using method documented in Wiki (moved install folder for additional backup in case of stuff going sideways)

* installed using manual method (also in Wiki)

* once started, restore from backup (SickChill required a restart)

* small exception: restart failed from web - sickchill restarted, but webUI was not responsive, required restarting again from Command line (SSH in my case).

* mass update meta data

Afterwards, everything is working normally and as expected.

I'll note that I did this because the old version I was running would not update metadata for new episodes; this has been an ongoing problem that I haven't found time to do a root-cause analysis on; however, once updated, one of the problematic series, that never seemed to update metadata automatically, was able to update metadata; though it was manual in this case, it's a good sign.

Thanks everyone who posted in this bug, I hope my comment helps someone else moving forward.

Thank you so much - this worked perfectly! I've been holding off on updating for so long but finally gave in. Following these steps made it straight forward and simple. Props!

Trying to upgrade to the latest version, running into problems.

I moved the old version of Sickchill and installed the new version in /opt/sickchill using:
pip3 install -t /opt/sickchill sickchill

The install went fine, but when I try and run /opt/sickchill/bin/SickChill.py, I get the following error:

Traceback (most recent call last):
  File "/opt/sickchill/bin/SickChill.py", line 14, in <module>
    import sickchill.start
ModuleNotFoundError: No module named 'sickchill'

I've tried futzing around with PYTHONPATH but was unable to resolve. Any hints?

Trying to upgrade to the latest version, running into problems.

I moved the old version of Sickchill and installed the new version in /opt/sickchill using:
pip3 install -t /opt/sickchill sickchill

The install went fine, but when I try and run /opt/sickchill/bin/SickChill.py, I get the following error:

Traceback (most recent call last):
  File "/opt/sickchill/bin/SickChill.py", line 14, in <module>
    import sickchill.start
ModuleNotFoundError: No module named 'sickchill'

I've tried futzing around with PYTHONPATH but was unable to resolve. Any hints?

You don't set a target that way or the wrapper doesn't work. Use the default path or set up a virtualenv instead.

<set up virtualenv, set WORKON_HOME in bashrc>

mkvirtualenv -p python3.8 sickchill
workon sickchill
pip3 install sickchill

Trying to upgrade to the latest version, running into problems.
I moved the old version of Sickchill and installed the new version in /opt/sickchill using:
pip3 install -t /opt/sickchill sickchill
The install went fine, but when I try and run /opt/sickchill/bin/SickChill.py, I get the following error:

Traceback (most recent call last):
  File "/opt/sickchill/bin/SickChill.py", line 14, in <module>
    import sickchill.start
ModuleNotFoundError: No module named 'sickchill'

I've tried futzing around with PYTHONPATH but was unable to resolve. Any hints?

You don't set a target that way or the wrapper doesn't work. Use the default path or set up a virtualenv instead.

<set up virtualenv, set WORKON_HOME in bashrc>

mkvirtualenv -p python3.8 sickchill
workon sickchill
pip3 install sickchill

Thanks for the hint. If I am using a startup script to get SickChill going and SickChill is running as a special user sickchill with no home directory, is there a diff set of recommendations?

Was this page helpful?
0 / 5 - 0 ratings