In looking at my GO file, I now only have the following lines, which I think are put there by SF current version;

 

# Start the Management Utility

/usr/local/sbin/emhttp &

sed -i '/Scheduled Parity Check/d' /var/spool/cron/crontabs/root

sed -i '/cron=\"\"/d' /var/spool/cron/crontabs/root

 

Can you confirm these should be there?

 

The current version of SF - based on the new plugin system - does not write anything to the 'go' file anymore. Nor did the old version produce the entries above.

 

In short these entries are not coming from any SF version !

 

 

 

Ok, thank you very much!  They must be left over from my 4.7 build with unmenu.  Bottom line they are not needed, so I'll remove them.  I see one of them was for the monthly parity check, which SF does now, but I don't even know what the other two lines did.  Oh well.

At closer look I see these entries are to correct a bug existing in an earlier SF version. Ghost entries would appear in the crontab when no parity schedule was set.

 

You don't need these anymore, the particular bug has been corrected!

 

At closer look I see these entries are to correct a bug existing in an earlier SF version. Ghost entries would appear in the crontab when no parity schedule was set.

 

You don't need these anymore, the particular bug has been corrected!

 

 

Thanks again!  I've removed all that stuff, and I now have only this in my GO file (almost empty and the cleanest ever)

 

#!/bin/bash

# Start the new Samba

installpkg /boot/custom/samba-3.6.8-i486-1.txz

 

 

you should have left the emhttp line in there... now your webgui won't start, when you reboot your server

 

# Start the Management Utility
/usr/local/sbin/emhttp &

you should have left the emhttp line in there... now your webgui won't start, when you reboot your server

 

# Start the Management Utility
/usr/local/sbin/emhttp &

 

Yup, just found that out after rebooting.  I also can't get to any of my shares, which I don't understand.  I'll have to remove the flash drive and fix the GO file on my pc.

 

I understand the webgui, but any idea why the shares would not start?

that's all controlled by the webgui. without the webgui, your array won't start, so your shares are not available.

 

also looking at my go file, it could be, that after your manual install of the new samba version, it wasn't started.

i have these additional lines...

/etc/rc.d/rc.samba stop
installpkg /boot/packages/samba-3.6.8-i486-1.txz
/etc/rc.d/rc.samba start

Ok, thanks.  I manually started the webgui, all happy again.  I put back the start management utility line.

 

For samba, that is weird because when I check, I'm running the new version, so it must have started somehow.  Anyway, I'm no expect so I'm adding the Stop and STart lines to match yours. 

 

Here is what complete GO file now,

 

#!/bin/bash

# Start the Management Utility

/usr/local/sbin/emhttp &

# Start the new Samba

/etc/rc.d/rc.samba stop

installpkg /boot/custom/samba-3.6.8-i486-1.txz

/etc/rc.d/rc.samba start

 

Do you have anything else in yours?

 

Thanks!

Ok, thanks.  I manually started the webgui, all happy again.  I put back the start management utility line.

 

For samba, that is weird because when I check, I'm running the new version, so it must have started somehow.  Anyway, I'm no expect so I'm adding the Stop and STart lines to match yours. 

 

Thanks!

I wonder - if you installed the new samba before starting emhttp then maybe emhttp started it for you. If that is the case then maybe installing the new samba before emhttp is all that's needed and stopping samba before you install it then restarting it is unnecessary.

 

I have the same lines that Benni-chan has but it is after emhttp. I think emhttp must be starting the old samba and then it has to be stopped before you can install the new one and then you have to start it.

 

I don't want to reboot right now just to find out but if anyone else wants to try and report back that would be great.

Turns out I needed to reboot anyway today so I did try this and it worked. Here is what I think happens.

 

In your go script, if you install the samba update before you start emhttp then there is no need to stop samba so you can install it because it hasn't started yet, and no need to start samba because emhttp does it for you. This makes sense because samba can be enabled/disabled from the webGUI.

 

So, you can just do this:

# custom install of updated samba package
installpkg /boot/custom/samba-3.6.8-i486-1.txz

# Start the Management Utility
/usr/local/sbin/emhttp &

 

Hi, I'm having a problem with getting sleep to work. My machine sleeps and wakes properly if I sleep it manually from the web interface. I want unraid to go to sleep 30 min after the array has become inactive but it doesn't seem to ever happen. I can see that the sleep script is running from ps -A and the disks have all been spun down. Any ideas what could be wrong?

I'm sorry if this is a dumb question but I followed the instructions in the first post to install and it isn't working.

 

The syslog says for each plugin "bad download, deleting" presumably because the network interface has not come up yet.

 

How do I fix this?

Hi, I'm having a problem with getting sleep to work. My machine sleeps and wakes properly if I sleep it manually from the web interface. I want unraid to go to sleep 30 min after the array has become inactive but it doesn't seem to ever happen. I can see that the sleep script is running from ps -A and the disks have all been spun down. Any ideas what could be wrong?

The sleep plugin isn't working properly. It was reported many pages of posts ago, easy to overlook. I had to put the sleep script activation back in my go file for now.

The sleep plugin isn't working properly. It was reported many pages of posts ago, easy to overlook. I had to put the sleep script activation back in my go file for now.

 

I see, thanks I'll look into doing the same for the time being.

Hi, I'm having a problem with getting sleep to work. My machine sleeps and wakes properly if I sleep it manually from the web interface. I want unraid to go to sleep 30 min after the array has become inactive but it doesn't seem to ever happen. I can see that the sleep script is running from ps -A and the disks have all been spun down. Any ideas what could be wrong?

The sleep plugin isn't working properly. It was reported many pages of posts ago, easy to overlook. I had to put the sleep script activation back in my go file for now.

 

could you share your sleep script with us? Mine just wont work at all and I am to much noobie, to debug it on my own.

I would appriciate your help.

 

Cheers

I use the script contained in the plugin and configured it from the plugin screen. I just call it from the go file.

 

/usr/local/sbin/s3_sleep -a -m10 -t0 -eeth0 -h03 -p /usr/local/bin/postRun

I'm sorry if this is a dumb question but I followed the instructions in the first post to install and it isn't working.

 

The syslog says for each plugin "bad download, deleting" presumably because the network interface has not come up yet.

 

How do I fix this?

 

Hi - I am also getting this same issue 'bad download, deleting' on all plugins

 

Is there a fix for this? I'm running 5.0-rc8a

 

EDIT - Installed all manually and worked fine.

 

I will be fixing the email notifications script soon (sending ioctl 2285 issue) .

 

I'm really looking forward to this fix speeding_ant.  Will it start reporting the Parity Check status as well as UPS status when the power goes out?  Mine used to do this with the old unmenu setup, but now I only get the "unraid OK" emails.  I'm running my monthly parity check right now and the only way I know that is by going to the gui.  Again, looking forward to the new email notifications. 

 

 

Hi speeding ant - any update on when you will release the updated email notification package?

 

Checking if there has been any update. I only just realized my logs were filling with these errors. Simplefeatures has otherwise been terrific.

This is by far the best Control Screen Set-Up I have seen.

 

It has tools galore...

 

So far, my testing has been very rewarding.

 

Kudos...! 

I just installed the latest version of Simplefeatures, v1.05.  Is it normal for all of the drives LEDs to flash (at the same time) every few seconds.  The stock GUI did not exhibit this behavior.  It does not do it when the drives are spun down.  I can't tell if its actually reading the disk for data or just accessing the drive status, ie drive temp.  As the drives spin down after the timeout, I believe that it is just getting some data from the drive and not actually accessing data.  If it were accessing data on the drive, I believe the drive inactivity timeout would never occur and the drives would stay spun up.

 

Update:  I just rebooted my server and noticed the following behavior.  I get the LED activity when I have a web page open to the Simplefeatures GUI.  If I close the browser window the activity goes away.

Hi,

 

I just downloaded simplefeaturesplugins.zip and extracted the .plg files onto my flash drive in /boot/config/plugins. 

 

when I reboot the server and access via "tower/main" in firefox I get the standard webgui (I have tried refreshing, etc).

 

If I telnet in and run root@Tower:/boot/config/plugins# installplg simpleFeatures.core.webGUI-1.0.5-noarch-1.plg

 

I get this error:

 

installing plugin: simpleFeatures.core.webGUI-1.0.5-noarch-1

file /boot/config/plugins/simpleFeatures/simpleFeatures.core.webGUI-1.0.5-i486-                                                  1.tgz: downloading from http://unraid-simplefeatures.googlecode.com/files/simple                                                  Features.core.webGUI-1.0.5-i486-1.tgz ... wget: unable to resolve host address `                                                  unraid-simplefeatures.googlecode.com'

bad download, deleting

 

 

Can someone help me troubleshoot the error?  I read on the first post to "ensure server has internet connectivity"....not sure if this is the issue.

 

thanks for the help

 

chuga

Hi,

 

I'm setting up a temporary unRAID server with older hardware till i build a new one. I have the same issue as chuga (post above). When my unRAID server is booting i'll get a message "unable to resolve host address". When i copy and past the address "unraid-simplefeatures.googlecode.com" in my browser in finds the simple features site. Also when i do:

 

installplg simple-features.core.webGUI-1.0.5-noarch-1.plg

 

It installs fine. Anyone a idea what the problem might be?

 

 

Hi,

 

I'm setting up a temporary unRAID server with older hardware till i build a new one. I have the same issue as chuga (post above). When my unRAID server is booting i'll get a message "unable to resolve host address". When i copy and past the address "unraid-simplefeatures.googlecode.com" in my browser in finds the simple features site. Also when i do:

 

installplg simple-features.core.webGUI-1.0.5-noarch-1.plg

 

It installs fine. Anyone a idea what the problem might be?

 

Apparently, there is a race condition between when certain NIC's are completely initialized (and have Internet connectivity) and when the  install procedure (installpgk)  runs.  Someone did write a script to delay the start of installations until the NIC was ready. 

 

Hopefully when LimeTech releases version 5 with the package installer, this issue will have been addressed and resolved.

We made a workaround for the network "delay" in the next version of SF.

 

I agree that eventually the 'race' condition should be solved in unRAID itself, i.e. start plugin installation once the network is up and ready (and give an error message when it isn't).

 

Hi Frank1940 and Bonienl,

 

I was suspecting that this was might be the issue. Thank you for confirming!

 

@Bonienl don't want to hurry things but when can we expect this update of simple features? It's a bit unhandy to start everything manually. B.t.w. awesome plugin's you guys have (simple features fan).

 

Is there any information when the next release of unraid will be? I'm a bit behind from whats going on.

Aim is for somewhere next week to come with several updates.

 

Please be patient! Though we should have a good start of the new year

 

Thank you Bonienl.

 

I think that is very fast bonienl. Indeed a good start of the new year!