"SimpleFeatures" Plugin - Version 1.0.11



2848 posts in this topic Last Reply

Recommended Posts

After reading the startpost, i understand the current plugin folder (boot/config/plugin) should be removed, but what happens to my plugins like sickbeard and sabnzbd and slimserver? Do i have to re-install those? Because they are also in the 'old' plugin folder location...

Read again, you need to delete the simpleFeatures folder NOT the complete plugins folder...

Ok, so after installing there will be 2 plugin folders, one for sf, and one for eeh... plugins :o

 

As explained in the OP, the new SF version is installed in /boot/plugins.

 

User plugins reside in /boot/config/plugins

 

 

Link to post
  • Replies 2.8k
  • Created
  • Last Reply

Top Posters In This Topic

Thats what i say, now there are 2 plugin folders. A bit counterintuitive dont you think? This is a very error prone construction. Less experienced people will place the 'custom' plugins in the first one they encounter, which is the wrong one... resulting in frustration, questions here in this topic etc. i would suggest to just use ONE plugin location. Not two.

Link to post

Thats what i say, now there are 2 plugin folders. A bit counterintuitive dont you think? This is a very error prone construction. Less experienced people will place the 'custom' plugins in the first one they encounter, which is the wrong one... resulting in frustration, questions here in this topic etc. i would suggest to just use ONE plugin location. Not two.

I suggest you go  a few pages back in this topic and read about the whole reasoning behind this setup...

Link to post

Just an idea, to help with organizing these really long but important threads...

* Plugin tutorials thread - http://lime-technology.com/forum/index.php?topic=26015

The tutorials thread isn't accessible for me with the meassage shown on the screenshot. Any idea?

 

It *was* there!  There was a nice Preclear tutorial there.  Apparently it has gone back to the drawing board!

 

This becomes a nice example of my idea!  When the tutorials are ready again, the TOC/Links table can be updated to point to the new location.

I removed it because the thread became locked. Will add a new topic about preclear, which can follow your suggestion.

 

I'd set it up in the wiki  :)

Link to post

Thats what i say, now there are 2 plugin folders. A bit counterintuitive dont you think? This is a very error prone construction. Less experienced people will place the 'custom' plugins in the first one they encounter, which is the wrong one... resulting in frustration, questions here in this topic etc. i would suggest to just use ONE plugin location. Not two.

I suggest you go  a few pages back in this topic and read about the whole reasoning behind this setup...

There is no way keeping up with this topic, or others for that matter. Got a link?

Link to post

Just an idea, to help with organizing these really long but important threads...

* Plugin tutorials thread - http://lime-technology.com/forum/index.php?topic=26015

The tutorials thread isn't accessible for me with the meassage shown on the screenshot. Any idea?

 

It *was* there!  There was a nice Preclear tutorial there.  Apparently it has gone back to the drawing board!

 

This becomes a nice example of my idea!  When the tutorials are ready again, the TOC/Links table can be updated to point to the new location.

I removed it because the thread became locked. Will add a new topic about preclear, which can follow your suggestion.

 

I'd set it up in the wiki  :)

Just added the link to the wiki...

Link to post

I just realized that I had posted this in the RC11 thread when it should have gone here....

 

For temps, just tried switching to F and I now get a reading for both mb and cpu.  Says 32F for both, which is of course incorrect.

 

Output of sensors -u

root@Tower:~# sensors -u

coretemp-isa-0000

Adapter: ISA adapter

Core 0:

  temp2_input: 55.000

  temp2_max: 86.000

  temp2_crit: 100.000

  temp2_crit_alarm: 0.000

Core 1:

  temp3_input: 58.000

  temp3_max: 86.000

  temp3_crit: 100.000

  temp3_crit_alarm: 0.000

 

 

Link to post

I'm having the same issues w/ the webGUI that others have reported, after ug'ing to 1.0.11 on RC11.  The most recent event happend after pre-clearing a disk to try to bring into the array.    After the pre-clear completed and I returned to the main screen, the webGUI appeared to hang.  Closing the IE window and attempting to re-open finds that I cannot access the webGUI any longer.

 

All other types of existing connections remain able to access the system - this includes mapped drives, plex, plex web thru port 32400, transmission GUI, etc.  It's only the main web access that I cannot achieve any longer w/o a reboot.

 

It's not a memory issue - I have top running and have more than 2G free as I type.

 

Thanks for a great plug-in !  Hopefully these types of things will get resolved soon.

Regards,

-Jim

Link to post

...It's not a memory issue - I have top running and have more than 2G free as I type...

That by itself is not evidence that emhttp did not get oom-killed

You didn't post a syslog so not much to go on, but if you did preclear with defaults on a large drive it is possible it used enough memory to get emhttp killed. Happened to me and several others.

Link to post

Thats what i say, now there are 2 plugin folders. A bit counterintuitive dont you think? This is a very error prone construction. Less experienced people will place the 'custom' plugins in the first one they encounter, which is the wrong one... resulting in frustration, questions here in this topic etc. i would suggest to just use ONE plugin location. Not two.

I suggest you go  a few pages back in this topic and read about the whole reasoning behind this setup...

There is no way keeping up with this topic, or others for that matter. Got a link?

 

somewhere/sometime in the past there was a post stating that /boot/config/plugins after 5.0 final was going away - standard location will be /boot/plugins for future releases....

 

Myk

 

Link to post

Thanks trurl - I could see emhttp running, so it was still in the process list  (will post syslog details in the future).  The drive I was pre-clearing was "only" 160GB and I have 4GB of mem on the machine, so I'm hoping it wasn't that.

 

Anyway - rebooted and all's well at this time.

Link to post

I started preclearing a disk the other day using the new SimpleFeatures, all was working fine until I closed my browser. Upon re-opening I could no longer access the WEB GUI. There is disk activity on my raid where I installed the new drive, and I can access the folders on the RAID, however I no longer have access to the web GUI. I tried this a couple of times (having had to reboot the server & do a parity check). I've left it alone the past 24 hours & will check again to see of the activity lights are still going. Has anyone else encountered this problem?

What unRAID version are you using ?

 

unRAID Pro 5.0 rc-11

It can be a lack of memory problem, killing the emhttp process.

 

 

Check if emhttp is listening... (your port may be different as shown here )

 

Here's what it's listing:

emhttp    18717  root    3u  IPv4  23098      0t0  TCP *:http (LISTEN)

 

I rebooted however SimpleFeatures is now disabled & it's back to the Unraid default GUI. I haven't added the cleared disk to the array yet but everything else is running normally. Syslog attached.

syslog.zip

Link to post

I rebooted however SimpleFeatures is now disabled & it's back to the Unraid default GUI. I haven't added the cleared disk to the array yet but everything else is running normally. Syslog attached.

Your syslog shows all SF packages v1.0.11 to be correctly installed, but get overwritten by SF version 1.0.5...

 

Remove the simpleFeatures*.plg files in the folder /boot/config/plugins

 

Also you are loading all available SF packages, great but do you use them all ?

 

In case of problems, first bring it back to the essentials, the core-webGUI is required all others are optional.

 

 

Link to post

I see some line in syslog showing ...

 

Feb 23 06:40:58 tower kernel: php[28788]: segfault at 4a38424b ip 0825dd50 sp bf99b1a0 error 4 in php[8048000+667000] (Errors)

 

SF issue ?

 

//Peter

Don't have this in my log... Perhaps a conflict with another plugin ?

Link to post

Just noticed this error, not sure exactly how to proceed since I'm a linux n00b

 

 Warning: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PST/-8.0/no DST' instead in /usr/local/emhttp/plugins/webGui/template.php on line 41 Sat Feb 23 11:08:56 2013 PST

Link to post

Just noticed this error, not sure exactly how to proceed since I'm a linux n00b

 

 Warning: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PST/-8.0/no DST' instead in /usr/local/emhttp/plugins/webGui/template.php on line 41 Sat Feb 23 11:08:56 2013 PST

I had that error message in the webgui (didn't bother to check the syslog) after the SF upgrade.  I set the time, Apply, done, then rebooted and it went away.

Link to post

Just noticed this error, not sure exactly how to proceed since I'm a linux n00b

 

 Warning: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PST/-8.0/no DST' instead in /usr/local/emhttp/plugins/webGui/template.php on line 41 Sat Feb 23 11:08:56 2013 PST

I had that error message in the webgui (didn't bother to check the syslog) after the SF upgrade.  I set the time, Apply, done, then rebooted and it went away.

 

The moment I hit apply on the date and time, I lose the webGUI entirely.  I had to manually stop samba and unmount all the drives. 

 

EDIT (forgot to add): When I reboot, I still have the same error.

Link to post

Just noticed this error, not sure exactly how to proceed since I'm a linux n00b

 

 Warning: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PST/-8.0/no DST' instead in /usr/local/emhttp/plugins/webGui/template.php on line 41 Sat Feb 23 11:08:56 2013 PST

I had that error message in the webgui (didn't bother to check the syslog) after the SF upgrade.  I set the time, Apply, done, then rebooted and it went away.

 

The moment I hit apply on the date and time, I lose the webGUI entirely.  I had to manually stop samba and unmount all the drives. 

 

EDIT (forgot to add): When I reboot, I still have the same error.

You need to confirm you are loading the current SF version, and be sure the old version is removed.  I would reboot and then post your syslog here.  Haven't seen anyone post that they lost the webgui by just trying to set the date, so you need to confirm you are on RC11 and using 1.0.11 of SF.

Link to post

Just noticed this error, not sure exactly how to proceed since I'm a linux n00b

 

 Warning: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PST/-8.0/no DST' instead in /usr/local/emhttp/plugins/webGui/template.php on line 41 Sat Feb 23 11:08:56 2013 PST

I had that error message in the webgui (didn't bother to check the syslog) after the SF upgrade.  I set the time, Apply, done, then rebooted and it went away.

 

The moment I hit apply on the date and time, I lose the webGUI entirely.  I had to manually stop samba and unmount all the drives. 

 

EDIT (forgot to add): When I reboot, I still have the same error.

You need to confirm you are loading the current SF version, and be sure the old version is removed.  I would reboot and then post your syslog here.  Haven't seen anyone post that they lost the webgui by just trying to set the date, so you need to confirm you are on RC11 and using 1.0.11 of SF.

 

Hnnctg5.png

 

Using rc11a, and you can see the simpleFeatures version in the bottom of the screenshot

Link to post

@ogi - post your syslog.  Also, why are you running 11a?  rc11 is the current RC.  RC11a was a test for only a couple of users.  If you did the upgrade from SF 1.0.5 to 1.0.11, did you make sure you deleted the old SF config files?

Link to post

@ogi - post your syslog.  Also, why are you running 11a?  rc11 is the current RC.  RC11a was a test for only a couple of users.  If you did the upgrade from SF 1.0.5 to 1.0.11, did you make sure you deleted the old SF config files?

 

I'll post a syslog when I'm home.  RC11a as I understand was a general release but had so few bug fixes that Tom didn't create his own thread about it.  He made a post about it on the RC11 thread.  I believe the "test" designators are the one for individual users.

 

I deleted the 1.0.5 simply features config files ...but I may not have deleted them after putting the new SimpleFeatures install and run. 

 

I may nuke all the config files for SimpleFeatures and try again and see what happens.

 

Ogi

Link to post
  • Squid locked this topic
Guest
This topic is now closed to further replies.