sickbeard can't stop plugin via web GUI

[rutherford]

root@Dumbo:~# ps -ef | grep sick
root     26264  7033  0 14:37 ?        00:00:00 /bin/sh /etc/rc.d/rc.sickbeard disable nobody 8091 /mnt/cache/.sickbeard /mnt/cache/.sickbeard/datadir
root     26317 25795  0 14:37 pts/0    00:00:00 grep sick
root@Dumbo:~# /etc/rc.d/rc.sickbeard stop
Stopping sickbeard...
/etc/rc.d/rc.sickbeard: line 42: kill: (10902) - No such process
<hang>

 

Seems like the pid isn't right for what sickbeard is actually running under. The rc.sickbeard tries to kill 10902, but can't find it because sickbeard is running under 26264. When I manually kill -9 26264, the web GUI still thinks sickbeard is running and won't snap out of it.

 

Any ideas?

[Keevil]

Did you ever get this fix? Or figure out a method?

[rutherford]

I have not figured anything out. It seems that Couch potato keeps acting squirrly... and just isn't as easy to deal with as SAB or sickbeard. Not sure what's going on there.

 

Do keep an eye out for the installation directory. For one reason or another, the update button downloads a new version of couchpotato but puts it into a sub directory like RuudBurger-3443788 or something. The GUI keeps trying to find the couchpotato py script in the regular directory, but the new one is actually in the RuudBurger sub directory. I usually just do a mv * ../ to make things start behaving properly again.

[aiden]

I have the same issue, and did a little more snooping.  If you look at the start command, there is a --pidfile switch that isn't working correctly. Instead of writing the PID into the file, which is what the stop code is expecting, it instead writes "pid" into the file. So when you issue a rc.sickbeard stop, the stop function encounters "pid" in the /var/run/sickbeard/sickbeard.pid file that was created on start. This bypasses the code that gracefully exits if the file is empty, because it isn't. At the same time, it is getting a bad input, and thus the kill command can't be issued. Since all this is embedded in a sudo python execute string, it hangs rather abruptly. I'm no Linux guru, so I have no idea how to fix it beyond describing the errors I can track.

 

I have found that sickbeard much prefers running as root, because when I run it as nobody, I get all kinds of fail.

[rutherford]

pid... "pid" hilarious.

[aiden]

pid... "pid" hilarious.

 

Yeah, kinda ridiculous. You can verify yourself by running "cat var/run/sickbeard/sickbeard.pid" after sickbeard starts.  Then if you look in the plugin code, you can trace where the line fails, on the "kill" command, which issues the "give me a valid pid" error.