SickChill doesn't start after update Git to v2.32.0
decharon opened this issue · 7 comments
After updating Git to version v2.32.0 SickChill wouldn't start anymore.
SickChill installed version: 99999999-1.3 | Newest online version: 20210329-1
Git version: 2.32.0-18
DSM version: 6.2.4-25556
Cannot have anything to do with each other.
Medusa only uses git when installing or updating, then it does a gitclone from the medusa github.
Just starting medusa does not use git at all.
Also updating from within medusa does not use git.
To be sure I updated git to 2.32.0-18 and found no problem at all.
Take al look in the medusa logs to find the problem.
Medusa log:
/var/packages/medusa/target/var/Logs/application.log
Package log:
/var/log/packages/medusa.log
BenjV,
First of all, thank you for your reply.
You mention Medusa, but i'm talking about SickChill is there a simularity?
It started with a Mako error, when i tried to update SickChill within the application itself. I thought the new update for Git would solve the problem.
No difference here between Medusa and SickChill regarding the use of git.
If something got corrupted or you have a SickChill release that will not start, then you could download the package again and do a manual install.
The package will update SickChill to the latest available software on github by doing a git clone, but only if you install it, not when you just start the existing package.
Most likely you had the same problem I had a littler while ago, a corrupted SickChill release that would not start, but is fixed in the mean time.
Unfortunately reinstalling SickChill did not solve the problem. Do you have any other idea?
Look in the logs.
Replace medusa, with sickchill in the location I mentioned.
Same problem here after just updating Git to 2.32.
This is my log from the begining of the update:
2021/07/16 18:31:31 (system) trigger sickchill 99999999-1.3 Begin start-stop-status stop
SickChill did not responde to the 'TERM' signal, so a forced kill will is needed.
/var/packages/sickchill/scripts/start-stop-status: line 74: kill: (24689) - No such process
2021/07/16 18:31:51 (system) trigger sickchill 99999999-1.3 End start-stop-status stop ret=[0]
2021/07/16 18:32:21 (system) trigger sickchill 99999999-1.3 Begin start-stop-status start
Writing PID: 6075 to /volume1/@appstore/sickchill/var/sickchill.pid
2021/07/16 18:32:23 (system) trigger sickchill 99999999-1.3 End start-stop-status start ret=[0]
2021/07/16 18:33:49 start sickchill 99999999-1.3 Begin start-stop-status stop
2021/07/16 18:33:49 start sickchill 99999999-1.3 End start-stop-status stop ret=[0]
2021/07/16 18:33:49 start sickchill 99999999-1.3 Begin start-stop-status start
Writing PID: 9791 to /volume1/@appstore/sickchill/var/sickchill.pid
Crashed. Removing pidfile!
removed '/volume1/@appstore/sickchill/var/sickchill.pid'
2021/07/16 18:33:51 start sickchill 99999999-1.3 End start-stop-status start ret=[3]
2021/07/16 18:33:52 (system) trigger sickchill 99999999-1.3 Begin start-stop-status stop
2021/07/16 18:33:52 (system) trigger sickchill 99999999-1.3 End start-stop-status stop ret=[0]
2021/07/16 18:34:03 start sickchill 99999999-1.3 Begin start-stop-status start
Writing PID: 10667 to /volume1/@appstore/sickchill/var/sickchill.pid
Crashed. Removing pidfile!
removed '/volume1/@appstore/sickchill/var/sickchill.pid'
Reinstall of your latest package doesn't help
SickChill version: 99999999-1.3
Git version: 2.32.0-18
DSM version: 6.2.4-25556
Clearly a sickchill, problem, the package log looks normal for an application that crashes.
My sickchill version was running fine, but when I updated from within sickchill it would not start again.
So the latest update of sickchill is the problem.
Nothing to do with the git update, as I said.
EDIT:
Did some investigation and found this:
The SickcChill developer has changed the code so it is no longer possible to run the package from source.
To be able to run sickchill to run on a Synology Nas, binaries have to be build and put in a package.
Synology does not supply compilers on their machines so building binaries during installation is not possible
They have to be created for every cpu architecture on a crosscompilation platform
I don't have the tools nor the environment to do that.
The sickchill developer is trying to create Synology packages themselves on the SynoCommunity.
I tried that package but that does not work either.
I will remove the sickchill packages from my github and would advice everybody to switch over to my medusa package (available for DSM6 and DSM 7) which still can be run from source.