SABnzbd Forums

Hello,

My SABnzbd install does not queue and start downloads. The software is running and my usenet provider tests successfully. However, when I add an nzb (any nzb), I see a directory in the incomplete folder is created, but the download is not added to the queue. Logging is set to debug, but the only entry it shows is "Creating directories: /export/shared/incomplete/[nzbname]"

Please help!

Version 0.7.20
OS: SunOS 5.11 joyent_20141113T164921Z i86pc i386 i86pc Solaris
Install type: python source

Do you get any warnings?
Are you using a pre-queue script?
Check Config->Folders

No warnings. Logging is set to debug.
No pre-queue script.
In folders, temp download and complete download location are set, permissions for completed downloads set to 777 to be sure.

If you have debug logging on, inspect the log file just after an NZB failed to load.
Download the file from the Status page and start at the bottom.

NZBs are never added to the queue in the first place.

Steps:
1. I choose "choose file" from the Add section on the Home tab, select an NZB and click Add
2. In the log file, I see:
2014-11-29 09:46:44,496::INFO::[__init__:628] Adding [nzname].nzb
2014-11-29 09:46:44,498::INFO::[misc:811] Creating directories: /export/shared/incomplete/[nzbname]

That's it. The nzb is never added to the queue. The Queue tab is empty. No other entries in the log file, no errors. On the status page, there is nothing.

Did you really enable Debug logging?
There should be more information.

2014-11-28 20:59:17,475::INFO::[SABnzbd:1597] Starting SABnzbd.py-0.7.20
2014-11-28 20:59:17,475::DEBUG::[__init__:346] Starting postprocessor
2014-11-28 20:59:17,476::DEBUG::[__init__:349] Starting assembler
2014-11-28 20:59:17,476::DEBUG::[__init__:352] Starting downloader
2014-11-28 20:59:17,477::DEBUG::[scheduler:188] Starting scheduler
2014-11-28 20:59:17,478::DEBUG::[__init__:357] Starting dirscanner
2014-11-28 20:59:17,478::INFO::[dirscanner:277] Dirscanner starting up
2014-11-28 20:59:17,479::DEBUG::[__init__:364] Starting urlgrabber
2014-11-28 20:59:17,479::INFO::[urlgrabber:77] URLGrabber starting up
2014-11-28 23:37:00,077::INFO::[__init__:628] Adding QxZGzCx7gCzxQOd7ODGA.nzb
2014-11-28 23:37:00,079::INFO::[misc:811] Creating directories: /export/shared/incomplete/QxZGzCx7gCzxQOd7ODGA

And that's the last log entry..

Can you email one of the failing NZB files
to bugs@sabnzbd.org ?
(Please add the URL of this post.)

The NZB files are of course fine, since they load on your Mac.
I missed the part where you said that you run SABnzbd on SunOS.
Which version of Python are you using?
I assume you installed yEnc and Cheetah?
And use SABnzbd's own CherryPy?

Which SunOS is that, where did you get it?

This is SmartOS (smartos.org), a Solaris clone based on Illumos. It's a hypervisor offering zones (like Docker) and has KVM support. My SABnzbd install runs in a zone.

[root@sabnzbd ~/.sabnzbd/logs]# python --version
Python 2.7.8

[root@sabnzbd ~/.sabnzbd/logs]# cheetah --version
2.4.4

[root@sabnzbd ~/.sabnzbd/logs]# yencode --version
yencode - yencode 0.46

I didn't install cherrypy so assuming I am using the SABnzbd's own version.

n_goossens wrote: 2014-11-28 23:37:00,079::INFO::[misc:811] Creating directories: /export/shared/incomplete/QxZGzCx7gCzxQOd7ODGA

And that's the last log entry..

Is /export/shared/ NOT a local disk, but a network share or disk share in another zone/container?

And does that directory /export/shared/incomplete/QxZGzCx7gCzxQOd7ODGA then exist? Is it writable for the account under which sabnzbd is running?

And to see if SAB is hanging, you could change the sabnzbd/misc.py code from
to

Yes, it exists.

[root@sabnzbd /opt/local/sabnzbd]# ls /export/shared/incomplete/
QxZGzCx7gCzxQOd7ODGA

Misc.py code changed, logs now show:

2014-12-01 23:04:28,940::INFO::[__init__:628] Adding QxZGzCx7gCzxQOd7ODGA.nzb
2014-12-01 23:04:28,942::INFO::[misc:811] Creating directories: /export/shared/incomplete/QxZGzCx7gCzxQOd7ODGA
2014-12-01 23:04:28,942::INFO::[misc:815] Creating directories .... done!: /export/shared/incomplete/QxZGzCx7gCzxQOd7ODGA

And yes, /export/shared is a ZFS disk pool named download (one disk) that is shared from the host to the zone.

n_goossens wrote:And yes, /export/shared is a ZFS disk pool named download (one disk) that is shared from the host to the zone.

Can you try to use the standard /home/<user>/ and the standard, relative paths for the Download dir etc, so more "local" disks?

Sadly, that does not make a difference. The behavior is the same: incomplete folder is created, that's it.