Whenever I restart machine with plugin installed in /usr, it downloads the plugin all over, and oftentimes, causes problems.  I tried to change it, this time, I want to have it installed in /mnt/cache/.apps/sabnzbd_install, but as soon as I press apply, unraid hangs.  It's no responds to ping, and ssh no longer works.  Web console no longer accessible.

 

What's the matter?

 

This is the last line that happens before putty session closes:

 

Tower sudo:    root : TTY=console ; PWD=/ ; USER=nobody ; COMMAND=/usr/bin/python -OO /usr/local/sabnzbd/SABnzbd.py -d -s 0.0.0.0:8081 --config-file /mnt/cache/.apps/sabnzbd_config --pidfile /var/run/sabnzbd/sabnzbd.pid

 

just tried the same thing to another directory, /mnt/disk1/.apps/sabnzbd_install, it hangs.

 

additional info:

 

when I start unraid with sabnzbd renamed to sabnzbd.plgx (just any random extension), unraid starts properly.  When I install it, and I use the same config directory /mnt/cache/.apps/sabnzbd_config, as soon as I start, it hangs.

 

How do I fix this without creating another configuration all over again?

 

Going back to /usr/local/sabnzbd install directory doesn't work anymore.  It still hangs. 

 

Hope I can just fix this.

Post a syslog

The question is,  if it hangs,  I can no longer access the syslog. When I restart,  do I get to copy the syslog before it hang? Or does it generate a new one?

Did you try the tail method for getting the syslog I posted on your other thread? Go read that sticky I mentioned there!

Did,  and it ended with the line I posted on my first post. That's the last line generated by unraid before it hangs. Then, it no longer responds to ping nor telnet.

BTW, I was able to copy that quickly.  The putty session closes automatically.

We need a complete syslog, not just the last line.

 

Are you sure you're not having a problem with your PC or possibly your network? The only time putty closes automatically is when I logoff. Disconnects or hangs just leave the window open.

 

Can you attach a monitor and keyboard to your unRAID system?

 

Boot in SAFE mode.

I booted it without plug-ins. It runs for a few minutes,  half an hour or so, in which time,  I can access console,  ping it even,  and see shared files. Then it will hang with the hard disk led on. Whenever it boots up,  it starts checking parity. I guess that's the reason hard disk led keeps on. I will connect monitor later. How do I generate complete syslog just before it hangs?

Any time you shutdown without stopping the array as you have had to do, it will always start a correcting parity check when it starts back up. This is by design because powering down without stopping the array could cause parity to not be updated properly.

 

Just get a syslog as soon as the shares become accessible and post it.

OK. I always use the power down button provided by unmenu,  unless the unit hangs. Which is what happens now. I will provide update later. Thanks

Then use the powerdown command at the command to stop the array safely or powerdown -r to reboot if you can't access unmenu or it hangs.

Hello megalodon,

 

The issue is I cannot even ping the IP.  So I have to physically press power button over 4 seconds to shut it down.

 

I don't know where to begin, why it hangs, with HDD led on, even when started without plugins.

You need to start it in safe mode with no plugins. If you are having problems with hanging in safe mode then you have a hardware problem. Run memtest to see if thats okay.

Just an update, I connected the box to a monitor and booted it without plugins.  It's been running for an hour so far.  Checking parity.  I'll see if I booted it up incorrectly with plug-ins before.  I'll update in a day or two.  Might be one of the plug-ins causing the problems. 

 

When I reinstall to plug-ins to a new data directory, still using the old config location, is there any reason this will cause unraid to hang?  Original location of plug-ins is /usr/local/...

As I said all my plugins are on my USB flash drive/card. I don't install them anywhere else. Are you saying you install them on a cache drive?. If so then you need help from another user. I know a lot of people install them on the cache drive because of the worry of wearing out the USB key but as I use a USB flash card I don't worry about a cache drive, its not going to make my system any faster as its just a media server and if the flash card fails I just pop in my spare and buy another without the worry of having to contact Tom for another license code for a new USB key.

Hello megalodon,

 

My reason for using cache drive is totally different.  But since it's there already, and since cache drive is out of the array, it should boot up pretty quickly, right? 

 

Originally, my plugins are installed on the /usr/local/....  Never did bother to check what happens since my config is saved in /mnt/cache/.apps/...

Last time, I connected it to a monitor, and notice that upon bootup, it downloads some files.  Don't know exactly what.  I thought it could be downloading a copy of sabnzbd, sickbeard, couchpotato, etc, which will be one of the reasons why it takes unraid so long to bring the array up. Which got me thinking, why not just save the apps to cache drive, on another folder.  Which started all these problems.  So when I tried configuring sab and installing it to /mnt/cache/.apps/sab_install, still using the config file under /mnt/cache/.apps/sabconfig folder, the system hang. 

 

Since we're on the topic, may I just ask whether plugins, when configured to install to /usr/local/..., does it download a fresh copy from online all the time?  Or does it get a copy from the flash drive?

 

I think I'm gonna need to create another topic :-(  another problem just popped up, mysql related.

 

 

/usr is in RAM so anything installed there will not survive a reboot.

 

In general, anything not in /boot or /mnt is in RAM.

Looks like trurl answered your question. I have never installed Apps to anything other than the USB Flash. If you install Apps to another location other than the Usb Key where should you place them trurl?

What does OP actually mean by install? I assume it has something to do with something on a particular plugins settings page, since the actual .plg file should be put in /boot/config/plugins.

 

What versions of what plugins are we talking about? Probably the answer to the question of where to "install" a plugin is in that plugins thread.

When installed in ram,  where does it get the plg file? From pre-downloaded location on disk? Or does it download a fresh copy every boot before load to ram?

BTW, I'm using PhAzE's plug-ins, sabnzbd, sickbeard, couchpotato.

Since I've started unraid on safe mode, nothing happened so far.  Perfectly working, no hanging. 

 

I could have thought I was running in safe mode earlier, but was actually running normal mode.  I chose safe mode by connecting a keyboard, and timing the time it boots up, and pressing the down arrow once, blindly

 

Which brings me to another question, any way of ensuring starting in safe mode without plugging unraid to a monitor?

 

Will focus on generating syslog tonight under normal mode startup.

 

Thanks

...Which brings me to another question, any way of ensuring starting in safe mode without plugging unraid to a monitor?...

You can edit syslinux.cfg using a linux compatible editor and move the "menu default" line under the "label" you want to be the default.

I'm back 

 

So, I restarted unraid with all plug-ins disabled.  Then, executed the following:

 

1. Went to plug-in directory, and did a "installplg sabnzbd.plg"

2. Made sure data directory is still /usr/local/sabnzbd, as from other comments, it's safe to install to memory, it gets plug-in from flash drive, and doesn't download a new copy all the time (won't take very long)

3. Made sure config directory is still /mnt/cache/.apps/sabnzbd_config (my original config directory while it was still working properly).

4. Started the plug-in, and got failed. 

5. Went into console, and did this /etc/rc.d/rc.sabnzbd start

6. Got the following output

 

root@Tower:/etc/rc.d# rc.sabnzbd start > sablog.txt

^C

root@Tower:/etc/rc.d# cat sablog.txt

Starting SABnzbd: sudo -u nobody python /usr/local/sabnzbd/SABnzbd.py -d -s 0.0.0.0:8081 --config-file /mnt/cache/.apps/sabnzbd_config --pidfile /var/run/sabnzbd/sabnzbd.pid

Error:

Can't write to logfile

PID not created, application did not start for some reason

root@Tower:/etc/rc.d#

 

7. Am attaching my syslog here

sabnzbd_error.txt