request

Get help, report and discuss bugs.
dude

Re: request

Post by dude » 16 Nov 2008, 21:12

Request sent
server returned: Scan-Command scheduled successfully

8-) 8-) 8-)

Thanks, works great!

Do need to give also the config file, of course no problem.

root@CH3SNAS:~# nzbget -S
No configuration-file found
Please put a configuration-file in one of the following locations:
~/.nzbget
/etc/nzbget.conf
/usr/etc/nzbget.conf
/usr/local/etc/nzbget.conf
/opt/etc/nzbget.conf
:shock:

root@CH3SNAS:~# nzbget -S -c /ffp/etc/nzbget.conf
Request sent
server returned: Scan-Command scheduled successfully

:mrgreen:

dude

Re: request

Post by dude » 16 Nov 2008, 21:16

Using: nzbget-0.6.0-testing-r252-bin-dns323-arm.tar.gz

:)

dude

Re: request

Post by dude » 16 Nov 2008, 21:22

I see, needs config to find daemon.
No problem.
Going to download a lot now to test stability. ;)

root@CH3SNAS:~# nzbget -S -c /ffp/etc/nzbget.conf
Unable to send request to nzbserver at 127.0.0.1 (port 6789)

dude

Re: request

Post by dude » 16 Nov 2008, 21:48

On thing though, when I issue the command "nzbget -S -c /ffp/etc/nzbget.conf" it picked up one nzb.
There where three nzb files in the folder waiting.

So I issued the scan command again and then it picked up the two other nzb's.

Maybe this has to do with the "NzbDirInterval=31536000" line in my nzbget.conf
I guess this is needless now and I can set it back to zero?
Or does the scan function not work with "NzbDirInterval=0" line?

I'll test with it more tomorrow, it's now doing some stability tests. ;)

hugbug
Developer & Admin
Posts: 7416
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: request

Post by hugbug » 16 Nov 2008, 23:01

Make sure files were old enough to be catched, check file timestamps and option "NzbDirFileAge".

dude

Re: request

Post by dude » 20 Nov 2008, 21:45

@hugbug, forum is back up so paste mail here, I know your checking on this.

Just did some extra testing because I think nzbget was not picking up (new) nzb's.
I changed the "NzbDirFileAge=60" in nzbget.conf to "20" and I think you are right, the scan function is working fine.

One thing I noticed is that when starting the daemon it sometimes picks up nzb's directly, and sometimes not.
It waits, in case not picking up directly, until "NzbDirInterval=60" time expires.
Because in my case this timer is set to "31536000" it waits for a long time. ;-)
(In fact it now starts when the Scan cron job kicks in.)

I use this "NzbDirInterval=31536000" trick value to pick up nzb's directly via stopping and starting the daemon by using the webinterface.
(Sometimes I don't want to wait for the Scan cron job.)
Maybe this can be fixed?
One "work-around" can be to make the Scan command available inside the webinterface?

To help you fix the problem I noticed in Top that, when starting the daemon, is see:

- 7x line: /ffp/bin/nzbget -D -c /ffp/etc/nzbget.conf (It picks up nzb's directly.)
- 5x line: /ffp/bin/nzbget -D -c /ffp/etc/nzbget.conf (It does NOT pick up nzb's directly.)

Tested with different values in "NzbDirInterval" and this doesn't change behaviour.

dude

Re: request

Post by dude » 26 Nov 2008, 21:56

After more testing it seems to be that the "NzbDirFileAge" value was my problem when starting the daemon and not picking up nzb's.
I changed the value to 10 sec. because, in my case, I mostly copy nzb's to nzbdir via Samba share.
This doesn't take much time.
Everything is working fine now. 8-)
Sorry for the mislead. :oops:

hugbug
Developer & Admin
Posts: 7416
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: request

Post by hugbug » 26 Nov 2008, 22:12

Not a problem, we have a cool new feature now. And we have even tested it ;)

Post Reply

Who is online

Users browsing this forum: No registered users and 10 guests