SABnzbd Forums

When I click on the pause button, the downloads pause for a short period of time (5 to 10 seconds) then go back to normal.

There is a countdown and the pause button is red, but it is still connected and downloading. I checked with Ubuntu System Monitor.
The only way I can disconnect Sabnzbd from the server is by disabling the server I'm using.

SABnzbd Version: 0.6.15

Sounds like a browser issue, which one do you use?

I can reproduce that with the current versions of Chrome, Firefox and Konqueror.

Then it's likely that your disk is full.
Do you see any warnings displayed?

Here is the trace after I click on pause:


2012-05-01 19:39:28,921::INFO::[downloader:194] Resuming
2012-05-01 19:39:28,922::INFO::[downloader:203] Pausing
2012-05-01 19:39:28,922::INFO::[nzbqueue:170] Saving queue
2012-05-01 19:39:28,924::INFO::[downloader:610] Thread 4@[news.server.com]:563: forcing disconnect
2012-05-01 19:39:34,416::INFO::[__init__:846] Saving data for queue9.sab in /home/ant/.sabnzbd/admin/queue9.sab
2012-05-01 19:39:34,417::INFO::[__init__:846] Saving data for totals9.sab in /home/ant/.sabnzbd/admin/totals9.sab
2012-05-01 19:39:34,417::INFO::[__init__:846] Saving data for rss_data.sab in /home/ant/.sabnzbd/admin/rss_data.sab
2012-05-01 19:39:34,417::INFO::[__init__:846] Saving data for bookmarks.sab in /home/ant/.sabnzbd/admin/bookmarks.sab
2012-05-01 19:39:34,450::INFO::[__init__:846] Saving data for watched_data.sab in /home/ant/.sabnzbd/admin/watched_data.sab
2012-05-01 19:39:34,450::INFO::[postproc:83] Saving postproc queue
2012-05-01 19:39:34,450::INFO::[__init__:846] Saving data for postproc1.sab in /home/ant/.sabnzbd/admin/postproc1.sab
2012-05-01 19:39:34,552::INFO::[downloader:610] Thread 3@[news.server.com]:563: forcing disconnect
2012-05-01 19:39:34,653::INFO::[downloader:610] Thread 1@[news.server.com]:563: forcing disconnect
2012-05-01 19:39:34,754::INFO::[downloader:610] Thread 2@[news.server.com]:563: forcing disconnect
2012-05-01 19:39:40,861::INFO::[downloader:351] 4@[news.server.com]:563: Initiating connection
2012-05-01 19:39:40,862::INFO::[downloader:351] 3@[news.server.com]:563: Initiating connection
2012-05-01 19:39:40,862::INFO::[downloader:351] 1@[news.server.com]:563: Initiating connection
2012-05-01 19:39:40,863::INFO::[downloader:351] 2@[news.server.com]:563: Initiating connection
2012-05-01 19:39:41,962::INFO::[downloader:539] Connecting 4@[news.server.com]:563 finished
2012-05-01 19:39:41,969::INFO::[downloader:539] Connecting 3@[news.server.com]:563 finished
2012-05-01 19:39:41,987::INFO::[downloader:539] Connecting 1@[news.server.com]:563 finished
2012-05-01 19:39:41,994::INFO::[downloader:539] Connecting 2@[news.server.com]:563 finished


None of my disks are full, even if the remaining space is smaller than the queue total size.

Can you set logging to "Debug" level (Status page)?

I have found the origin of the problem.
I use the priorities to sort my groups of files. Some of them were in "Force" priority.
The "force" (at least in french, I suppose this translates to force in the english version) priority prevents Sabnzbd from staying in the paused state.
You should remind to the user when he tries to enter the paused state, that at least one element of the queue is in this forced state.

Have been interpreting your message wrong all the time as "doesn't download from more than 5 sec." Duh.
Still, this is behaviour as designed.
Force is called force for a reason.
"You should warn" is a nice idea until you actually want to implement it and
put it in a useful place.

OK. That makes sense now.
"Force is called force for a reason."

OK I have found the paragraph describing the feature (no need to tell that users don't read the doc..)
Forced items will go straight to the top of the queue, and will continue to download even if the queue is paused.

I think that users will intuitively interpret this feature as "put this item to the top", but rarely as "continue to download even if the queue is paused". (at least I did)

SABnzbd is too many options and has too many historical compatibility things
to ever make it a truly intuitive app.
I can understand the confusion, but where would we put info in the UI so that people see it?
UI design is hard and we're not particularly good at it.