SABnzbd Forums

Version: 0.6.9
OS: OSX Lion
Install-type: OSx .app,
Firewall Software: OSX Firewall
Are you using IPV6? no
Is the issue reproducible? no

I'm running Sabnxbd+ on OSX Lion, being fed by SickBeard in the main.

Every so often I noticed that the app just isn't running anymore? It's usually in the middle of downloading a few files when I restart it up again.

Nothing in the logs, no failures, nothing, it has just unloaded itself.
Starting the app up again it happily continues as if nothing happened.

It can go for a week without doing this, and then do it 2 days in a row.

Does this happen to anyone else? I have no idea what could be causing it, it never used to happen on Snow Leopard as far as I can recall.
Rolling back to 0.6.6 it seems a bit more stable and this happens less frequently than using 0.6.9, but it still happens.

Any ideas?

Have you scanned SAB's log file? It's here: http://localhost:8080/connections/ -> Latest Warning -> Show logging.

I have, nothing in there that shows it is shutting down, nor any reason it would.

Anybody else getting this, I can't be the only OSX user here

I am having the same problem. I am running 6.9.0 on Arch Linux. It will run for a day sometimes, maybe 10 minutes, maybe an hour. The logs show that it stops after decoding with yenc. I have tried rolling back yenc and still getting the same result.

brad0383 wrote:I am having the same problem. I am running 6.9.0 on Arch Linux. It will run for a day sometimes, maybe 10 minutes, maybe an hour. The logs show that it stops after decoding with yenc. I have tried rolling back yenc and still getting the same result.

I would do this: run sabnzbd / sabnzbdplus from the command line (so: in a terminal). As soon as it stops, copy-paste the text in the terminal into this thread.

See log below, it always just stops working while decoding.

*filenames changed

brad0383 wrote:See log below, it always just stops working while decoding.

*filenames changed

Code: Select all

2011-10-15 21:02:45,580::INFO::[assembler:85] Decoding /usr/share/sabnzbd/Downloads/incomplete/xxxxxxxxxxxxxxxxxxxxxxxxxxxx.r11 yenc
2011-10-15 21:04:56,561::INFO::[__init__:838] Saving data for totals9.sab in /usr/share/sabnzbd/admin/totals9.sab
2011-10-15 21:04:56,562::INFO::[assembler:85] Decoding /usr/share/sabnzbd/Downloads/incomplete/xxxxxxxxxxxxxxxxxxxxxxxxxxxx.r12 yenc
2011-10-15 21:07:13,907::INFO::[__init__:838] Saving data for totals9.sab in /usr/share/sabnzbd/admin/totals9.sab
2011-10-15 21:07:13,907::INFO::[assembler:85] Decoding /usr/share/sabnzbd/Downloads/incomplete/xxxxxxxxxxxxxxxxxxxxxxxxxxxx.r13 yenc
2011-10-15 21:09:33,056::INFO::[__init__:838] Saving data for totals9.sab in /usr/share/sabnzbd/admin/totals9.sab
2011-10-15 21:09:33,056::INFO::[assembler:85] Decoding /usr/share/sabnzbd/Downloads/incomplete/xxxxxxxxxxxxxxxxxxxxxxxxxxxx.r14 yenc

I don't see a command prompt at the end, so I would think 1) SAB has not stopped, or 2) this is not the output from the CLI / terminal.

There could be some stability problem.
The easiest way out is to schedule a daily restart in the SABnzbd scheduler.
(Restart of SABnzbd, not of the system).

sander wrote:

brad0383 wrote:See log below, it always just stops working while decoding.

*filenames changed

Code: Select all

2011-10-15 21:02:45,580::INFO::[assembler:85] Decoding /usr/share/sabnzbd/Downloads/incomplete/xxxxxxxxxxxxxxxxxxxxxxxxxxxx.r11 yenc
2011-10-15 21:04:56,561::INFO::[__init__:838] Saving data for totals9.sab in /usr/share/sabnzbd/admin/totals9.sab
2011-10-15 21:04:56,562::INFO::[assembler:85] Decoding /usr/share/sabnzbd/Downloads/incomplete/xxxxxxxxxxxxxxxxxxxxxxxxxxxx.r12 yenc
2011-10-15 21:07:13,907::INFO::[__init__:838] Saving data for totals9.sab in /usr/share/sabnzbd/admin/totals9.sab
2011-10-15 21:07:13,907::INFO::[assembler:85] Decoding /usr/share/sabnzbd/Downloads/incomplete/xxxxxxxxxxxxxxxxxxxxxxxxxxxx.r13 yenc
2011-10-15 21:09:33,056::INFO::[__init__:838] Saving data for totals9.sab in /usr/share/sabnzbd/admin/totals9.sab
2011-10-15 21:09:33,056::INFO::[assembler:85] Decoding /usr/share/sabnzbd/Downloads/incomplete/xxxxxxxxxxxxxxxxxxxxxxxxxxxx.r14 yenc

I don't see a command prompt at the end, so I would think 1) SAB has not stopped, or 2) this is not the output from the CLI / terminal.

This is the output from the log file. It is the same as the CLI. SAB does indeed stop.

There could be some stability problem.
The easiest way out is to schedule a daily restart in the SABnzbd scheduler.
(Restart of SABnzbd, not of the system).

I don't like that idea, it's a band aid.

brad0383 wrote:

sander wrote:

brad0383 wrote:See log below, it always just stops working while decoding.

*filenames changed

Code: Select all

2011-10-15 21:02:45,580::INFO::[assembler:85] Decoding /usr/share/sabnzbd/Downloads/incomplete/xxxxxxxxxxxxxxxxxxxxxxxxxxxx.r11 yenc
2011-10-15 21:04:56,561::INFO::[__init__:838] Saving data for totals9.sab in /usr/share/sabnzbd/admin/totals9.sab
2011-10-15 21:04:56,562::INFO::[assembler:85] Decoding /usr/share/sabnzbd/Downloads/incomplete/xxxxxxxxxxxxxxxxxxxxxxxxxxxx.r12 yenc
2011-10-15 21:07:13,907::INFO::[__init__:838] Saving data for totals9.sab in /usr/share/sabnzbd/admin/totals9.sab
2011-10-15 21:07:13,907::INFO::[assembler:85] Decoding /usr/share/sabnzbd/Downloads/incomplete/xxxxxxxxxxxxxxxxxxxxxxxxxxxx.r13 yenc
2011-10-15 21:09:33,056::INFO::[__init__:838] Saving data for totals9.sab in /usr/share/sabnzbd/admin/totals9.sab
2011-10-15 21:09:33,056::INFO::[assembler:85] Decoding /usr/share/sabnzbd/Downloads/incomplete/xxxxxxxxxxxxxxxxxxxxxxxxxxxx.r14 yenc

I don't see a command prompt at the end, so I would think 1) SAB has not stopped, or 2) this is not the output from the CLI / terminal.

This is the output from the log file. It is the same as the CLI. SAB does indeed stop.

That's why I explicitly said you need to run SAB from the CLI; a crashed program can not write to a log file (as it's dead and gone), so you won't find the crash info there. As the OS is still running, it will report on the CLI what happened and hopefully why/what crashed.

It may take awhile for it to crash. Standby.

Do you happen to download very large jobs, like above 25G?
Not total queue size, but of individual items.

No, the largest would be around 500M. I am going to try reinstalling and using all the defaults. I think may be related to the web interface authentication.

brad0383 wrote:I think may be related to the web interface authentication.

If there are no browser tabs communicating with SABnzbd, then the Web UI cannot be a factor.