Page 1 of 1

Empty Queue After Reboot

Posted: January 5th, 2020, 7:51 pm
by callumro
Hey guys!

Appreciate the support in advanced.

Some background, im running a RPi 4 on Raspbian and using Sonarr to push downloads to SABnzbd.

Everything is working once up and running but after any reboot, my queue and history are cleared. I can run a queue repair after the service is started again ideally I would like the application to be able to survive a system reboot without the need for manually logging into the webui and running the queue repair.

Here are the recent logs (with debug on) after a reboot:
pastebin . com/QSBEne3f

My google fu makes me think that this is a permissions issue but all folders in this directory are 777 and owned by the pi user.

Code: Select all

drwxrwxrwx 1 pi pi  4096 Jan  5 14:32 Completed
drwxrwxrwx 1 pi pi 16384 Jan  5 15:50 Downloading
drwxrwxrwx 1 pi pi     0 Jan  3 18:23 Scripts
drwxrwxrwx 1 pi pi  4096 Jan  3 19:05 Watch
Any thoughts here? The primary error I am seeing is this:

Code: Select all

2020-01-05 15:44:56,795::INFO::[misc:519] download_dir directory: /media/usb1/Usenet/Downloading does not exist, try to create it
2020-01-05 15:44:56,796::ERROR::[misc:521] Cannot create directory /media/usb1/Usenet/Downloading

Re: Empty Queue After Reboot

Posted: January 6th, 2020, 1:12 am
by sander
USB / power or timing problems.
After booting your Raspi, and waiting 5 minutes, can you start SAB safely?

Re: Empty Queue After Reboot

Posted: January 6th, 2020, 11:00 pm
by callumro
Yeah appears to run fine when I start the service manually or after I restart the service once the Pi is already online.

Any recommendations on how to delay-start a service on a Pi?

Re: Empty Queue After Reboot

Posted: January 7th, 2020, 12:45 am
by callumro
I found this thread which sounded similar to my issue but my NTFS drive is already mounting through fstab which was the solution resolved Xeijin's issue.

viewtopic.php?t=4888

/etc/fstab

Code: Select all

proc            /proc           proc    defaults          0       0
PARTUUID=6c586e13-01  /boot           vfat    defaults          0       2
PARTUUID=6c586e13-02  /               ext4    defaults,noatime  0       1
UUID=26860F7E860F4DAD /media/usb1 auto nofail,uid=1000,gid=1000,noatime 0 0
# a swapfile is not a swap partition, no line here
#   use  dphys-swapfile swap[on|off]  for that

Re: Empty Queue After Reboot

Posted: January 9th, 2020, 2:46 am
by callumro
Seems that this setting under special was what i was looking for:
wait_for_dfolder
"Some people use external or network drives for the "temporary download folder". It can happen that such a drive isn't mounted yet when SABnzbd starts up, causing it to create a new folder at the default location. To prevent this, set the option to 1. This will make SABnzbd wait until the drive is available. Note that SABnzbd will hang until the drive is available! Also, the folder must already exist otherwise SABnzbd will hang until terminated."

Now I get about a dozen errors like this one after a reboot. Any thoughts on what this means and if they can be safely ignored?
Error importing <NzbFile: filename=8e9ff206e519411ba97f5c8b1ab324a3.part19.rar, type=None>

Re: Empty Queue After Reboot

Posted: January 9th, 2020, 10:14 pm
by callumro
The importing error has not resurfaced after the first reboot. This is resolved!