unraid ver 5, snap, sabnzbd persistent

[bender1]

Having an issue here.  I have the sab plugin and have the data dir pointing at a drive configured with snap (/mnt/disk/sda1/sabnzbd/data), install dir is there too.

 

I can see that the data directory has been created, but everytime I reboot the server I have to reconfigure sab.  what am I missing?

 

Sab tells me:

 

WARNING: Your data directory is not persistent and WILL NOT survive a reboot. Please locate Data Directory on disk for persistency

 

I'm using the latest version of the plugin from Influencer's Github

 

 

[marcusone]

My guess would be because some rebooted the drive might be assigned a different sdX.

 

Sent from my SGH-I727R using Tapatalk 2

[bender1]

It's been sda1 every time.  I removed my previous message about it working as it was just toying with me.  Still didnt hold the configuration, although, the message about

 

WARNING: Your data directory is not persistent and WILL NOT survive a reboot. Please locate Data Directory on disk for persistency

 

went away until I rebooted....back to square 1.

 

Now, when I check the box next to "data directory" and put the path in "/mnt/disk/SNAPSHARE/sabnzbd" and click apply, the check in the box disappears.

[bender1]

***UPDATE***

After installing the latest sickbeard plugin, rebooting the server causes the previous issue of the having to setup sab on reboot.  If I remove the sickbeard plugin, sab loads the correct config on reboot.  Found the issue, now how do I fix it? 

****************

 

***ORIGINAL POST***

this seems kind of silly, but I did finally get it working.  After deleting and reinstalling all my plugins numerous times, rebooting 100 times, etc....This is what worked for me, can't say why, but this is the order of things in case someone else wants to try it.

 

removed everything from /boot/config/plugins and rebooted

 

grabbed a fresh copy of the Snap .plg and dumped it in to the plugins directory

telnet in, ran installplg on the snap plugin

Installed and configured snap plugin (create share "SNAP") through webgui

reboot

 

edit go script and moved the line for snap above the line that starts with cd /boot/packages

reboot

 

grab a fresh copy of sabnzbd plugin from Influencer's github

https://github.com/Influencer/UNplugged

put plugin in /boot/config/plugins

telnet in and installplg

go in to /boot/config/plugins/sabnzbd and edit the .cfg file, change data dir to /mnt/disk/SNAP

use webgui to install sabnzbd, then enable

reboot

 

This worked for me, although, not sure why.  I had tried all of the steps above, but not in this exact order and with all of the reboots.  I'm sure there is a perfectly logical explanation, but Im a noob...

 

 

 

[Influencer]

The reason it probably worked that way is because sab was being installed before snap, and snap was being installed after the array had came online. What happens here is the sabnzbd plugin tells sab to start with a data directory of /mnt/disk/SNAP. Since snap has not started yet, the location does not exist. If this happens in a linux environment the location will be created, but it is created in RAM(just like the rest of unraid runs in ram, which is NOT persistent).

 

Once this happens, snap cannot mount the drive to that location since it is already in use and not empty. So sab has a fresh data directory with no files, so you were having to set the configuration up again.

 

Now that you moved the line that starts snap, snap is being installed and starting before sab is installed and started. See where I'm going with this?

 

Sorry I didn't catch this thread earlier, it probably would have saved a few steps. In the future if you have an issue relating to one of my plug-ins, please post in my support thread, I am notified immediately via e-mail when someone posts and I check it as soon as I can. This will ensure quicker support for you, and keep me updated with any possible issues!

[bender1]

Influencer, thank you for your input.  Makes total sense, and I had a feeling that's what was happening...

 

Everytime I try to install the sickbeard plugin, I have the issue of snap not mounting first, even though the go script hasnt changed.  Any suggestions?

 

BTW, I'd just like to personally thank you for these plugins, and your help.

[Influencer]

sickbeard may be installing before snap anyway. You can rename the plug-in to something like sickbeard_unplugged.plg.manual and add a line after the snap line in your go file to install it manually:

 

installplg /boot/config/plugins/sickbeard_unplugged.plg.manual

 

That will work until I can work something else out. I don't use snap so I'll have to try and source a drive to test with.

[bender1]

Ill try that and report back.  Should I delete this thread and create it in your support area?

[Influencer]

It's fine, just for future reference post in my thread so I can be notified and can help. I'm subscribed to this thread so If you post here ill be notified as well

[bender1]

will do, and thanks.  Below is my go file.  its ignoring those plugins on boot.  I've verified path and filenames but they aren't getting installed.  I don't see any mention of them in syslog.

 

 

#!/bin/bash

# Start the Management Utility

/usr/local/sbin/emhttp &

 

/boot/config/plugins/snap/snap.sh -b

 

installplg /boot/config/plugins/sabnzbd_unplugged.plg.manual

installplg /boot/config/plugins/sickbeard_unplugged.plg.manual

 

cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c

 

 

 

[Influencer]

You will probably have to declare the full path to installplg, it probably isn't in the env variables at the time the go file is executed.

 

I believe the path is /user/sbin/installplg but I'm not 100% on that, ill see if I can find it and post back.

[Influencer]

The full path will be

/usr/local/sbin/installplg

[bender1]

cool, I added a wait 30; and added those lines to the go script and it installs. 

 

However, when I go in to the webgui it shows sab and sb as not installed...I click install, then start it and it works (reading from old config).  A reboot reverts it back to not installed. 

 

I did edit the .plg to reflect the datadir as /mnt/disk/snap and set service="enable"

 

How can I go about making it install and start?

[bender1]

Any recommendations for me on this sir?

[Influencer]

I'll have to look at how I initiate the auto-start. It gets started when the disks_mounted event is fired. Installing the plug-ins this way the plug-ins are installed after the event, so they obviously never catch it.

 

Quick and dirty you can add these to the go file as well:

 

/etc/rc.d/rc.sabnzbd start
/etc/rc.d/rc.sickbeard start
/etc/rc,d/rc.couchpotato_v2 start

 

That will install/start the plug-ins

 

 

[bender1]

that worked.

 

so frustrating, now I get

 

WARNING: Your data directory is not persistent and WILL NOT survive a reboot. Please locate Data Directory on disk for persistency

 

again..

[bender1]

my go script...boot takes forever now, but I was trying to make sure that snap was done before loading plugins.  Still having the persistence issue.

 

#!/bin/bash

# Start the Management Utility

/usr/local/sbin/emhttp &

/boot/config/plugins/snap/snap.sh -b

sleep 60;

cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c

sleep 60;

/usr/local/sbin/installplg /boot/config/plugins/sickbeard.plg.manual

/usr/local/sbin/installplg /boot/config/plugins/sabnzbd.plg.manual

/usr/local/sbin/installplg /boot/config/plugins/couchpotato_v2.plg.manual

/etc/rc.d/rc.sabnzbd start

/etc/rc.d/rc.sickbeard start

/etc/rc.d/rc.couchpotato_v2  start

[Influencer]

Out of interest, post the output of

 

stat -f -c '%T' /mnt/SNAP/

 

Of course change /mnt/SNAP/ to the path to your data directory

[bender1]

it says ramfs

[Influencer]

Does SNAP report that the drive is mounted? I'm not sure how snap works exactly, but if that line reports ramfs then the mount point is in ram, not the disk

[bender1]

yeah, snap shows it mounted as reiserfs.  Snap is about to go out the window so to speak lol

 

 

[Influencer]

Does snap's log say anything about the drive being mounted? I'm not sure at all why Snap + Sab, Sickbeard & Couchpotato is giving such an issue. Sickbeard's code is almost identical to couchpotato, and really the only thing different from sab is how they are downloaded. This should in no way affect a drive being mounted.

 

The data directory is /mnt/disk/snap, which does exist and is mounted as reiserfs as far as snap is concerned, but stat returns its ramfs.

 

^^That statement sums it up, correct?

[bender1]

yep, sounds about right.

 

I'm going to get rid of snap and re-install/configure.  If it doesn't work...I'm on to the next option.  I started with unraid because I wanted something that just works...and it does.  If I have to goof it up with something like snap that seems to me to be unreliable, I'm taking two steps back.  Might just have to buy the license to get a cache drive. 

 

I really just wanted to see if this was going to work for me, and had planned on buying the license anyway once I was finished evaluating.

[Influencer]

Well for what its worth, I use Sab and Sickbeard, not couchpotato so much, and I never have to do anything to either. Sickbeard finds, Sab downloads, Sickbeard processes. I watch.

[bender1]

I think the issue could be this:

 

Plex gets installed, possibly before snap is done.  I have the library set to the snap drive, and if it isnt there I guess it just creates the directory in ram.  I think the simplest solution to all of this is the inclusion of a cache drive...that should end the tinkering, correct?