Sabnzbd+ randomly quitting on OSX

[trooper]

No worries, unless you can reproduce it, there isn't a huge amount we can do, other than keep trying random things. Especially as there are no entries in any logs.

[trooper]

It just crashed within the last half hour, the only thing in the console.log for osx that looks out of place is the following

Code: Select all

02/03/2012 20:37:52.000 kernel: PSYNCH: pid[277]: cvwait: thread entry with same sequence already present

The pid looks to be the right sort of number for sab in my loadup sequence looking at the other apps around it (I rebooted last night, sab is set to load on startup, and this is the first crash since then)
I've noted down the pid of the current sab instance and when it next crashes i'll look for that and see what I can find in the console.log then.

[trooper]

Well, this is new!

Using 0.6.15 the last two nights it has just hung rather than crashed. Same result though, no errors in the log, not even that line in the console.log.
Had to force quit to get it to restart.

If the same happens tonight i'll go back to 0.6.14 and make sure it only happens on the latest version

[shypike]

Meanwhile, 0.6.15 has been downloading for 36 hours at 600Kbytes/sec
without issues on my miniMac.
Do you use any other software or browser add-ons that interface with SABnzbd?
I would be most interested in your results with 0.6.14

[trooper]

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?

[shypike]

Changing two things at the same time makes it harder to find the cause.
Consider running 0.6.15 first with cleaned data.
You can erase everything in ~/Library/Application Support/SABnzbd
except for the sabnzbd.ini file
That should be enough.
If you want to clean the INI file too, consider copying the [server] and [rss] sections
into a fresh INI file.

[shypike]

Another thing.
Do you use HTTPS for the web interface or ssl for the Usenet servers?

[trooper]

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

[trooper]

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

[shypike]

as it obviously wasn't overwriting the ini file correctly in OSX

It's not supposed to overwrite the existing files in ~/Library/AS/SABnzbd.
How else would you have a non-destructive upgrade?
It's not the OSX way to overwrite settings anyway.
Also, we always recommend cleaning ~/Library/AS/SABnzbd instead of re-installing the app
if things don't work as they should.

[trooper]

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 files?

[shypike]

Missing fields are automatically added and besides that, each value has a default.
I have done this for years, I must have "upgraded" my original INI file dozens of times.
That your file missed a field may be a symptom of some other problem,
but not a sign that you need a fresh INI file every time.

[trooper]

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.

[shypike]

We only increase the INI version number if the file has become incompatible
with the previous version. Meaning that you can no longer downgrade.
We try to keep those moments as minimal as possible.

[trooper]

Still crashing even with a full re-install from scratch. Not as often though

Code: Select all

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 nothing to me!