OSickGear unable to start on reboot

[jillmess]

I am setting up a new TS-264 and have SickGear & SAB installed and running ok but am getting the following errors after rebooting the NAS. In the App Centre SickGear appears as though it is started (but is not). SickGear starts (restarts) without problem using ''Sherpa restart sg'' or running sickgear.sh via putty.

Error 2025-05-15 16:15:38 --- --- localhost --- --- --- [OSickGear] port tests failed!
Error 2025-05-15 16:15:38 --- --- localhost --- --- --- [OSickGear] no response on configured port(s)
Error 2025-05-15 16:15:38 --- --- localhost --- --- --- [OSickGear] port '8288' failed to respond after 120 seconds!

Any suggestions?

I have reverted to using SickGear & SAB on my TS-451+ With the required folder from the 264 mounted on the 451+ this all works to put downloads where I want them but I would prefer it all to run on the new NAS.

[OneCDOnly]

Hi @jillmess and thanks for reporting this problem. 👍🏽

Can you please check the OSickGear service log?

/etc/init.d/sickgear.sh log

The first action in the log is the one tried when the NAS is booting (this should be a start). Can you please copypaste the action block back here?

[jillmess]

Murphy's Law! I got the above error again when I tried to 'start' SickGear from App Centre so that it was active before rebooting to get the log - this had not happened previously (and I didn't think to get the log at that point). I then restarted sickgear via putty (started ok), rebooted, and everything started normally.

I have rebooted twice more and all ok both times. While I am happy it is working now I really hate it when I don't know why, particularly when nothing has changed.

[OneCDOnly]

Ah, no-worries. If it happens again, can you please get that first start action block from the service log and post it here?

Thank you. 🤓

[jillmess]

Just shut down and moved to new location - error again on restart as follows:
1 > source: sickgear.sh, action: start, time: Fri 16 May 2025 12:00:08 PM EST, load: 2.02
2 - package: 250514, service: 250514, library: 250514
3 - daemon PID: none
4 - QPKG enabled: 'true'
5 - application auto-update: 'true'
6 - active git branch: 'main'
7 - file exists: '/opt/bin/git'
8 > update 'OSickGear' from remote repository: OK
9 > load ports from configuration file: OK
10 > start daemon: OK
11 - daemon PID: none
12 > watch for daemon process name to appear (no-more than 120 seconds): appeared in 1 second
13 - daemon PID: '3600'
14 - daemon listening address: '0.0.0.0'
15 - HTTPS port enabled: 'false'
16 - HTTP port: '8288'
17 > test for port '8288' response (no-more than 120 seconds): failed
18 no response on configured port(s)
19 port tests failed!
20 = source: sickgear.sh, action: start, time: Fri 16 May 2025 12:02:38 PM EST, result: FAILED, elapsed: 0h:02m:31s, load 20 : 2.54

[jillmess]

/etc/init.d/sickgear.sh log
11 - daemon PID: none
12 > watch for daemon process name to appear (no-more than 120 seconds): appeared in 1 second
13 - daemon PID: '3600'
14 - daemon listening address: '0.0.0.0'
15 - HTTPS port enabled: 'false'
16 - HTTP port: '8288'
17 > test for port '8288' response (no-more than 120 seconds): failed
18 no response on configured port(s)
19 port tests failed!
20 = source: sickgear.sh, action: start, time: Fri 16 May 2025 12:02:38 PM EST, result: FAILED, elapsed: 0h:02m:31s, load: 2.54
21 •
22 > source: sickgear.sh, action: stop, time: Fri 16 May 2025 12:11:14 PM EST, load: 1.30
23 - package: 250514, service: 250514, library: 250514
24 - daemon PID: '3600'
25 - QPKG enabled: 'true'
26 - application auto-update: 'true'
27 - active git branch: 'main'
28 - daemon PID: '3600'
29 > stop daemon PID '3600' with SIGTERM (no-more than 120 seconds): stopped in 4 seconds
30 - daemon PID: none
31 = source: sickgear.sh, action: stop, time: Fri 16 May 2025 12:11:18 PM EST, result: OK, elapsed: 4,098ms, load: 1.30
32 •
33 > source: sickgear.sh, action: start, time: Fri 16 May 2025 12:11:49 PM EST, load: 1.11
34 - package: 250514, service: 250514, library: 250514
35 - daemon PID: none
36 - QPKG enabled: 'true'
37 - application auto-update: 'true'
38 - active git branch: 'main'
39 - file exists: '/opt/bin/git'
40 > update 'OSickGear' from remote repository: OK
41 > load ports from configuration file: OK
42 > start daemon: OK
43 - daemon PID: none
44 > watch for daemon process name to appear (no-more than 120 seconds): appeared in 1 second
45 - daemon PID: '28996'
46 - daemon listening address: '0.0.0.0'
47 - HTTPS port enabled: 'false'
48 - HTTP port: '8288'
49 > test for port '8288' response (no-more than 120 seconds): responded in 2 seconds
50 > update QPKG icon with UI ports: OK
51 = source: sickgear.sh, action: start, time: Fri 16 May 2025 12:11:55 PM EST, result: OK, elapsed: 5,837ms, load: 1.18

More log entries - after stopping and starting via sherpa - if these are of any help.

[OneCDOnly]

Thank you for posting the service log.

It looks like I'll need to add an auto-retry-startup option, for the times when a daemon didn't launch correctly the first time, so it will be automatically tried again a short time later. This should save you needing to restart SickGear manually.

I'll add this quite-soon, but right now I'm working on fixing my main NAS that decided to throw a hissy fit this morning out-of-the-blue.

I'll post back in this discussion topic when the new SickGear QPKG is available upgrade so you can try it out. 🤓

[jillmess]

Thanks. No rush on my account as I will be away for a few weeks after tomorrow. I have reverted to running it on my old nas so all good for the time being anyway.

[OneCDOnly]

Hi @jillmess I've just released a bunch of new QPKG versions, including an auto-restart-daemon fix for packages like SickGear.

Can you please upgrade your QPKGs and let me know if SickGear works fine on your next bootup?

sherpa upgrade new

[jillmess]

Upgraded and have rebooted twice. All good both times.
Thank you

[OneCDOnly]

Awesome! 👍🏽