Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings.
Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Hi all, was happily running until earlier today when I ran 'apt-get update' and 'apt-get upgrade', receiving 0.4.7. Now, I receive this when accessing sabnzbd's web server:
500 Internal error
The server encountered an unexpected condition which prevented it from fulfilling the request.
Traceback (most recent call last):
File "/var/lib/python-support/python2.5/cherrypy/_cphttptools.py", line 126, in _run
applyFilters('before_finalize')
File "/var/lib/python-support/python2.5/cherrypy/filters/__init__.py", line 151, in applyFilters
method()
File "/var/lib/python-support/python2.5/sabnzbd/utils/multiauth/filter.py", line 61, in beforeFinalize
**rsrc.callable_kwargs)
File "/var/lib/python-support/python2.5/sabnzbd/interface.py", line 309, in index
return template.respond()
File "cheetah__usr_share_sabnzbdplus_interfaces_Plush_templates_main_tmpl_1235717246_1_23420.py", line 368, in respond
NotFound: cannot find 'darwin'
I'm not really sure where to go from here -- my sabnzbd install is pretty plain, but everything is working for other people..? Any thoughts?
amerrykan wrote:was happily running until earlier today when I ran 'apt-get update' and 'apt-get upgrade', receiving 0.4.7. Now, I receive this when accessing sabnzbd's web server:
Be sure to restart the program after upgrading - otherwise, you might end up mixing the program and interfaces from different versions (in this case, the running program at version 0.4.6 is likely trying to use the newly updated interface templates belonging to 0.4.7).
jcfp wrote:Be sure to restart the program after upgrading - otherwise, you might end up mixing the program and interfaces from different versions (in this case, the running program at version 0.4.6 is likely trying to use the newly updated interface templates belonging to 0.4.7).
Yup, Plush is working after 'sudo /etc/init.d/sabnzbdplus restart'. Feeling pretty stupid, but maybe this will help somebody else. Thanks for your help!
shypike wrote:JCFP, is it possible to force a shutdown of SABnzbd before upgrading it?
We do that in the Windows installer.
Shutting something down is never a problem if you can run scripts as root . In fact, for users of the init script (re)starting it after a package upgrade could also be done automatically. Thus far, I didn't do such things because the program doesn't seem to like being shutdown while verifying or extracting... iirc (quite a while back since I looked at this) sabnzbd always shuts down fine but leaves par and unrar running, leading to a mismatch with its own job accounting when it's started again?
No data loss though fafaik, so it could be done this way anyway if this isn't considered too much of an inconvenience (as compared to the issue with mixing template version). Thoughts?
Thanks a lot for this repository. It makes running sabnzbd+ on Ubuntu much simpler. However during today's Jaunty update I got a very similar python error when trying to refresh the sabnzbd+ page. Well guess, what? The update almost totally removed sabnzbd+. Now, not even /usr/bin/sabnzbdplus is left. Trying to install sabnzbd+ again reveals a major conflict with the new python-2.6.
razor1394@leonis:~$ sudo apt-get install sabnzbdplus
Läser paketlistor... Färdig
Bygger beroendeträd
Läser tillståndsinformation... Färdig
Några paket kunde inte installeras. Det kan betyda att du har begärt
en omöjlig situation eller, om du använder den instabila utgåvan
att några nödvändiga paket ännu inte har skapats eller flyttats
ut från "Incoming".
Följande information kan vara till hjälp för att lösa situationen:
Följande paket har beroenden som inte kan tillfredsställas:
sabnzbdplus: Beroende av: python (< 2.6) men 2.6.1-0ubuntu1 kommer att installeras
Beroende av: python-cheetah (>= 2.0.1) men det kommer inte att installeras
Rekommenderar: python-yenc (>= 0.3) men det kommer inte att installeras
E: Trasiga paket
I get the same message on my other Ubuntu Jaunty i386 machine (Both are i386).
Följande paket har beroenden som inte kan tillfredsställas:
sabnzbdplus: Beroende av: python (< 2.6) men 2.6.1-0ubuntu1 kommer att installeras
Beroende av: python-cheetah (>= 2.0.1) men det kommer inte att installeras
Rekommenderar: python-yenc (>= 0.3) men det kommer inte att installeras
E: Trasiga paket
Ubuntu is making python-2.6 the default python right now, this has severe impact on the usability of systems running jaunty (rumor has it that "upgrade" rather than "dist-upgrade" leaves it somewhat functional with regard to program requiring python < 2.6). Can't give you any real advise other than to wait a few days until the dust settles.
I just did a fresh install of Jaunty Alpha 5, and found "Python 2.5.4". So, that's good. However, after an update of 148 MB, "Python 2.6.1+ (r261:67515, Feb 24 2009, 16:56:08)" was installed.
Trying to install the SABnzbd dependencies resulted in the error message below. I'm not an expert, but I think this is not a pure SABnzbd problem, but a python vs python-cheetah problem. As python-cheetah is part of the Ubuntu repository, it's my (naive?) thought that the Ubuntu maintariners should take care of this in the coming days/weeks. And/but maybe that's what jcfp already said.
sander@jaunty:~$ sudo apt-get install python python-cherrypy python-cheetah python-elementtree python-yenc python-celementtree python-feedparser unrar unzip par2 python-openssl
[sudo] password for sander:
Reading package lists... Done
Building dependency tree
Reading state information... Done
python is already the newest version.
unzip is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
python-cheetah: Depends: python (< 2.6) but 2.6.1-0ubuntu1 is to be installed
python-yenc: Depends: python (< 2.6) but 2.6.1-0ubuntu1 is to be installed
E: Broken packages
sander@jaunty:~$
Last edited by sander on February 28th, 2009, 11:23 am, edited 1 time in total.
Please don't send me unrequested PM's; the forum is the best way to communicate.
If someone helps you, please reply to that help.
f you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
There are regression/hold back options in the aptitude application but I'm not so used to to aptitude on Ubuntu. I'm more used to working with gentoo and package.mask. You should be able to lock out python 2.6 with it
python-cheetah: Depends: python (< 2.6) but 2.6.1-0ubuntu1 is to be installed
python-yenc: Depends: python (< 2.6) but 2.6.1-0ubuntu1 is to be installed
I would like to hear advice from others: is it clever to file a bug related to python-cheetah and python-yenc (not sabnzbd which is probably too remote)?
Please don't send me unrequested PM's; the forum is the best way to communicate.
If someone helps you, please reply to that help.
f you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Thanks for your help!
. In fact, for users of the init script (re)starting it after a package upgrade could also be done automatically. Thus far, I didn't do such things because the program doesn't seem to like being shutdown while verifying or extracting... iirc (quite a while back since I looked at this) sabnzbd always shuts down fine but leaves par and unrar running, leading to a mismatch with its own job accounting when it's started again?
