Page 1 of 1

[Solved]Repeated crashing

Posted: March 3rd, 2017, 4:53 pm
by identd
I was using the 2.0 beta release, but reverted to 1.2.2, and am still getting these messages in the log:

```
2017-03-03 15:42:45,287::INFO::[_cplogging:219] [03/Mar/2017:15:42:45] ENGINE Stopped thread '_TimeoutMonitor'.
2017-03-03 15:42:45,288::INFO::[_cplogging:219] [03/Mar/2017:15:42:45] ENGINE Bus STOPPED
2017-03-03 15:42:45,289::INFO::[_cplogging:219] [03/Mar/2017:15:42:45] ENGINE Bus EXITING
2017-03-03 15:42:45,289::INFO::[_cplogging:219] [03/Mar/2017:15:42:45] ENGINE Bus EXITED
2017-03-03 15:42:49,345::INFO::[_cplogging:219] [03/Mar/2017:15:42:49] ENGINE Bus STARTING
2017-03-03 15:42:49,349::INFO::[_cplogging:219] [03/Mar/2017:15:42:49] ENGINE Started monitor thread '_TimeoutMonitor'.
2017-03-03 15:42:49,487::INFO::[_cplogging:219] [03/Mar/2017:15:42:49] ENGINE Serving on http://0.0.0.0:7005
2017-03-03 15:42:49,488::INFO::[_cplogging:219] [03/Mar/2017:15:42:49] ENGINE Bus STARTED
2017-03-03 15:43:22,503::INFO::[_cplogging:219] [03/Mar/2017:15:43:22] ENGINE Bus STOPPING
2017-03-03 15:43:22,506::INFO::[_cplogging:219] [03/Mar/2017:15:43:22] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 7005)) shut down
2017-03-03 15:43:22,506::INFO::[_cplogging:219] [03/Mar/2017:15:43:22] ENGINE Stopped thread '_TimeoutMonitor'.
2017-03-03 15:43:22,506::INFO::[_cplogging:219] [03/Mar/2017:15:43:22] ENGINE Bus STOPPED
2017-03-03 15:43:22,507::INFO::[_cplogging:219] [03/Mar/2017:15:43:22] ENGINE Bus EXITING
2017-03-03 15:43:22,507::INFO::[_cplogging:219] [03/Mar/2017:15:43:22] ENGINE Bus EXITED
2017-03-03 15:43:27,270::INFO::[_cplogging:219] [03/Mar/2017:15:43:27] ENGINE Bus STARTING
2017-03-03 15:43:27,282::INFO::[_cplogging:219] [03/Mar/2017:15:43:27] ENGINE Started monitor thread '_TimeoutMonitor'.
2017-03-03 15:43:27,435::INFO::[_cplogging:219] [03/Mar/2017:15:43:27] ENGINE Serving on http://0.0.0.0:7005
2017-03-03 15:43:27,437::INFO::[_cplogging:219] [03/Mar/2017:15:43:27] ENGINE Bus STARTED
2017-03-03 15:44:00,449::INFO::[_cplogging:219] [03/Mar/2017:15:44:00] ENGINE Bus STOPPING
2017-03-03 15:44:00,452::INFO::[_cplogging:219] [03/Mar/2017:15:44:00] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 7005)) shut down
2017-03-03 15:44:00,452::INFO::[_cplogging:219] [03/Mar/2017:15:44:00] ENGINE Stopped thread '_TimeoutMonitor'.
2017-03-03 15:44:00,453::INFO::[_cplogging:219] [03/Mar/2017:15:44:00] ENGINE Bus STOPPED
2017-03-03 15:44:00,453::INFO::[_cplogging:219] [03/Mar/2017:15:44:00] ENGINE Bus EXITING
2017-03-03 15:44:00,453::INFO::[_cplogging:219] [03/Mar/2017:15:44:00] ENGINE Bus EXITED
2017-03-03 15:44:03,974::INFO::[_cplogging:219] [03/Mar/2017:15:44:03] ENGINE Bus STARTING
2017-03-03 15:44:03,979::INFO::[_cplogging:219] [03/Mar/2017:15:44:03] ENGINE Started monitor thread '_TimeoutMonitor'.
2017-03-03 15:44:04,116::INFO::[_cplogging:219] [03/Mar/2017:15:44:04] ENGINE Serving on http://0.0.0.0:7005
2017-03-03 15:44:04,117::INFO::[_cplogging:219] [03/Mar/2017:15:44:04] ENGINE Bus STARTED
2017-03-03 15:44:37,126::INFO::[_cplogging:219] [03/Mar/2017:15:44:37] ENGINE Bus STOPPING
2017-03-03 15:44:37,129::INFO::[_cplogging:219] [03/Mar/2017:15:44:37] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 7005)) shut down
2017-03-03 15:44:37,129::INFO::[_cplogging:219] [03/Mar/2017:15:44:37] ENGINE Stopped thread '_TimeoutMonitor'.
2017-03-03 15:44:37,130::INFO::[_cplogging:219] [03/Mar/2017:15:44:37] ENGINE Bus STOPPED
2017-03-03 15:44:37,130::INFO::[_cplogging:219] [03/Mar/2017:15:44:37] ENGINE Bus EXITING
2017-03-03 15:44:37,130::INFO::[_cplogging:219] [03/Mar/2017:15:44:37] ENGINE Bus EXITED
2017-03-03 15:44:41,263::INFO::[_cplogging:219] [03/Mar/2017:15:44:41] ENGINE Bus STARTING
2017-03-03 15:44:41,268::INFO::[_cplogging:219] [03/Mar/2017:15:44:41] ENGINE Started monitor thread '_TimeoutMonitor'.
2017-03-03 15:44:41,398::INFO::[_cplogging:219] [03/Mar/2017:15:44:41] ENGINE Serving on http://0.0.0.0:7005
2017-03-03 15:44:41,398::INFO::[_cplogging:219] [03/Mar/2017:15:44:41] ENGINE Bus STARTED
2017-03-03 15:45:14,406::INFO::[_cplogging:219] [03/Mar/2017:15:45:14] ENGINE Bus STOPPING
2017-03-03 15:45:14,408::INFO::[_cplogging:219] [03/Mar/2017:15:45:14] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 7005)) shut down
2017-03-03 15:45:14,409::INFO::[_cplogging:219] [03/Mar/2017:15:45:14] ENGINE Stopped thread '_TimeoutMonitor'.
2017-03-03 15:45:14,409::INFO::[_cplogging:219] [03/Mar/2017:15:45:14] ENGINE Bus STOPPED
2017-03-03 15:45:14,409::INFO::[_cplogging:219] [03/Mar/2017:15:45:14] ENGINE Bus EXITING
2017-03-03 15:45:14,410::INFO::[_cplogging:219] [03/Mar/2017:15:45:14] ENGINE Bus EXITED
2017-03-03 15:45:19,265::INFO::[_cplogging:219] [03/Mar/2017:15:45:19] ENGINE Bus STARTING
2017-03-03 15:45:19,271::INFO::[_cplogging:219] [03/Mar/2017:15:45:19] ENGINE Started monitor thread '_TimeoutMonitor'.
2017-03-03 15:45:19,413::INFO::[_cplogging:219] [03/Mar/2017:15:45:19] ENGINE Serving on http://0.0.0.0:7005
2017-03-03 15:45:19,413::INFO::[_cplogging:219] [03/Mar/2017:15:45:19] ENGINE Bus STARTED
```

This repeats until process is killed, any idea how to get more verbose logs?
Update: I downloaded the debug logs form the interface, but this just outputs the .ini file in addition to the above message

-MIkeW

Re: Repeated crashing

Posted: March 3rd, 2017, 5:12 pm
by safihre
In the Status window, can you switch the logging level to +Debug?
Then wait until this crash happens again, then we have the new logs.

Re: Repeated crashing

Posted: March 3rd, 2017, 5:13 pm
by sander
If the webinterface isn't starting anymore, from the commandline, you can start SABnzbd with "-l 2":

Code: Select all

-l  --logging <0..2>     Set logging level (-1=off, 0= least, 2= most) [*]

Re: Repeated crashing

Posted: March 3rd, 2017, 6:50 pm
by identd
The error is:

2017-03-03 17:48:04,644::INFO::[rss:554] Finished scheduled RSS read-outs
2017-03-03 17:48:06,975::INFO::[__init__:1081] Restarting because of crashed downloader
2017-03-03 17:48:06,976::INFO::[_cplogging:219] [03/Mar/2017:17:48:06] ENGINE Bus STOPPING
2017-03-03 17:48:06,995::INFO::[_cplogging:219] [03/Mar/2017:17:48:06] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 7005)) shut down
2017-03-03 17:48:06,995::INFO::[_cplogging:219] [03/Mar/2017:17:48:06] ENGINE Stopped thread '_TimeoutMonitor'.
2017-03-03 17:48:06,995::INFO::[_cplogging:219] [03/Mar/2017:17:48:06] ENGINE Bus STOPPED
2017-03-03 17:48:06,995::INFO::[_cplogging:219] [03/Mar/2017:17:48:06] ENGINE Bus EXITING
2017-03-03 17:48:06,996::INFO::[_cplogging:219] [03/Mar/2017:17:48:06] ENGINE Bus EXITED

When running:

grep "Finished scheduled RSS read-outs" -A 2 ~/Library/Application\ Support/SABnzbd/logs/sabnzbd.log

I get:

2017-03-03 17:46:50,216::INFO::[rss:554] Finished scheduled RSS read-outs
2017-03-03 17:46:52,708::INFO::[__init__:1081] Restarting because of crashed downloader
2017-03-03 17:46:52,708::INFO::[_cplogging:219] [03/Mar/2017:17:46:52] ENGINE Bus STOPPING
--
2017-03-03 17:47:27,049::INFO::[rss:554] Finished scheduled RSS read-outs
2017-03-03 17:47:29,959::INFO::[__init__:1081] Restarting because of crashed downloader
2017-03-03 17:47:29,959::INFO::[_cplogging:219] [03/Mar/2017:17:47:29] ENGINE Bus STOPPING
--
2017-03-03 17:48:04,644::INFO::[rss:554] Finished scheduled RSS read-outs
2017-03-03 17:48:06,975::INFO::[__init__:1081] Restarting because of crashed downloader
2017-03-03 17:48:06,976::INFO::[_cplogging:219] [03/Mar/2017:17:48:06] ENGINE Bus STOPPING

Re: Repeated crashing

Posted: March 4th, 2017, 2:11 am
by safihre
And this is also with 2.0.0? Crashed Downloader.. That's very unique.
Instead of that grep, can you just send me the whole log (download from Show logging in the Status window) at [email protected]?

Have you tried clearing the queue? Or doing a queue repair?

Re: Repeated crashing

Posted: March 4th, 2017, 2:27 pm
by identd
I sent in a set of logs for you for look at, thank you for that,
I have tried doing queue repair, and emptying the queue, The laster works, but as soon as I add something, within 30 seconds, the server restarts.
I also disabled my RSS feed, and that did not make a difference.

I removed the folder on application support, and restarted sab. Once started, I swapped out the .ini file and restarted. Upon adding a nzb a crash occurred (within 30 seconds)

Re: Repeated crashing

Posted: March 7th, 2017, 6:34 pm
by identd
@safihre
Did you get my logs, and is there a way to get more information aside from the "Downloader has crashed"?

Re: Repeated crashing

Posted: March 8th, 2017, 2:29 pm
by identd
I ran this as source, and the error I get is more descriptive:

Exception in thread Thread-7:
Traceback (most recent call last):
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 810, in __bootstrap_inner
self.run()
File "/Applications/sabnzbd/sabnzbd/downloader.py", line 611, in run
BPSMeter.do.update(server.id, bytes)
File "/Applications/sabnzbd/sabnzbd/bpsmeter.py", line 247, in update
if sabnzbd.downloader.Downloader.do and not Downloader.do.paused:
NameError: global name 'Downloader' is not defined

Re: Repeated crashing

Posted: March 8th, 2017, 10:55 pm
by identd
I reverted the .ini file from one a week or so ago, and it worked fine.
I diff'd the files, and saved the report.
I will email this link to you.
item on left was the working version, and the one on the right is the file "broken"