"SimpleFeatures" Plugin - Version 1.0.11



Recommended Posts

  • Replies 2.8k
  • Created
  • Last Reply

Top Posters In This Topic

I am having problem with SF in RC13. emhttp doesn't seem to respond. I had to restart for it to work.

 

Mine wasn't responding either last night either, but this morning it seems to be fine. Didn't do anything just left it overnight and it all came good. Unmenu was working fine last night and this morning, so it was just sf.

 

Sent from my Nexus 4 using Tapatalk 2

 

 

Link to comment

Can someone please help me out. I am running 12a and just installed simplefeatures.

 

I would like to preclear a disk that is not installed in the array yet. I have the .plg file with all the other plugins however I don't see an option of where to go for preclear. Is it in a hidden menu somewhere? Would be great if someone could help me out

Link to comment

Can someone please help me out. I am running 12a and just installed simplefeatures.

 

I would like to preclear a disk that is not installed in the array yet. I have the .plg file with all the other plugins however I don't see an option of where to go for preclear. Is it in a hidden menu somewhere? Would be great if someone could help me out

 

I believe firing off from the Command line is the preferred method. I can't seem to find it, but there was some discussion about SF using a modified version of the pre_clear script. I don't if that ever got sorted out.

 

It takes all of 10 minutes to get pre_clear downloaded, extracted and running... with very little linux knowledge required...

 

Link to comment

Can someone please help me out. I am running 12a and just installed simplefeatures.

 

I would like to preclear a disk that is not installed in the array yet. I have the .plg file with all the other plugins however I don't see an option of where to go for preclear. Is it in a hidden menu somewhere? Would be great if someone could help me out

It is not a part of simple-features,  it is available here

http://lime-technology.com/forum/index.php?topic=2817.0

and invoked from the command line.

 

Link to comment

I'm' seeing the same issues with SF not responding via the webgui / browser.  Sometimes I get  right in, and other times it just times out and never connects.  I've tested with Chrome, IE and Safari, same results.  It seems SF webgui has become unstable, or should I say more unstable than before.

Link to comment

I was wondering what this means?

 

file /boot/plugins/simpleFeatures/simpleFeatures.disk.preclear-1.0.10-i486-1.txz: downloading from http://unraid-simplefeatures.googlecode.com/files/simpleFeatures.disk.preclear-1.0.10-i486-1.txz ... bad download, deleting

 

and

 

file /boot/packages/sqlite-3.7.14.1-i486-1.txz: downloading from http://slackware.cs.utah.edu/pub/slackware/slackware-current/slackware/ap/sqlite-3.7.14.1-i486-1.txz ... bad download, deleting

 

Does any one else see this in there log file? how can I fix this?

 

 

Link to comment

I was wondering what this means?

 

file /boot/plugins/simpleFeatures/simpleFeatures.disk.preclear-1.0.10-i486-1.txz: downloading from http://unraid-simplefeatures.googlecode.com/files/simpleFeatures.disk.preclear-1.0.10-i486-1.txz ... bad download, deleting

 

and

 

file /boot/packages/sqlite-3.7.14.1-i486-1.txz: downloading from http://slackware.cs.utah.edu/pub/slackware/slackware-current/slackware/ap/sqlite-3.7.14.1-i486-1.txz ... bad download, deleting

 

Does any one else see this in there log file? how can I fix this?

 

Sometings trying to install an out of date version of sqlite find the plg file and update the relevent line of code to:

http://slackware.cs.utah.edu/pub/slackware/slackware-current/slackware/ap/sqlite-3.7.16-i486-1.txz

 

If memory serves its the web server plug-in in SF

 

pre clear for SF was removed, delete the relevant plg file from your SF directory

Link to comment

Feature Request:

Please change the S3_Sleep plugin to exlude drives outside the array (or better: drives specified by the user in the plugins config) from the hdd activity check. I installed a ssd drive in my system (outside the array) which reports active/idle when inactive. At the moment this is recognized as active by the s3_sleep script and the system never goes to sleep anymore. So I want to exclude the drive from the list.

 

@speeding_ant:

I would make this change myself, but the google code repository seems to be empty?! So I can't clone it. And I guess I won't be able to create a working pull request or whatever it is called in mercurial either. Do you have the code on github somewhere? Alternatively I could send you the changed files by mail or post them somewhere if you like.

Link to comment

it would be great if we had a way to get back to the stock native unraid webgui as a backup for when SF dies.  Is that possible? I can use unmenu, so why not the stock webgui?

 

I think unMenu has it's own webserver; simple features replaces the stock one. I too would love if we can Frankenstein the best of UM and SF.

 

 

Link to comment

it would be great if we had a way to get back to the stock native unraid webgui as a backup for when SF dies.  Is that possible? I can use unmenu, so why not the stock webgui?

Well, cant you just pull out SF and reboot? after that it should just give you the stock gui. To do it without rebooting would be more of a pain, you would have to go back and replace all the gui files in active memory with the originals...

Link to comment

it would be great if we had a way to get back to the stock native unraid webgui as a backup for when SF dies.  Is that possible? I can use unmenu, so why not the stock webgui?

Well, cant you just pull out SF and reboot? after that it should just give you the stock gui. To do it without rebooting would be more of a pain, you would have to go back and replace all the gui files in active memory with the originals...

 

i think the point is that when the emhttp goes unresponsive, it becomes increasingly difficult to *safely* shutdown the array.

Link to comment

Well, cant you just pull out SF and reboot?

SimpleFeatures is an alternative "skin" for the stock unRAID interface (emhttp).  If emhttp crashes, it does not matter which "skin" you've installed, you cannot shut down unRAID easily.  emhttp cannot be re-started on the 5.0 series of unRAID without un-mounting all the disks and removing all the mount-points.  That cannot occur without stopping the array.  You can't easily stop the array if you do not have emhttp.

 

unMENU is its own web-server (written in "awk") and entirely independent.  It has enough logic to shut down the server as cleanly as it can in place of emhttp.  (It kiils processes, un-mounts drives, stops the array)    It cannot re-start emhttp, nor administer the array.  It can let you reboot.

Link to comment

Hi All

 

Hoping someone could help me out, I seem to be having and issue with the iTunes server plugin on 5.0 rc 12a.

 

I can see my unraid as a shared library, I can move music into my music folder but cannot see the music.

 

I am getting this error in "/var/log/forked-daapd/forked-daapd.log"

 

 

/usr/bin/tail -n 1000 -f /var/log/forked-daapd/forked-daapd.log

[2013-06-09 04:10:41] main: Forked Media Server Version 0.19gcd taking off

[2013-06-09 04:10:41] main: mDNS init

[2013-06-09 04:10:41] mdns: Avahi state change: Client registering

[2013-06-09 04:10:41] db: Could not prepare statement: no such table: admin

[2013-06-09 04:10:41] db: Could not check database version, trying DB init

[2013-06-09 04:10:41] scan: Could not lstat() '/mnt/music/itunesdb/songs3.db-journal': No such file or directory

[2013-06-09 04:10:41] scan: Could not lstat() '/mnt/music/itunesdb/songs3.db-journal': No such file or directory

[2013-06-09 04:10:41] scan: Could not lstat() '/mnt/music/itunesdb/songs3.db-journal': No such file or directory

[2013-06-09 04:10:41] scan: Could not lstat() '/mnt/music/itunesdb/songs3.db-journal': No such file or directory

[2013-06-09 04:10:41] scan: Could not lstat() '/mnt/music/itunesdb/songs3.db-journal': No such file or directory

[2013-06-09 04:10:41] scan: Could not lstat() '/mnt/music/itunesdb/songs3.db-journal': No such file or directory

[2013-06-09 04:10:42] mdns: Avahi state change: Client running

 

 

Would this be causing the issue and does anyone know how to resolve it?

 

Thanks

 

Lee

 

Link to comment

it would be great if we had a way to get back to the stock native unraid webgui as a backup for when SF dies.  Is that possible? I can use unmenu, so why not the stock webgui?

Well, cant you just pull out SF and reboot? after that it should just give you the stock gui. To do it without rebooting would be more of a pain, you would have to go back and replace all the gui files in active memory with the originals...

 

i think the point is that when the emhttp goes unresponsive, it becomes increasingly difficult to *safely* shutdown the array.

exactly.  This happened again yesterday, SF died again, and I had to use unmenu to stop the array.  The sad news is that as soon as I hit Stop on unmenu, it too because non-responsive.  I had to use the console and Powerdown, which didn't power all the way down.  So, had to issue the reboot command and it rebooted. 

 

I did not have these issues with rc11, and it first showed it ugly head in rc12a for me, but is now very bad.  SF just isn't happy.

 

@Speeding Ant - do you already know the root cause for this?  Even better, do you know how to fix it?  If you need syslogs or anything, let me know.  I just figured given this has been a issue with so many people reporting it, you must already have figured out what the cause is.  Please fix and update SF.  :)

Link to comment

it would be great if we had a way to get back to the stock native unraid webgui as a backup for when SF dies.  Is that possible? I can use unmenu, so why not the stock webgui?

Well, cant you just pull out SF and reboot? after that it should just give you the stock gui. To do it without rebooting would be more of a pain, you would have to go back and replace all the gui files in active memory with the originals...

 

i think the point is that when the emhttp goes unresponsive, it becomes increasingly difficult to *safely* shutdown the array.

exactly.  This happened again yesterday, SF died again, and I had to use unmenu to stop the array.  The sad news is that as soon as I hit Stop on unmenu, it too because non-responsive.  I had to use the console and Powerdown, which didn't power all the way down.  So, had to issue the reboot command and it rebooted. 

 

I did not have these issues with rc11, and it first showed it ugly head in rc12a for me, but is now very bad.  SF just isn't happy.

 

@Speeding Ant - do you already know the root cause for this?  Even better, do you know how to fix it?  If you need syslogs or anything, let me know.  I just figured given this has been a issue with so many people reporting it, you must already have figured out what the cause is.  Please fix and update SF.  :)

If you are running uot of memory, then any process that is idle will be killed.  I've had times when logging in would have my login session killed.  (granted, I was attempting to compile something I did not have the memory for, so I knew the cause of the OOM condition)

 

It might not be SimpleFeatures itself, but it is a symptom of memory used by one of your other add-ons.

Link to comment

it would be great if we had a way to get back to the stock native unraid webgui as a backup for when SF dies.  Is that possible? I can use unmenu, so why not the stock webgui?

Well, cant you just pull out SF and reboot? after that it should just give you the stock gui. To do it without rebooting would be more of a pain, you would have to go back and replace all the gui files in active memory with the originals...

 

i think the point is that when the emhttp goes unresponsive, it becomes increasingly difficult to *safely* shutdown the array.

exactly.  This happened again yesterday, SF died again, and I had to use unmenu to stop the array.  The sad news is that as soon as I hit Stop on unmenu, it too because non-responsive.  I had to use the console and Powerdown, which didn't power all the way down.  So, had to issue the reboot command and it rebooted. 

 

I did not have these issues with rc11, and it first showed it ugly head in rc12a for me, but is now very bad.  SF just isn't happy.

 

@Speeding Ant - do you already know the root cause for this?  Even better, do you know how to fix it?  If you need syslogs or anything, let me know.  I just figured given this has been a issue with so many people reporting it, you must already have figured out what the cause is.  Please fix and update SF.  :)

If you are running uot of memory, then any process that is idle will be killed.  I've had times when logging in would have my login session killed.  (granted, I was attempting to compile something I did not have the memory for, so I knew the cause of the OOM condition)

 

It might not be SimpleFeatures itself, but it is a symptom of memory used by one of your other add-ons.

 

+1, the only time I've personally seen the GUI go down is when Plex shat itself. I've raised a few things with Tom anyhow - however he's quite preoccupied with releasing V5 final.

Link to comment

I was wondering what this means?

 

file /boot/packages/sqlite-3.7.14.1-i486-1.txz: downloading from http://slackware.cs.utah.edu/pub/slackware/slackware-current/slackware/ap/sqlite-3.7.14.1-i486-1.txz ... bad download, deleting

 

Does any one else see this in there log file? how can I fix this?

You can edit the simple features web plugin file and change the two sqlite-3.7.14.1-I486-1.txz lines towards the top of the file to sqlite-3.7.14.1-i486-1_slack14.0.txz and change slackware-current to slackware-14.0 save and reboot or try reinstalling the web server plugin after the changes.  If you don't use the web server delete the plugin.  Maybe it was just me but I use the 3.7.16 ver for other plugins but had gui issues not using 3.7.14 with the web server.

 

Link to comment

I no longer think that SF is the root cause.  I'm not sure what rc13 did to SF, and unmenu, but things are not good.

 

I rolled back to rc12a, and SF is just fine again.  I haven't changed any of my plugins or memory, so I would hope that isn't it.  I think the issues have to do with rc13.  I never had any issues with unmenu before rc13 and I didn't have that many response issues with rc12a for SF.

 

I hope thing can be worked out to make them both happy at the same time. 

 

Link to comment

What is the ".DS_Store" file in the Plugin folder? Can I delete this along with the plugins I don't want to use?

 

Also is there something I need to add to Chrome to make it look right in the web browser? Or do I have to use INternet Explorer for it to look like it does in the pictures?

Link to comment

What is the ".DS_Store" file in the Plugin folder? Can I delete this along with the plugins I don't want to use?

 

Also is there something I need to add to Chrome to make it look right in the web browser? Or do I have to use INternet Explorer for it to look like it does in the pictures?

 

that's created by the beloved Apple Finder.  :o

 

it does that whenever you access a network share. as a sys admin on the windows side, this annoys me to no end.

 

screenshot what it looks like to you - mine looked OK in Chrome and IE

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