sabnzbd / sickbeard / couchpotato pbi's

[Joshua Parker Ruehlig]

Thanks everybody for all your help, but I think I found the issue. I restarted, but this didn't have any effect. I removed all plugins and reinstalled the Plugin Jail. Reinstalled plugins and now they successfully turn on in the GUI (except for Headphones). No error message, it just won't turn on.

What port number are used for SABnzbd, SickBeard, Headphones, Couch Potato? Thanks again.

According to the SABnzbd config.ini file, the default HTTPS port number is set to port 9090. But if I go to https://jailip:9090 it doesn't work.

mind running the below in your jail?

Code:

service headphones status
service headphones start

---

EDIT
Haha, nvm todos got to answering your question before I did

 

[toddos]

About the par2cmdline-tbb issue, I'm on 0.81 and still had problems (verified with a download that needed to be repaired but kept failing even though it should've repaired). I just ran:

Code:

pkg_add -r par2cmdline-tbb

After that, running "par2" or "par2verify" did not return the error others have reported and that I was getting before, and SAB actually started verifying/repairing my failed download as it should have.

It looks like the pbi needs to be revved with a fresh "pkg_add -r par2cmdline-tbb" to make things work.

 

[Joshua Parker Ruehlig]

About the par2cmdline-tbb issue, I'm on 0.81 and still had problems (verified with a download that needed to be repaired but kept failing even though it should've repaired). I just ran:

Code:

pkg_add -r par2cmdline-tbb

After that, running "par2" or "par2verify" did not return the error others have reported and that I was getting before, and SAB actually started verifying/repairing my failed download as it should have.

It looks like the pbi needs to be revved with a fresh "pkg_add -r par2cmdline-tbb" to make things work.

I'll look into it, I swear I added that package but I may have missed something. I'll also find something that needs to be repaired and test it out

EDIT
If you have the link to something that needs to be repaired it might save me some time.
EDIT2
running par2 or par2verify seems to be fine for me.. can anyone confirm that 0.8.1 gives a bad output when running 'par2verify' from a fresh jail?
EDIT3

Code:

2012-09-03 17:17:22,428::INFO::[postproc:546] Par2 check starting on South Park S15E07 You're Getting Old 720p WEB DL AAC2 0 H 264 MC
2012-09-03 17:17:22,429::INFO::[postproc:561] Running repair on set South.Park.S15E07.Youre.Getting.Old.720p.WEB-DL.AAC2.0.H.264-MC
2012-09-03 17:17:22,434::INFO::[newsunpack:1301] Quick-check of file South.Park.S15E07.Youre.Getting.Old.720p.WEB-DL.AAC2.0.H.264-MC.part05.rar failed!
2012-09-03 17:17:22,435::INFO::[newsunpack:789] Scanning "/usr/pbi/sabnzbd-amd64/data/Downloads/incomplete/South Park S15E07 You're Getting Old 720p WEB DL $
2012-09-03 17:17:29,902::INFO::[newsunpack:971] Verified in 7 seconds, repair is required
2012-09-03 17:17:33,515::INFO::[newsunpack:1094] Repaired in 3 seconds
2012-09-03 17:17:33,516::INFO::[newsunpack:799] Par verify finished ok on /usr/pbi/sabnzbd-amd64/data/Downloads/incomplete/South Park S15E07 You're Getting $
2012-09-03 17:17:33,517::INFO::[newsunpack:829] Deleting /usr/pbi/sabnzbd-amd64/data/Downloads/incomplete/South Park S15E07 You're Getting Old 720p WEB DL A$
2012-09-03 17:17:33,530::INFO::[newsunpack:853] Deleting /usr/pbi/sabnzbd-amd64/data/Downloads/incomplete/South Park S15E07 You're Getting Old 720p WEB DL A$
2012-09-03 17:17:33,532::INFO::[newsunpack:867] Deleting /usr/pbi/sabnzbd-amd64/data/Downloads/incomplete/South Park S15E07 You're Getting Old 720p WEB DL A$
2012-09-03 17:17:33,533::INFO::[postproc:574] Par2 check finished on South Park S15E07 You're Getting Old 720p WEB DL AAC2 0 H 264 MC
2012-09-03 17:17:33,535::INFO::[misc:792] Creating directories: /usr/pbi/sabnzbd-amd64/data/Downloads/complete/South Park S15E07 You're Getting Old 720p WEB$
2012-09-03 17:17:33,537::INFO::[postproc:342] Running unpack_magic on South Park S15E07 You're Getting Old 720p WEB DL AAC2 0 H 264 MC
2012-09-03 17:17:33,547::INFO::[newsunpack:201] Unrar starting on /usr/pbi/sabnzbd-amd64/data/Downloads/incomplete/South Park S15E07 You're Getting Old 720p$
2012-09-03 17:17:33,548::INFO::[newsunpack:411] Extracting rarfile /usr/pbi/sabnzbd-amd64/data/Downloads/incomplete/South Park S15E07 You're Getting Old 720$
2012-09-03 17:17:37,889::INFO::[newsunpack:666] Skipping unrar file check due to unreliable file names or old unrar
2012-09-03 17:17:37,890::INFO::[newsunpack:671] Unpacked 1 files/folders in 4 seconds

does this mean my system correctly used par2 or are we looking for something else in the output?

 

[TazgodX]

First, thanks for the hard work!
Second, I got a question. I like to have 2 versions of sickbeard running, the normal up to date master, which you made a PBI for, and the Anime Branch. Is there a way to modify your sickbeard PBI to create another version of sickbeard but for the anime branch?

-Thanks again!

 

[Joshua Parker Ruehlig]

First, thanks for the hard work!
Second, I got a question. I like to have 2 versions of sickbeard running, the normal up to date master, which you made a PBI for, and the Anime Branch. Is there a way to modify your sickbeard PBI to create another version of sickbeard but for the anime branch?

-Thanks again!

Well for the pbi's to not conflict youd need to name them something else when they're being build. If you want you can PM me your public key, I can give you git access and you can modify the code a bit to create your own sickbeard-anime pbi.

 

[gesshoku]

If you are successful creating the anime branch for parallel installation, i'd be happy if you would make it available for download

 

[toddos]

Joshua, it looks like your par2 is correct. Here's a log from a repair check where par2 is broken:

Code:

2012-09-03 08:09:36,327::INFO::[postproc:546] Par2 check starting on <my download>
2012-09-03 08:09:36,327::INFO::[postproc:561] Running repair on set <my download>
2012-09-03 08:09:36,339::INFO::[newsunpack:1301] Quick-check of file <my download> failed!
2012-09-03 08:09:36,339::INFO::[newsunpack:789] Scanning "/usr/pbi/sabnzbd-amd64/data/Downloads/incomplete/somefolder/some.par2
2012-09-03 08:09:36,360::INFO::[newsunpack:807] Par verify failed on /usr/pbi/sabnzbd-amd64/data/Downloads/incomplete/somefolder/some.par2
2012-09-03 08:09:36,360::INFO::[postproc:574] Par2 check finished on <my download>

And here's a log from where par2 works (in this case the download still didn't repair because there weren't enough par2s)

Code:

2012-09-03 08:28:32,640::INFO::[postproc:546] Par2 check starting on <my download>
2012-09-03 08:28:32,640::INFO::[postproc:561] Running repair on set <my download>
2012-09-03 08:28:32,652::INFO::[newsunpack:789] Scanning "/usr/pbi/sabnzbd-amd64/data/Downloads/incomplete/somefolder/some.par2
2012-09-03 08:34:44,812::INFO::[newsunpack:971] Verified in 6 minutes 12 seconds, repair is required
2012-09-03 08:34:44,812::INFO::[newsunpack:1011] Need to fetch 196 more blocks, checking blocks
2012-09-03 08:34:44,812::INFO::[newsunpack:1033] 0 blocks available

This is the same exact download. The only difference is the first run is from a broken par2 (throws the "thread_monitor Invalid argument" if you run from the command line) and the second is after running "pkg_add -r par2cmdline-tbb" (shows the command usage if you rn from the comman

 

[Joshua Parker Ruehlig]

toddos are you sure my 0.8.1 plugin has a broken par2? My log is from a fresh jail install with just sabnzbd 0.8.1 installed and it seems par2 is working.
Not sure what happened in your jail but might be because of a previous version being uninstalled?

 

[toddos]

When I updated to 0.8, I uninstalled, deleted my jail, and reinstalled everything (recommended installation method for 0.7 -> 0.8). For 0.8.1, I used the gui update button (the first post instructions didn't say not to do that, so I figured I'd try it out) rather than uninstalling/reinstalling. It's possible that's why my sab was broken even after updating to 0.8.1. For now reloading par2cmdline-tbb through pkg_add fixed my issues, but I'll be sure to uninstall sab and reinstall next time.

 

[Wolfeman0101]

Is there a trick to updating Couchpotato? I click "just update, gogogo!" and it seems to try to update but it never does.

 

[toddos]

Is there a trick to updating Couchpotato? I click "just update, gogogo!" and it seems to try to update but it never does.

Do you mean updating the plugin, for example from 0.7 to 0.8? If so, read the first post in this thread for instructions.

Or do you mean the couchpotato source code? In which case, you should be able to upgrade from the CP UI directly (click the gear button on the top-right, choose "Update to latest"). It'll pull the latest code from github and update in-place.

 

[Wolfeman0101]

Do you mean updating the plugin, for example from 0.7 to 0.8? If so, read the first post in this thread for instructions.

Or do you mean the couchpotato source code? In which case, you should be able to upgrade from the CP UI directly (click the gear button on the top-right, choose "Update to latest"). It'll pull the latest code from github and update in-place.

Yeah inside CP, there is a source code update but it doesn't seem to work when I click update.

 

[russdyer]

toddos, thanks for all the information.

A few other things...Maybe this is because I am running FreeNAS 8.3.0 Beta 1, but in the plugins both SABnzbd and Headphones are turned off in the GUI and can't be turned on. Yet I can still access Sabnzbd and Headphones through their ports.

Also, when I try to change options in SABnzbd it doesn't save any of the changes. I make changes, save them and they don't stay. What can I do to fix this? Is this the same for all plugins? To save changes, do I need to something other than CHOWN them? Do they need CHMOD 777? Or do I need to 777 only where the config file is located?

Thanks for any help.

 

[Wolfeman0101]

I fixed my Couchpotato problem by

Code:

chown -R root /usr/pbi/couchpotato-amd64/

 

[toddos]

toddos, thanks for all the information.

A few other things...Maybe this is because I am running FreeNAS 8.3.0 Beta 1, but in the plugins both SABnzbd and Headphones are turned off in the GUI and can't be turned on. Yet I can still access Sabnzbd and Headphones through their ports.

Also, when I try to change options in SABnzbd it doesn't save any of the changes. I make changes, save them and they don't stay. What can I do to fix this? Is this the same for all plugins? To save changes, do I need to something other than CHOWN them? Do they need CHMOD 777? Or do I need to 777 only where the config file is located?

Thanks for any help.

I have not used 8.3, and unless you need functionality that's in the beta I'd recommend you not use 8.3 either. With that said, you probably can't go back to 8.2 without rebuilding your datasets (8.3 supports ZFS v28, 8.2 only supports v14, ZFS is backward-compatible but not forward-compatible, so a 8.2 v14 pool will work on 8.3 but an 8.3 v28 pool will not work on 8.2).

If you start the services by hand, using "service sabnzbd onestart", I assume they work?

When you make changes in the UI, are you clicking the "Save changes" button before navigating away? Some changes require restarting SAB, so it may not look like they're working until you do. Worst case, you can manually make changes in data/config.ini (shutdown sab before doing this). The app data and files should be owned by the service user (user "sabnzbd" for sab, user "headphones" for headphones, etc) and that user should have write permissions on everything.

Seriously, though, you might want to consider just starting over with 8.2 if you possibly can.

 

[toddos]

I fixed my Couchpotato problem by

Code:

chown -R root /usr/pbi/couchpotato-amd64/

Are you running couchpotato as root? That shouldn't be right. It should run as user "couchpotato", and that user should have ownership and write permissions of the couchpotato files.

 

[Wolfeman0101]

Are you running couchpotato as root? That shouldn't be right. It should run as user "couchpotato", and that user should have ownership and write permissions of the couchpotato files.

It runs as couchpotato but wouldn't update. Let me spin up a test Jail and try it again.

 

[russdyer]

I have not used 8.3, and unless you need functionality that's in the beta I'd recommend you not use 8.3 either. With that said, you probably can't go back to 8.2 without rebuilding your datasets (8.3 supports ZFS v28, 8.2 only supports v14, ZFS is backward-compatible but not forward-compatible, so a 8.2 v14 pool will work on 8.3 but an 8.3 v28 pool will not work on 8.2).

If you start the services by hand, using "service sabnzbd onestart", I assume they work?

When you make changes in the UI, are you clicking the "Save changes" button before navigating away? Some changes require restarting SAB, so it may not look like they're working until you do. Worst case, you can manually make changes in data/config.ini (shutdown sab before doing this). The app data and files should be owned by the service user (user "sabnzbd" for sab, user "headphones" for headphones, etc) and that user should have write permissions on everything.

Seriously, though, you might want to consider just starting over with 8.2 if you possibly can.

I've tried chown -R sabnzbd /usr/pbi/sabnzbd-amd64 and that doesn't work either.

I haven't update my zpool yet on the Beta, I was waiting for a public release for that. If I haven't updated my zpool, should I be able to upgrade to a lower version without issues?

Thanks,
Russ

 

[toddos]

I've tried chown -R sabnzbd /usr/pbi/sabnzbd-amd64 and that doesn't work either.

I haven't update my zpool yet on the Beta, I was waiting for a public release for that. If I haven't updated my zpool, should I be able to upgrade to a lower version without issues?

Thanks,
Russ

First, don't do things blindly. Look at what's there before you chown or chmod. What are the ownership and permissions for the sabnzbd-amd64/data directory, and for the data/config.ini file? What user is the service running as (ps waux | grep sabnzbd, the first column is the user the process is running as)? If the service is not running as the right user, chowning isn't going to help. If it is running as the right user but the files are already owned properly, that's not going to help.

If you're up for it, I'd definitely recommend downgrading. Save your current config, put 8.2 on a different USB drive (keep your current 8.3 drive just in case), boot up 8.2 and import your old config, and then setup your jail and plugins.

 

[russdyer]

Would you not recommend just using the GUI upgrade tool?