Sickchill Permission Errors

LSIO Discussion Container Support
1

Started, I think, after the last update or the one before. Had been working OK for a year or so.

I am updating using the Docker Create method as published by LSIO

I see these error messages whenever I try to “check for updates”:

2020-05-03 09:28:31 ERROR    WEBSERVER-ERRORLOGS :: [c5ed827] git fetch origin --prune returned code 255, treating as error : error: cannot open .git/FETCH_HEAD: Permission denied

2020-05-03 09:28:31 DEBUG    WEBSERVER-ERRORLOGS :: Executing git fetch origin --prune with your shell in /app/sickchill

None

2020-05-03 09:28:31 ERROR    WEBSERVER-ERRORLOGS :: [c5ed827] git config remote.origin.url https://github.com/SickChill/SickChill.git returned code 255, treating as error : error: could not lock config file .git/config: Permission denied

2020-05-03 09:28:31 DEBUG    WEBSERVER-ERRORLOGS :: Executing git config remote.origin.url https://github.com/SickChill/SickChill.git with your shell in /app/sickchill

2020-05-03 09:28:31 DEBUG    WEBSERVER-ERRORLOGS :: git rev-parse HEAD : returned successful

2020-05-03 09:28:31 DEBUG    WEBSERVER-ERRORLOGS :: Executing git rev-parse HEAD with your shell in /app/sickchill

None

2020-05-03 09:28:31 ERROR    WEBSERVER-ERRORLOGS :: [c5ed827] git symbolic-ref -q HEAD returned : 

2020-05-03 09:28:31 DEBUG    WEBSERVER-ERRORLOGS :: Executing git symbolic-ref -q HEAD with your shell in /app/sickchill

2020-05-03 09:28:31 INFO     WEBSERVER-ERRORLOGS :: Checking for updates using GIT

None

2020-05-03 09:28:30 ERROR    WEBSERVER-ERRORLOGS :: [c5ed827] git symbolic-ref -q HEAD returned : 

2020-05-03 09:28:30 DEBUG    WEBSERVER-ERRORLOGS :: Executing git symbolic-ref -q HEAD with your shell in /app/sickchill

2020-05-03 09:28:30 DEBUG    WEBSERVER-ERRORLOGS :: Using: git

2020-05-03 09:28:30 DEBUG    WEBSERVER-ERRORLOGS :: git version : returned successful

2020-05-03 09:28:30 DEBUG    WEBSERVER-ERRORLOGS :: Executing git version with your shell in /app/sickchill

2020-05-03 09:28:30 DEBUG    WEBSERVER-ERRORLOGS :: Checking if we can use git commands: git version

2020-05-03 09:27:32 DEBUG    WEBSERVER-HOME :: check_for_new_news: Checking GitHub for latest news.

2020-05-03 09:27:32 INFO     WEBSERVER-HOME :: No update needed

2020-05-03 09:27:32 WARNING  WEBSERVER-HOME :: Unable to contact github, can't check for update

None

2020-05-03 09:27:32 ERROR    WEBSERVER-HOME :: [c5ed827] git fetch origin --prune returned code 255, treating as error : error: cannot open .git/FETCH_HEAD: Permission denied

2020-05-03 09:27:32 DEBUG    WEBSERVER-HOME :: Executing git fetch origin --prune with your shell in /app/sickchill

None

2020-05-03 09:27:32 ERROR    WEBSERVER-HOME :: [c5ed827] git config remote.origin.url https://github.com/SickChill/SickChill.git returned code 255, treating as error : error: could not lock config file .git/config: Permission denied

2020-05-03 09:27:32 DEBUG    WEBSERVER-HOME :: Executing git config remote.origin.url https://github.com/SickChill/SickChill.git with your shell in /app/sickchill

2020-05-03 09:27:32 DEBUG    WEBSERVER-HOME :: git rev-parse HEAD : returned successful

2020-05-03 09:27:32 DEBUG    WEBSERVER-HOME :: Executing git rev-parse HEAD with your shell in /app/sickchill

None

2020-05-03 09:27:32 ERROR    WEBSERVER-HOME :: [c5ed827] git symbolic-ref -q HEAD returned : 

2020-05-03 09:27:32 DEBUG    WEBSERVER-HOME :: Executing git symbolic-ref -q HEAD with your shell in /app/sickchill

2020-05-03 09:27:32 INFO     WEBSERVER-HOME :: Checking for updates using GIT

I’ve tried removing and re-installing both the container/image as I would when updating, as well as removing and re-installing the Docker application on my Synology NAS with no change.

For my Sickchill user/group I am using Admin:Users (PUID=1024, PGID=100)

I note on the Sickchill issues page there are several others reporting the same problem.

Any help?

Thanks.

2

We don’t recommend or support updating via the webgui. Update instructions are in the readme

3

I am aware of that. Please note on the second line of my question I wrote:

** I am updating using the Docker Create method as published by LSIO**

4

Then what’s the issue? The error just says it can’t fetch the HEAD, which is only needed by the built-in updater

Disable the updater in the gui and you’re fine

5

Also, if you’re only updating via our recommended method, why are you checking for update in the webgui?

6

This is a new problem. Never happened until recently. And the GUI updater is a handy method of knowing whether or not there has been a new update.

7

It’s side effect. People kept complaining that sickchill didn’t display the current version in the webgui (unless you used the built-in updater). So we fixed it. The way we fixed it (git checkout tag) doesn’t work with the built-in updater, hence the errors.

8

LOL – And I was one of the one’s who complained!

How does the git checkout tag method work?

If I go to the page that apparently has that option, I get a similar error

9

https://media.giphy.com/media/MPLpvJcsWvrkk/giphy.gif(image larger than 4 MB)

The way sickchill checks for the version is by looking at git tags. We were previously installing the tarball, which doesn’t contain the git headers and other info.

So we switched to git clone to get all the other info that sickchill uses to determine version. But since we do versioned releases, we can’t just git clone and leave it at that, so we then do git checkout <tag> which sets it to the tagged release that is also in the docker image tag.

It seems the update checker needs to know which branch it is currently on to figure out updates. Since we checkout the specific tag, we’re no longer on the master branch, hence the error.

10

Will there be any help for that? Updates are erratic and it is handy to know, when starting the program, if there have been any updates.

11

Help for what?

The gui now shows you the exact version (as you requested), which happens to be the date of release.

Do a docker pull to see if there is a newer image

12

Help for what?

Having the correct version show up is a good thing.

But I did not expect the side effect of not being able to check for an updated version from the GUI.

13

Did you revert the last change? After updating this morning (using the Docker Create method as outlined in the instructions), the Branch is blank and the commit no longer updates.

For me, this is the worst of all possible worlds where I can neither check for updates, nor easily see which commit I have.

14

nothing was reverted. updates are working fine for other users.

15

@driz Any suggestions as to how to figure out why it is not working for me?

I’ve checked the file at /app/sickchill/.git/HEAD which contains the correct version, but the version from the preceding update is what is showing in the sickchill UI