).Right now that doesn't look like anything packaging related.probedb wrote:I've posted another bug over here.... https://forums.sabnzbd.org/index.php?to ... icseen#new
Basically it starts and crashes after 30 seconds to a minute or so. 0.4.9 was fine :/
Thanks for the reply. I'm flattening my box this weekend so we'll see what happens with a clean install.jcfp wrote:Right now that doesn't look like anything packaging related.probedb wrote:I've posted another bug over here.... https://forums.sabnzbd.org/index.php?to ... icseen#new
Basically it starts and crashes after 30 seconds to a minute or so. 0.4.9 was fine :/
For b): post your issue on the beta forum. Packaging doesn't touch such things and I know nothing about this specific funtionality.nomad980 wrote: a) It seems to crash every so often, with or without downloads in the queue.
b) If I change the categories the downloads belong to, they are sent to the last place on the queue.
c) The pages seem to load really slow now compare to when it was on the previous version before 5.
When I check the log it gives me errno 24
Alas, old stuff is actually deleted automatically within 24 hours once superseded by a newer release. Any logs (sab or system) that might help you find out what's wrong?fatboynotsoslim wrote:Question though, am I able to revert back from the latest beta6 of 0.50? I'm getting very unstable behavior that requires me to physically stop sab (via kill -9 id) every morning, as it just locks up during the night (I download 3-9am) and obviously this isn't ideal. I dont know if its sab of my internet connection, but beta 4 and 5 worked admirably.
I've yet to check my system logs, but basically Sabnzbd will get stuck on a few connections, and selecting force disconnect or restart, 'sudo /etc/init.d/sabnzbdplus stop' wont kill the process. Had to kill the process then start it up again in /etc/init.d. It happened once or twice on earlier versions, hence why I was thinking about ruling out beta6 first, since its happened about 3 times in the last week.jcfp wrote:Alas, old stuff is actually deleted automatically within 24 hours once superseded by a newer release. Any logs (sab or system) that might help you find out what's wrong?fatboynotsoslim wrote:Question though, am I able to revert back from the latest beta6 of 0.50? I'm getting very unstable behavior that requires me to physically stop sab (via kill -9 id) every morning, as it just locks up during the night (I download 3-9am) and obviously this isn't ideal. I dont know if its sab of my internet connection, but beta 4 and 5 worked admirably.
Code: Select all
2010-01-19 03:07:21,655::INFO::[downloader:449] [email protected]:563: Initiating connection
2010-01-19 03:07:32,479::INFO::[newswrapper:203] Failed to connect: (110, '[Errno -2] Name or service not known') [email protected]:563
Happens to most of the threads, none connect then:
2010-01-19 04:52:43,927::INFO::[__init__:753] Restarting crashed scheduler
... Same error
2010-01-19 07:33:26,900::INFO::[__init__:753] Restarting crashed scheduler
2010-01-19 07:34:01,946::INFO::[__init__:278] SABnzbd shutting down...
Thats when I manually reset it, and it started up fine.Code: Select all
/usr/share/sabnzbdplus/sabnzbd/utils/ssmtplib.py:116: DeprecationWarning: socket.ssl() is deprecated. Use ssl.wrap_socket() instead.
sslobj = socket.ssl(self.sock, self.keyfile, self.certfile)
ERROR DURING SCHEDULER EXECUTION list index out of range
Traceback (most recent call last):
File "/usr/share/sabnzbdplus/sabnzbd/utils/kronos.py", line 276, in _run
self.sched.run()
File "/usr/lib/python2.6/sched.py", line 111, in run
delayfunc(time - now)
File "/usr/share/sabnzbdplus/sabnzbd/utils/kronos.py", line 103, in __delayfunc
toptime = self._getqueuetoptime()
File "/usr/share/sabnzbdplus/sabnzbd/utils/kronos.py", line 262, in _getqueuetoptime
return self.sched._queue[0].time
IndexError: list index out of range
. Report this as a bug in the beta releases forum; be sure to include logging excerpts just like you have here. If you need a b5 (or rc2) package for comparison or further investigation, drop me a pm.Code: Select all
Exception in thread HTTPServer Thread-10:
Traceback (most recent call last):
File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
self.run()
File "/usr/lib/python2.5/threading.py", line 446, in run
self.__target(*self.__args, **self.__kwargs)
File "/usr/share/sabnzbdplus/cherrypy/process/servers.py", line 75, in _start_http_thread
self.httpserver.start()
File "/usr/share/sabnzbdplus/cherrypy/wsgiserver/__init__.py", line 1629, in start
raise socket.error, msg
error: (99, 'Cannot assign requested address')Code: Select all
2010-01-22 13:25:46,854::ERROR::[misc:453] You have no permisson to use port 8181The rc3 package has a minor change in the behaviour of the init script. Previously, it would only use the HOST and PORT settings in /etc/default/sabnzbdplus if both were set; now, setting just one of 'm also takes effect. As a result, if you had only the PORT set (which had no effect at all), it will now start using that as --server :port which is where the hostname guessing game begins. Unfortunately, Ubuntu isn't very steadfast in how it handles that.s1nglebarrel wrote: I am getting some weird behavior on the latest RC3 release. After updating when I launc sabnzbd via init.d it fails and drops errors in the logs like the ones below
