Support Forum

...and this morning I come back to a crashed sab again :( Same message as always in the console log, so it doesn't look like it it the apple python library causing it. In fact checking the download history, nothing has been sent to sab at all since I installed the ActiveState variant, so all it has ...

Installed no problems and the top menu is back.
I'll report back in a couple of days as to whether it is stable.

Thanks a lot!

Sure thing, I'll grab it now
The Leopard install is still up and running by the way, so looking very promising.

Still up and running after 30 hours, looking promising
I do miss the top menu though

Leopard version installed, i'll turn off my restart script too and report back

If anything turns up, then I'll let you know. It has to be to do with the cvwait log message, which seems to be some sort of low level threading issue. But without any more logging than that, it'll be impossible to track down. Is there a higher level of logging I can switch on and give you the conte...

Yup, nothing was happening at the time of the crash, as far as I can tell, full extent of the logs around that time: 2012-03-11 01:10:01,320::INFO::[postproc:83] Saving postproc queue 2012-03-11 01:10:01,320::INFO::[__init__:846] Saving data for postproc1.sab in /Users/trooper/Library/Application Su...

Results as follows Time Real mem Virtual mem Private mem Shared mem 12:00 147.3 132.0 35.9 198.0 13:48 149.8 135.1 36.2 199.8 17:02 168.3 151.6 36.2 216.5 18:10 169.5 151.8 36.2 216.9 22:23 172.1 158.5 34.5 222.0 09:38 64.9 57.1 13.7 128.2 According to the logs it crashed at some point in the night,...

shypike wrote: Does a running SABnzbd show a steadily increasing memory usage while it's still running?

Not that I nave noticed particularly.
I've noted down the memory usage as it now, and ill check it a few times today to see and report back

Still crashing even with a full re-install from scratch. Not as often though 10/03/2012 06:11:55.000 kernel: PSYNCH: pid[52308]: cvwait: thread entry with same sequence already present Again this is in the OSX console.log at the time of the crash. Hope that makes some sense to you as it means nothin...

Fair enough. I would be surprised if I was the only one where the missing fields aren't being added though. It's impossible to know as it carries on working regardless Might be worth adding a version display in the config screen at some point, to see if amendments are actually taking.

Then if you are not overwriting the ini, how are people supposed to get the latest version of the ini file? You were surprised before that I didn't have the correct ini file, yet if you don't overwrite or amend an ini file that is already there, what else do you expect other than out of date ini fil...

Completely wiped sab and re-installed. After deleting the sab directory in app support and reinstalling, I now have the correct ini.
Might be worth mentioning in the install readme, as it obviously wasn't overwriting the ini file correctly in OSX

Lets see what happens overnight

I do use SSL for usenet, but normal http for the web interface

I use Sickbeard and couchpotato.

When I roll back to 0.6.14, I think I will do a full delete and re-setup from scratch. I assume all I need to do is delete the app and the sab folder in application support? Or is there anything more I need to delete?