Episode Bulter and SAB 5.0

[JayBird]

Is there any know issues with Episode Butler and the new sabnzbd 5.0 beta?

Episode bulter is finding my episodes, but they never appear in the sab queue.

Everything was working fine with 0.4.12

Im wondering if it is an authentication issue becuase of the new sab login method.

Any ideas?

This is what is see in the OSX console

Code: Select all

30/11/2009 09:53:00	[0x0-0x2b02b].com.apple.JarLauncher[369]	Nov 30, 2009 9:53:00 AM com.janoz.eb.Core doEpisodeUpdate
30/11/2009 09:53:00	[0x0-0x2b02b].com.apple.JarLauncher[369]	INFO: Fetching Top Gear
30/11/2009 09:53:07	[0x0-0x2b02b].com.apple.JarLauncher[369]	Nov 30, 2009 9:53:07 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme
30/11/2009 09:53:07	[0x0-0x2b02b].com.apple.JarLauncher[369]	INFO: basic authentication scheme selected
30/11/2009 09:53:07	[0x0-0x2b02b].com.apple.JarLauncher[369]	Nov 30, 2009 9:53:07 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme
30/11/2009 09:53:07	[0x0-0x2b02b].com.apple.JarLauncher[369]	INFO: basic authentication scheme selected
30/11/2009 09:53:08	[0x0-0x2b02b].com.apple.JarLauncher[369]	Nov 30, 2009 9:53:08 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme
30/11/2009 09:53:08	[0x0-0x2b02b].com.apple.JarLauncher[369]	INFO: basic authentication scheme selected
30/11/2009 09:53:08	[0x0-0x2b02b].com.apple.JarLauncher[369]	Nov 30, 2009 9:53:08 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme
30/11/2009 09:53:08	[0x0-0x2b02b].com.apple.JarLauncher[369]	INFO: basic authentication scheme selected
30/11/2009 09:53:08	[0x0-0x2b02b].com.apple.JarLauncher[369]	Nov 30, 2009 9:53:08 AM org.apache.commons.httpclient.HttpMethodDirector processWWWAuthChallenge
30/11/2009 09:53:08	[0x0-0x2b02b].com.apple.JarLauncher[369]	INFO: No credentials available for BASIC 'SABnzbd'@192.168.1.2:8181

Thanks

[RageX]

EpisodeButler has also stopped working for me with the upgrade to SABnzbd+ 0.5 beta

[Duffman]

I am having the same problem

[rollingeyeball]

Are you guys using the version that uses the apikey?
Janoz released an update a fair while ago that makes use of the apikey iirc.

If you are- my bad. sorry

[RageX]

Yeah I am.

[JayBird]

Yep, im using the latest version too.

Janoz pops into these forums from time-to-time i believe so hopefully he will see this soon.

Im going to try disabling my SABnzbd login tonight to see if episode butler will then send the report id

[Janoz]

The current version of the Episode Butler does NOT support sabnzbd 5.0. The new EB 0.9 version does support the new sabnzbd beta, but it isn't in a releasable state unfortunately. A possible workaround is using a watch folder. Configure the Episode Butler to save the nzb's to disk (using the filesaver) and let sabnzbd watch this folder. It isn't a nice solution, but I hope it will do until the new version is available.

Things I still have to do for the new version are:
- creating screens for the configuration (new version is configured from the webinterface instead of a properties file)
- testing the upgrade (connection to TvRage is more robust but requires an addition to the existing data)
- storage of configuration data.

Since 5.0 is around the corner I have to re-prioritize and put other projects on hold. I hope I can finish 0.9 before the end of this year.

[JayBird]

Thank you for the update Janoz.

Looking forward to the update!

[Ancillas]

If you disable authentication in SABnzbd (delete the username and password), Episode Butler will successfully add items to the queue by report ID.  I am using this as a workaround until episode butler is updated.  Run without authentication at your own risk.

I don't know about anyone else, but the new HTTP authentication has caused me several headaches.

[MrAcid]

If you disable authentication in SABnzbd (delete the username and password), Episode Butler will successfully add items to the queue by report ID.  I am using this as a workaround until episode butler is updated.  Run without authentication at your own risk.

I don't know about anyone else, but the new HTTP authentication has caused me several headaches.

Can anyone confirm this?

[JayBird]

Can anyone confirm this?

yes, this is what I am doing until the episode butler update is release

[opet]

This does not work for me... Did you just delete the user + pass in the config file for Butler as well as the ones in SAB config? Add a restart and thats it?

[JayBird]

This does not work for me... Did you just delete the user + pass in the config file for Butler as well as the ones in SAB config? Add a restart and thats it?

yep, that's all I did

[MrAcid]

I'll try it later today then. Sounds pretty easy! :-) Thanks.

[Ancillas]

I let episode butler run for a week's worth of shows and everything is still working as expected with authentication disabled.  Just a side note, you can keep your API key enabled; it's just the username and password that need to be removed.