SABnzbd Forums

Windows 7 SP1 x64
I did not find any obvious cause (what causes the reset), but it happens every now and then - and it is becoming very annoying.

Only the categories, nothing else?
Any info about circumstances?
I have never seen it happen despite all my mistreatment of SABnzbd.

Yes, only the catergories (well, I do not use anything else).
The only thing I do is add new nzb files and change the category after adding them.
Might be related to shutdown though.
Thank you for checking.

It is important to shutdown SABnzbd properly, although I've yet to see it
being damaged by a improper shutdown.
Do you use any third-party utilities that support SABnzbd?

I expect a proper shutdown when I shut windows down - am I supposed to shut it down manually, beforehand?
No, I do not use third party tools.

The problem is that Windows is much to impatient.
When exiting, SABnzbd will try to dump its article cache to disk, which takes time.
Which it doesn't necessarily get from Windows.
This is only an issue during active download.
When SABnzbd is passive, it shouldn't be a problem.

Moreover, the state of the sabnzbd.ini file should not be an issue at all, because
it's only saved at the moment you change something in the configuration.
It's never saved on exit.
The short of it: I don't know how this happens, but I would strongly suspect an outside influence.
Maybe a debug log of SABnzbd, saved just after the last time it lost its categories, can be helpful.
But then you would have run in debug-log mode (Status page) all the time and check the config each time you start.

shypike wrote:When exiting, SABnzbd will try to dump its article cache to disk, which takes time.

I have an SSD drive, so that should not be an issue. Sab gets a shutdown signal from Windows like any other app and then it has 10-20 secs or so.

shypike wrote:But then you would have run in debug-log mode (Status page) all the time and check the config each time you start.

Yes, this is the tough part. Catching sab in the act.

It's not likely to be the shutdown.
The INI file isn't touched at shutdown time.
As for the other side-effects, 0.6.9 is quite robust regarding unpleasant stops.

I can tell it never stops other than shutdown (starts with the PC and shuts down with it).

I cannot think of any scenario that would damage (especially selectively) the INI file.
Without a specific scenario, I don't have a clue what to look for.

I managed to catch Sab in the act.
The assigned priorities revert to 'Default', too, not only the categories.
I emailed you the log file, hope it helps.
Thank you.