Restart required to pick up nzb files in watched folder?

[probedb]

Hi all,

I seem to have had a problem with sab for a while now, whereby the only way it will pick up new nzb files in my watched folder is to restart it.

Any ideas why this might be? I just updated to 0.7.11 and it still has the same problem, even when reinstalling and starting it doesn't pick the files up. Only a forced restart will do it.

System is WIn 7 64 bit.

Cheers,
Paul.

[shypike]

What's you scan interval?
Did you schedule a watched folder event?

[probedb]

What's you scan interval?
Did you schedule a watched folder event?

It's the standard 5s.

I didn't realise I had to, I thought it did it automatically? It always used to.

[ledgetheorc]

Same exact question, actually. Doesn't having to make a schedule for it make the interval irrelevant? I've got the folder and interval set as well, oddly enough just as I was typing this I JUST saw it finally pick up a NZB I downloaded 30 minutes ago, and I have it set to five seconds, I've still got another NZB in the folder it hasn't seemed to pick up yet. Any suggestions on how to make this more instant, or near instant would be awesome! Sorry don't mean to piggy back though I feel the two correlate.

[probedb]

No problem, it's the same issue. It used to work. It may have been the update to 0.7 that did it for me but I went through a period of not using Usenet.

[shypike]

The scheduled event will stop the automatic scan.
So you need to choose between that and the interval.

The watched folder works like it always did.
The last change to it was many versions ago.

[probedb]

The scheduled event will stop the automatic scan.
So you need to choose between that and the interval.

The watched folder works like it always did.
The last change to it was many versions ago.

So as per my original question why isn't it working for me then? I have no scheduled event for it, just the default 5s scan yet it doesn't work.

Is there any logging I can turn on and post here to help debugging?

[shypike]

Which folder are you using exactly?

[probedb]

Which folder are you using exactly?

I'm not sure what you mean?

It's the folder I drop nzb files in, which is specified with a full path including drive letter. It's correct as it picks the files up on a restart, just never again from that point on. It's like it's not doing the check every 5s as it should.

As I say is there any logging I can turn on to see what it's doing? I'm happy to debug.

[shypike]

Do you have anything in Config->Scheduler?
I asked for the full path, exactly specified, just in case there's some special situation where SABnzbd might falter.
So far I simply cannot reproduce your issue on any of my Windows systems.
There is no logging of access to the watched folder.
However, there is a diagnostic tool in Microsoft's SysInternals kit that will log access attempts to folders and files.

[probedb]

Well it would seem I'm not alone from the other poster.

The folder path couldn't be any simpler Q:\nzbs

As I previously said there is nothing in the scheduler other than Pause and Resume.

As I say this used to work.

[shypike]

So it's an external drive or a network drive?
You're sure it's always connected?
You say "it used to work". With the same SABnzbd version?
Is there a version that still works OK for this issue?

[probedb]

So it's an external drive or a network drive?
You're sure it's always connected?
You say "it used to work". With the same SABnzbd version?
Is there a version that still works OK for this issue?

It's an internal drive so it's always on. It also picks them up on a restart of Sabnzbd.

Unfortunately I can't remember I used to use it a lot more than I do now so I cant remember. Even with a clean install on a fresh Windows 7 build it does it.

I guess I'll have to live with it.

[shypike]

Does the function "Scan watched folder" work?
(Located in the dropdown menu under the yellow arrow at the top right of the queue.)