I was using SAB 0.4.x for a very long time.
It was running on a small Linux server (Synology NAS) without any problem.
I have configured the watched folder to a RAM drive / no RSS.
When SABnzbd became idle, my hard drives correctly enter power save mode after a while.
I recently tested 0.5.0 beta 1 (working very well)
Configuration was exactly the same. But my hard drives never enter power save mode.
I guess there is some hard disk access. But I'm able to locate the feature causing this.
I checked the logs, nothing after SAB has entered idle state.
I checked also starting SAB with empty queue: same thing, no power save.
Do you have any hints about it ?
Thanks.
[FIXED] Power saving issue with 0.5.0 beta 1
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.
[FIXED] Power saving issue with 0.5.0 beta 1
Last edited by elmer91 on December 8th, 2009, 11:17 am, edited 1 time in total.
Re: Power saving issue with 0.5.0 beta 1
First make sure logging is set to the lowest level.
Further we have now a scheduled "pause-all" which should
prevent all disk access.
We're not aware of any disk access, but it's hard to tell for sure.
(One problem is that we use quite a number of third-party modules
which lead their own internal lives).
Further we have now a scheduled "pause-all" which should
prevent all disk access.
We're not aware of any disk access, but it's hard to tell for sure.
(One problem is that we use quite a number of third-party modules
which lead their own internal lives).
Re: Power saving issue with 0.5.0 beta 1
Thanks for your answer,
I have already checked logs.
Nothing is logged after SAB has finished downloading.
Logging is set to "Errors/warnings"
I will try to find a Linux tool able to monitor hard disk /file acces.
I will report any progress in this direction.
Thanks for your help.
I have already checked logs.
Nothing is logged after SAB has finished downloading.
Logging is set to "Errors/warnings"
I will try to find a Linux tool able to monitor hard disk /file acces.
I will report any progress in this direction.
Thanks for your help.
Re: Power saving issue with 0.5.0 beta 1
I have found (at least) one thing:
RSS module is saving its state periodically.
In my config file, RSS checks is set to 15 mn
I have no RSS feed set.
In 0.4.x series, no problem.
In 0.5.0 beta 1, RSS module is saving its state.
I enabled debug logs, following lines appear every 15mn:
2009-12-07 15:48:21,428::INFO::[__init__:635] Saving data for rss_data.sab in /volume1/download/news/cache/rss_data.sab
2009-12-07 16:03:21,498::INFO::[__init__:635] Saving data for rss_data.sab in /volume1/download/news/cache/rss_data.sab
Setting RSS checking interval to a huge value can do the trick.
(may be 0, i have to check the source)
Would it be possible not to write rss_data.sab when there is nothing to write ?
RSS module is saving its state periodically.
In my config file, RSS checks is set to 15 mn
I have no RSS feed set.
In 0.4.x series, no problem.
In 0.5.0 beta 1, RSS module is saving its state.
I enabled debug logs, following lines appear every 15mn:
2009-12-07 15:48:21,428::INFO::[__init__:635] Saving data for rss_data.sab in /volume1/download/news/cache/rss_data.sab
2009-12-07 16:03:21,498::INFO::[__init__:635] Saving data for rss_data.sab in /volume1/download/news/cache/rss_data.sab
Setting RSS checking interval to a huge value can do the trick.
(may be 0, i have to check the source)
Would it be possible not to write rss_data.sab when there is nothing to write ?
Re: Power saving issue with 0.5.0 beta 1
Thanks for doing the hard work for this problem.
I'll fix this for the next Beta.
I'll fix this for the next Beta.
Re: Power saving issue with 0.5.0 beta 1
rss.py line 365:
if type(feeds) != type({}):
self.save()
Works !
if type(feeds) != type({}):
self.save()
Works !
Re: Power saving issue with 0.5.0 beta 1
It's a little more complex than that.
You want to save when any feed definition is active,
because you can have inactive ones too.
But it's no big deal, will make it to Beta2.
You want to save when any feed definition is active,
because you can have inactive ones too.
But it's no big deal, will make it to Beta2.