Sickbeard won't start after update

[Vinzend]

Hello,

I have a small issue on my 302T. I have updated Couchpotato and Sickbeard and reboot the NAS. I can't seem to start Sickbeard anymore . When I click the icon I get the following error:

Code: Select all

Can not connect
Firefox can not connect to the server at 10.xxx.xxx.xx:7071.

I'm a bit new to Telnet and NAS environment, please be gentle . Sickbeard-Anime is working, couchpotato as well.

What could be the problem?
How can i troubleshoot this issue? I've googled quite a bit, but I'm having difficulty finding the needle in the haystack.

Many thanks in advance for reading this topic.

[cyph]

That happened to me too but I thought it was because I had a git clone.

If you follow the thread on git cloning sickbeard, and follow through with the commands, it will fix your issue.

[clinton.hall]

Try disabling and enabling in app Central.

If that doesn't work, via ssh/telnet issue

Code: Select all

/usr/local/AppCentral/sickbeard/CONTROL/start-stop.sh restart

And post the output here.

[Vinzend]

Thank you both for replying so fast.
In an attempt to telnet (Putty) i tried to run last night. I used 'start' command, I'll try again with 'restart' tonight.

Code: Select all

/usr/local/AppCentral/sickbeard/CONTROL/start-stop.sh start (and stop)

I think I got (not near my local computer now, sorry)

Code: Select all

-sh: start-stop not found

when I did

Code: Select all

/usr/local/AppCentral/sickbeard/CONTROL/ ls

it did show start-stop.sh* in a green font and asterix symbol.

[Vinzend]

Try disabling and enabling in app Central.

I did disable and enable it but no effect.

Code: Select all

/usr/local/AppCentral/sickbeard/CONTROL/start-stop.sh restart

Result:

Code: Select all

xxxxxxxx@AS302T:/volume1/.@root # /usr/local/AppCentral/sickbeard/CONTROL/start-stop
.sh restart
Restarting SickBeard
Shutting down SickBeard at Thu Apr 10 21:50:58 CEST 2014...
SickBeard is not running? (Thu Apr 10 21:50:58 CEST 2014)
SickBeard prestartup checks... (Thu Apr 10 21:50:58 CEST 2014)
 Cheetah found...
Starting SickBeardPID file: /usr/local/AppCentral/sickbeard/SickBeard.pid already exists. Exiting.
 Done (Thu Apr 10 21:51:01 CEST 2014)

[clinton.hall]

Ok, try

Code: Select all

ps | grep sick

If there are any processes listed for SickBeard, kill them.

Code: Select all

kill xxxxx

Where xxxxx is the number given for the processed returned by the previous command.

Then

Code: Select all

rm /usr/local/AppCentral/sickbeard/SickBeard.pid
/usr/local/AppCentral/sickbeard/CONTROL/start-stop.sh restart

[Vinzend]

That did the trick. Thank you for your quick support. I'll keep an eye out on how it goes.
What could have causes the error?

[clinton.hall]

this could have been caused by a system crash/power failure while SB was running, or a file permissions issue... or just a few attempts to start this via ssh (using start, not restart) while SB was already running.

[Vinzend]

Thank you Clinton.hall

[igracgq]

You are a gentleman and a scholar Clinton.hall ... your solution worked perfectly

out of curiosity, what did the last code do?

rm /usr/local/AppCentral/sickbeard/SickBeard.pid
/usr/local/AppCentral/sickbeard/CONTROL/start-stop.sh restart