SABnzbd Forums

ontrose wrote: Hello getting this error, anyone know how to fix it or what ir means?


2010-06-19 07:28:05.834000 SEARCH :: Error while searching NZBs, skipping: 'ascii' codec can't decode byte 0xf6 in position 319: ordinal not in range(128)

Look in your log and post the whole error that will be near that line and I will take a look.

Hi Midgetspy,

could you add NZBindex.com to Sick Beard? They have a great RSS service and it happens more than once that the services provided don't find matches where NZBindex does. At this moment I have to add the RSS manually to SABnzbd...

About NZBIndex/binsearch, these are not index sites they're raw search sites. Supporting raw search sites would mean I would have to deal with parsing the whole post name rather than just the scene name, which is what the index sites already do. At this point I have no interest in dealing with that (and I'm not sure what the benefits would even be over the existing index sites).

midgetspy wrote:

ontrose wrote: Hello getting this error, anyone know how to fix it or what ir means?


2010-06-19 07:28:05.834000 SEARCH :: Error while searching NZBs, skipping: 'ascii' codec can't decode byte 0xf6 in position 319: ordinal not in range(128)

Look in your log and post the whole error that will be near that line and I will take a look.

Dunno if this is what you want, so here it goes.
On a windows 7 pc, with build 454

Hello again, been doing som testing and something seams to be wroing with the 454win32 build.

It wont search for "wanted" episodes, it works if you go to the show and press search then it will fetch it but not when you just start SB.
Then it seams like something has happend to Nzbs.org as far as i can tell the error i reported the other dar is related to Nzbs.
Did a fresh install of 454 build and got the same error, also getting the error when i run the 453 build tho SB moves on to nzbmatrix and searches. Since i dont really know anything about coding or such im quite lost of what info you want me to provide, so if you just can tell me what you need i will try and do my best.

//Ontrose

It doesn't search for every Wanted ep when it starts up, only when they air or when the backlog runs. You can force your backlog in Manage Shows -> Manage Searches.

If there is an NZBs error post the traceback like you did above, I should be able to fix it with that info.

What option do I have to enable to get artwork to show on the Coming Episodes page? Is there an option that downloads just the art for that page? I don't use XBMC or anything it's just a computer hooked to a TV and I browse the folders and don't like tons of other files in there.

midgetspy wrote: It doesn't search for every Wanted ep when it starts up, only when they air or when the backlog runs. You can force your backlog in Manage Shows -> Manage Searches.

If there is an NZBs error post the traceback like you did above, I should be able to fix it with that info.

Before the change from missing to wanted, the missing episodes was searched for at startup right?

Ok, if i may ask what is the "timeframe" when an ep goes from unaired to "aired?" to wanted?
What i mean is the comp that i have SB running on is not turned on all the time so if the XXXX show is airing on tuesday and i shut down my comp on monday and turn it back on during thursday, the episodes that did air on tuesday goes to the backlog?

If this is the case i would like to suggest that if possible annother category would be implemented like "aired" or something that will go over to wanted after a week or so? And the "aired" episodes will be searched for on the start up.

// Ontrose

Gobd: Config -> General -> Create images. Currently that'll also create tbn files for your episodes but that's fixed in the upcoming tvshowv2 branch.

ontrose: Yes and no. There used to be a difference between Missing and Backlog, now they are all just Wanted. Newly-aired Wanted episodes will automatically get downloaded because they will be on the "new" RSS feeds for the providers. If SB isn't running when they are on the index sites' RSS feeds then they will not get searched for until the backlog runs. The backlog system is still a work in progress though so it's possible I will make it search recent episodes more often... but the real solution here is to leave SB running like it's meant to be :0)

midgetspy wrote: Gobd: Config -> General -> Create images. Currently that'll also create tbn files for your episodes but that's fixed in the upcoming tvshowv2 branch.

[...]

Will there also be an option to choose between wide banners and posters?  Or is that option already available but well hidden?  :D


Also, I noticed a strange thing this morning:

2010-06-25 06:38:53 Futurama - 6x01 Snatched   SD TV
2010-06-25 06:38:52 Futurama - 6x01 Snatched   SD TV


The first one was snatched from nzbs.org, the other one from nzbmatrix.

Why was it snatched (and actually added to sabnzb) twice?  ???



[edit]
Second mistery

Apparently, there was a double episode of Futurama last night.  It's listed on TVRage and TheTVDB.
But Sickbeard doesn't know anything about it?  It's not on the missed eps and not on the coming episodes.

Any idea why that is? 

Thought I'd post a "how to" on getting SickBeard installed as a service under Windows Vista (x64 if it makes a difference) with SAB running on a FreeNAS box.

I have SickBeard on a Vista PC and SABnzbd+ running on a FreeNAS box and I wanted auto startup of SickBeard.

It was a story of pain (all my own fault and caused by my lack of understanding of Windows I'm afraid), so if even 1 person learns from my mistakes, job done  ;)

What I eventually did was this:

1) Downloaded and installed the Windows resource kit from here: http://download.microsoft.com/download/ ... ktools.exe

2) Copied the files srvany.exe and instsrv.exe from the windows resource kit directory to my SickBeard root install directory (in my case C:\Program Files (x86)\SickBeard) instsrv.exe is the tool that allows you to easily create a windows service and srvany.exe is a dummy program that allows you to specify (via a couple of registry keys) your executable of choice to run....in this case, SickBeard.exe.

3) Droped into a command prompt in my SickBeard root install directory and executed the following:
4) The above creates the service, now you need to tell it which program to run - in my case, SickBeard.exe, I created a windows .reg file to do this, so it automates the process a little.  This is the content of that file, which I called sickbeard_parameters.reg:
Create a text file of your choice in your SickBeard root install directory (or somewhere for safe keeping), cut and paste the above into it and either execute it from a command prompt, or double click it from windows explorer etc. Follow the on-screen prompts to add the values to the registry.

5) Use the Windows  Services Manager (start>run>services.msc) to set the new "SickBeard" service to start automatically.  I personally have set the recovery options to restart the service at every available opportunity - do this via the "recovery" tab.

6) Start the service using the above tool.

7) Browse to SickBeard and make sure you use a UNC path to your network TV download directory (in my case on one of my FreeNAS boxes).  The reason you must use a UNC path rather than just a drive letter is because a Windows Service is unable to use a drive mapping via it's "friendly" name so-to-speak.  To do this enter an absolute path to the TV download directory (config>episode downloads>Post-Processing>TV Download Dir) like this:
In my case this is something like: \\192.168.n.n\data_share\sabnzbd\downloads\complete\TV

This obviously depends upon you having shared out your tv download area using CIFS\SMB and setting appropriate permissions!

8 ) Make sure the check box for "Config>Episode Downloads>Post-Processing>Scan & Process TV Download Dir" is UNCHECKED

9) Make sure your "Config>Episode Downloads>SABnzbd>Category" is set to "tv"

10) Configure SABnzbd on your remote box so that TV sorting is disabled (I am running 0.52 SAB)

11) Copy the Python scripts from the "scripts" sub-directory on your Windows box to an appropriate directory on your server running SAB.  Keep a note of the directory.

12) Make a copy of the file autoProcessTV.cfg.sample as autoProcessTV.cfg and edit it to reflec the IP and user creds etc of your Windows PC running SickBeard.

13) Make the scripts directory known to SAB, by using the above noted directory and plugging it into the "Config>Folders>Post-Processing Scripts Folder" box.

14) Under your Config>Categories on SAB (remember I am 0.52, yours might be different), set the script for the "TV" category to "sabToSickBeard.py"

15) Give SAB a restart and restart the SickBeard Windows service for good measure.

16) With any luck: stand back, light your pipe and admire your handywork

17) Perhaps kick off a test download that you know should be available and check it all works as it should.  Mine works a treat!

I know that most of the last section has been covered in various posts/places, but for me, following the information available to get windows to start SickBeard automatically as a service was the holy grail and I was not prepared to give up - having a shortcut to SickBeard in my "all users>start>programs>startup" folder was not an acceptable option as it relies on someone logging in.  I like to log in remotely and I don't necessarily always log on to the PC running SickBeard straight after a boot/restart.

ATB,
bikefright.

bikefright wrote: Thought I'd post a "how to" on getting SickBeard installed as a service under Windows Vista (x64 if it makes a difference) with SAB running on a FreeNAS box.



I know that most of the last section has been covered in various posts/places, but for me, following the information availbale to get windows to start SIckBeard automatically as a service was the holy grail and I was not prepared to give up - having a shortcut to SickBeard in my "all users>start>programs>startup" folder was not an acceptable option as it relies on someone logging in.  I like to log in remotely and I don't necessarily always log on to the PC running SickBeard staright after a boot/restart.

ATB,
bikefright.

While I appluad your work and your posting, I'd be remiss if I dodn't link to this app: http://www.firedaemon.com/

Cheers Homerboy - I found a number of posts from folks who had followed the process to install SABnzbd as a service, substituting SABnzbd with SickBeard, but ommiting the "AppParameters" registry entry, but certainly for me, trying to run the SickBeard executable as a service in it's own right would not work - the wrapper that srvany.exe creates was the key and maybe the prog you linked to does something similar, by creating a "wrapper" for any executable you care to throw at it.

The other thing I was getting at was that a windows service (on Vista) cannot use a persistent drive mapping (I map my FreeNAS share to my PC's Z: drive), so even though I (at one point) had the service successfully auto-starting, when the sabToSickBeard.py on my FreeNAS was trying to kick off the post-processing on my SickBeard PC, it (SickBeard as a service) could not interpret my network "Z:" drive specified in my "TV Download Dir".  Proven by hitting the Config>Manual Post-Processing button where none of my network drives were visible/usable (when Sickbeard was running as a service).

Valid point though re software to run "anything you like" as a windows service ;-)

bikefright wrote: Cheers Homerboy - I found a number of posts from folks who had followed the process to install SABnzbd as a service, substituting SABnzbd with SickBeard, but ommiting the parameters registry entry, but certainly for me, trying to run the SickBeard executable as a service in it's own right would not work - the wrapper that srvany.exe creates was the key and maybe the prog you linked to does something similar, by creating a "wrapper" for any executable you care to throw at it.

Valid point though ;-)

Upon further review, what blows is the program I linked USED to be free (haven't used for eons). Seems its pay now, but I'm sure there are similar that are still free.

Regardless, it super-cool that you took the time to write such a detailed how-to.

Fixed