Windows 7 x64 SP1
0.6.0 RC2
Sab is running automatically.
I queue up a bunch of downloads, and I assign a category to each (and processing manually due to this bug).
Then, it seems when I do a normal restart or a shutdown/startup cycle, the settings get lost somewhere along the way, and all of the queued downloads's categories, priorities and processing are reset to the Default the next system startup - except the first (the active download).
Thank you for fixing.
0.6.0 RC2 Category, priority and processing reset on restart/shutdown/startup
Forum rules
Help us help you:
Help us help you:
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
-
looseruser
- Newbie
- Posts: 41
- Joined: April 12th, 2010, 12:17 pm
0.6.0 RC2 Category, priority and processing reset on restart/shutdown/startup
Last edited by looseruser on April 29th, 2011, 7:05 am, edited 1 time in total.
Re: 0.6.0 RC2 Category, priority and processing reset on restart/shutdown/startup
Do you have a specific scenario that causes this?
I stop and start SABnzbd all the time during development
and I have never seen this happen.
I stop and start SABnzbd all the time during development
and I have never seen this happen.
-
looseruser
- Newbie
- Posts: 41
- Joined: April 12th, 2010, 12:17 pm
Re: 0.6.0 RC2 Category, priority and processing reset on restart/shutdown/startup
This is not sab start/stop, this is system start/stop.
No, I did not do any customization other than the one category that I added (see the linked thread with the bug), so I cannot think of any reason why it behaves like this.
But, I wonder if the problem is that sab is trying to save during the system shutdown, wipes the old data but does not have enough time to write the old data out...
Update:
I quickly shut down sab (not the system) and restarted it. It seems to be ok.
So, it implies at system shutdown/startup only.
Update 2:
I wanted to create a screenshot about the result, but it seems that after performing the step above (manually stop and start sab without a system restart) everything seems normal.
I suppose the previous step allowed sab to save things properly.
So, to be more precise about the problem, the error seems to occur when:
- you queue a number of downloads
- change the categories (and the processing settings) to something else than the default
- you do a system restart or shutdown (without stopping sab manually)
Gotta rush to work, will test his in the afternoon.
No, I did not do any customization other than the one category that I added (see the linked thread with the bug), so I cannot think of any reason why it behaves like this.
But, I wonder if the problem is that sab is trying to save during the system shutdown, wipes the old data but does not have enough time to write the old data out...
Update:
I quickly shut down sab (not the system) and restarted it. It seems to be ok.
So, it implies at system shutdown/startup only.
Update 2:
I wanted to create a screenshot about the result, but it seems that after performing the step above (manually stop and start sab without a system restart) everything seems normal.
I suppose the previous step allowed sab to save things properly.
So, to be more precise about the problem, the error seems to occur when:
- you queue a number of downloads
- change the categories (and the processing settings) to something else than the default
- you do a system restart or shutdown (without stopping sab manually)
Gotta rush to work, will test his in the afternoon.
Last edited by looseruser on April 29th, 2011, 7:18 am, edited 1 time in total.
Re: 0.6.0 RC2 Category, priority and processing reset on restart/shutdown/startup
The most likely cause for problems is that
the operating system is not giving SABnzbd enough time to save all its data to disk.
This can lead to all sorts of queue corruption issues.
Should you run it as a Windows Service, this is much less likely.
(See: http://wiki.sabnzbd.org/sabnzbd-as-a-windows-service )
the operating system is not giving SABnzbd enough time to save all its data to disk.
This can lead to all sorts of queue corruption issues.
Should you run it as a Windows Service, this is much less likely.
(See: http://wiki.sabnzbd.org/sabnzbd-as-a-windows-service )