SABnzbd Forums

I've just started controlling SAB remotely from my second laptop, (both using os x 10.5.6, sab 0.4.7) and for some reason whenever I try and load the queue page remotely, it will only display the first 10 or so items and then it seems to just get cut off suddenly (like it will draw perhaps a few columns of a line and then stop)

i did notice this would happen occasionally when looking at the queue page on the localhost, but then just refreshing the page would always fix the problem. when I access it remotely though no matter what I do I can't get it to display the whole queue.

its quite long, possibly about 50 or so entries

i'm connecting via my wireless router, and using the ip of the machine running sab on my local network (ie 192.168.1.xx:8080/sabnzbd) as the url I have tried setting the host in the config to both blank and 0.0.0.0.

i have tried with the os x firewall turned off on both machines and this makes no difference

is there any way I can fix this? is my queue just too big?!

I have this problem too... Is somone using SAB on other platform have the same issue ?

Never happened to me on windows.

well its only really a problem when accessing it remotely, with it being hosted on os x.

thought perhaps it was the browser but camino made no difference (infact it cuts off in the exact same place). looking at the page source it appears to just get cut off all of a sudden as if the connection died or timed out or something before it loaded the whole page (although it loads very quickly).

using the simpl theme remotely it doesnt even load the graph at the bottom and none of the links work. having slightly more success with plush, in that it will sometimes display the whole queue if i reload a few times.

could this be something to do with the way the html is being served up that is specific to python on os x?

switch wrote: Never happened to me on windows.

please dont let this me a mac vs win thing 

a page that should be viewable in IE should be equally viewable on safari, firefox etc etc. After all, not everyone drives a VW 

Well the issue is most likely with the web server we use (cherrypy). It can have different bugs depending on which platforms it is running on hence why this looks like a Mac only bug.

My main advice would be to wait for 0.5 alpha as that uses an upgraded version of cherrypy.

I don't remember what version is used in osx package, I'll check if I can build with another version.
I'll report results here monday.

SABnzbd 0.4.7 uses the most recent CherryPy-2.x release, which is 2.3.0.
At least I hope you used that one for your OSX release.

It's not possible to use CherryPy-3.x for SABnzbd 0.4.x

Yes shypike, I remember upgrading to 2.3.0 but I need to check to be sure.
and of course no 3.x for 0.4x

I have had identical problems with SABnzbd(I have been upgrading my versions all along).  The only thing that fixes this issue is to bind to port something other than 8080. 

The moment I changed the config to port 8090 in my case, things started working like a charm.  I monkeyed around a lot to see what was going on, but I just could not find anything.  There was no other service running, there was nothing that was being bound to the port etc, but SAB would just not startup to port 8080.

Some interesting infos found in this Cherrypy trac :

http://www.cherrypy.org/ticket/598

It seems that there is an old problem affecting OSX.

I've checked and I'm using the latest version of CherryPy in OSX build but not lastest python (2.5.2)
I've updated python to 2.5.4 and tested and same issue occurs.

I've try to patch CherryPy with that (from the link above not mine) :

Inside def tick(), comment out these two lines:
And add these two:
And it seems to work... if someone wants to test here a link to a SAB patched version

It seems that internal Apple python may work, I'll try to test but we can't use this because we'll loose 10.4, 10.5 compatibility...

rAf

I will try it out and let you guys know.

Raf,

I tried the updated release, unfortunately I am running into the same problem.  SAB running out of port 8080 seems to crap out after some time.  I switch to port 8090 and things are just fine. 

Best,
b1scu1t

I wonder if you have the same issue. It's strange because, I'm using this build all day without any problem, I've loaded 100+ nzb without any display issue.
I don't see why you have issue on 8080 and not 8090...

rAf

Edit : I'll try official build with 8090 to see if it works for me.
Edit2 : Tested with 8090 with official build, I have the bug, so I think you have an another issue...

Tried with port 8888.. same issue.