0.4.0RC2 has the issue that when you download NZBs into the watch folder that has been set while the daemon isn't running, the NZBs will be deleted when Sabnzbd+ starts, however, they aren't added to the queue.
Upgrading to RC4 now to see if it's resolved in that version, however, I've been having this issue since 0.3.4, so probably not.
Edit: RC4 still has this problem.
NZB watch folder not properly handled on start
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- 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.
NZB watch folder not properly handled on start
Last edited by Leftblank on June 19th, 2008, 7:40 am, edited 1 time in total.
Re: NZB watch folder not properly handled on start
Have you any data to illustrate this, like a logfile ?
I have never seen this happen.
I have never seen this happen.
Last edited by shypike on June 19th, 2008, 9:25 am, edited 1 time in total.
Re: NZB watch folder not properly handled on start
Do you use nzbstatus extension with firefox ?
If yes your problem is that your nzbtatus is configured to send downloaded nzb to sabnzbd daemon... but without checking if it's running or not...
Hope it helps...
If yes your problem is that your nzbtatus is configured to send downloaded nzb to sabnzbd daemon... but without checking if it's running or not...
Hope it helps...
Re: NZB watch folder not properly handled on start
Thanks a lot, I assumed that option was only relevant when 'Open' would be used, but this explains the trouble indeed. Sorry for the confusionrAf wrote: Do you use nzbstatus extension with firefox ?
If yes your problem is that your nzbtatus is configured to send downloaded nzb to sabnzbd daemon... but without checking if it's running or not...
Hope it helps...
