Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

"SimpleFeatures" Plugin - Version 1.0.11

Featured Replies

Possible Bug with cache_dir component of SimpleFeatures:

 

Create share with space in name (e.g. "Wayback Machine").  Add to exclusion list (this is a Time Machine backup on a single drive).

 

Start process and see error:

 

cache_dirs: ERROR: excluded directory "'Wayback" does not exist. (Errors)

 

Note "Wayback" vs. "Wayback Machine"

 

thx!

  • Replies 2.8k
  • Views 827.9k
  • Created
  • Last Reply

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 :)

 

Good news. New SF releases are always fun.

 

Any chance you guys have been able to suppress the logfile spamming ? That's my biggest bugbear at the moment.

Possible Bug with cache_dir component of SimpleFeatures:

 

Create share with space in name (e.g. "Wayback Machine").  Add to exclusion list (this is a Time Machine backup on a single drive).

 

Start process and see error:

 

cache_dirs: ERROR: excluded directory "'Wayback" does not exist. (Errors)

 

Note "Wayback" vs. "Wayback Machine"

 

thx!

 

Confirmed, I have the same behaviour. I want to excluded my itunes library because of its enormous amount of dirs (its called My Music) and get the same error.

I can't seem to find the correct syntax for cache_dirs itself...

 

Usually quoting the name does the trick, e.g. cache_dirs -e "My Share", but the script is not able to find the name when it contains a space.

root@vesta:/# ls -l /mnt/user

total 11

drwxrwx--- 1 nobody users  48 2012-12-28 13:59 My\ Share/

 

root@vesta:/# cache_dirs -e "My Share"

ERROR: excluded directory "My Share" does not exist.

cache_dirs process ID 13661 started, To terminate it, type: cache_dirs -q

 

root@vesta:/# cache_dirs -e My\ Share

ERROR: excluded directory "My Share" does not exist.

cache_dirs process ID 21266 started, To terminate it, type: cache_dirs -q

 

 

I can't seem to find the correct syntax for cache_dirs itself...

 

Usually quoting the name does the trick, e.g. cache_dirs -e "My Share", but the script is not able to find the name when it contains a space.

root@vesta:/# ls -l /mnt/user

total 11

drwxrwx--- 1 nobody users  48 2012-12-28 13:59 My\ Share/

 

root@vesta:/# cache_dirs -e "My Share"

ERROR: excluded directory "My Share" does not exist.

cache_dirs process ID 13661 started, To terminate it, type: cache_dirs -q

 

root@vesta:/# cache_dirs -e My\ Share

ERROR: excluded directory "My Share" does not exist.

cache_dirs process ID 21266 started, To terminate it, type: cache_dirs -q

 

Joe L should know !

There might be another service aggressively taking over port 80. When this happens again, try running this command: lsof -i | grep 80

 

I'm dubious that it's SimpleFeatures causing an issue. Even if there is a configuration issue with the web server plugin, it doesn't ever start before emhttp, therefore lighttpd conflicts with the port and never starts. None of the other services are heavy weight, with the worst of memory leaks you'd be using 50MB tops over a few months.

 

I hope we find the source of this problem either way.

 

It happened again (http://lime-technology.com/forum/index.php?topic=23274.msg216863#msg216863)

 

here is the output of lsof -i | grep 80:

root@Tower:~#     lsof -i | grep 80
rpc.portm  1080    bin    4u  IPv4    5317      0t0  UDP *:sunrpc
rpc.portm  1080    bin    5u  IPv4    5318      0t0  TCP *:sunrpc (LISTEN)
ntpd       1101   root   19u  IPv4   37180      0t0  UDP 25.203.119.109:ntp
vboxwebsr 17413   root    9u  IPv4   34600      0t0  TCP Tower:18083 (LISTEN)

 

I do not see any problem here.

Everything else seems to be running fine.

No indication in the syslog that anything happened.

 

do you want me to check anything else before I reboot?

 

Can you do?  lsof -i -P | grep 80

 

See below:

root@Tower:~#  lsof -i -P | grep 80
rpc.portm  1080    bin    4u  IPv4    5317      0t0  UDP *:111
rpc.portm  1080    bin    5u  IPv4    5318      0t0  TCP *:111 (LISTEN)
ntpd       1101   root   19u  IPv4   37180      0t0  UDP 25.203.119.109:123
emhttp    17038   root    3u  IPv4   30261      0t0  TCP *:80 (LISTEN)
emhttp    17038   root    5u  IPv4 5929588      0t0  TCP 192.168.2.104:80->192.168.2.201:40088 (ESTABLISHED)
vboxwebsr 17413   root    9u  IPv4   34600      0t0  TCP Tower:18083 (LISTEN)
Plex      17735   root   54u  IPv4 6377431      0t0  TCP 192.168.2.104:32469->192.168.2.120:38098 (ESTABLISHED)

 

What does this line mean?

emhttp    17038   root    5u  IPv4 5929588      0t0  TCP 192.168.2.104:80->192.168.2.201:40088 (ESTABLISHED)

 

What does this line mean?

emhttp    17038   root    5u  IPv4 5929588      0t0  TCP 192.168.2.104:80->192.168.2.201:40088 (ESTABLISHED)

It means there is an active TCP session from the PC with address 192.168.2.201 to your unRAID server. In other words from said PC the web GUI is opened and should work !

 

@theone

 

Can you tell me the size of your syslog file ?

 

ls -l /var/log/syslog

 

It means there is an active TCP session from the PC with address 192.168.2.201 to your unRAID server. In other words from said PC the web GUI is opened and should work !

 

That IP is my Samsung Galaxy II - it does not show the WEBUI as well.

 

@theone

 

Can you tell me the size of your syslog file ?

 

ls -l /var/log/syslog

 

He it is:

root@Tower:~# ls -l /var/log/syslog
-rw-r--r-- 1 root root 192233 2012-12-29 22:36 /var/log/syslog

 

Not too large.

 

Interestingly enough, I think it needs to be, e.g.:

 

cache_dirs -e "My\ Share"

 

(at least that's how it was in my old "go" file...)

 

 

I can't seem to find the correct syntax for cache_dirs itself...

 

Usually quoting the name does the trick, e.g. cache_dirs -e "My Share", but the script is not able to find the name when it contains a space.

root@vesta:/# ls -l /mnt/user

total 11

drwxrwx--- 1 nobody users  48 2012-12-28 13:59 My\ Share/

 

root@vesta:/# cache_dirs -e "My Share"

ERROR: excluded directory "My Share" does not exist.

cache_dirs process ID 13661 started, To terminate it, type: cache_dirs -q

 

root@vesta:/# cache_dirs -e My\ Share

ERROR: excluded directory "My Share" does not exist.

cache_dirs process ID 21266 started, To terminate it, type: cache_dirs -q

Interestingly enough, I think it needs to be, e.g.:

 

cache_dirs -e "My\ Share"

Funnily enough I didn't try that combination  ;)

 

The good news: it works !!!

 

I updated the cache_dirs plugin and have it working.

 

In the GUI you can enter the file names without quotes or special escapes for spaces, in other words you just type the name as is...

 

Thanks for sorting this out.

bonienl,

 

Any new insight regarding the WEBUI crashing?

 

 

For some reason it seems like I need to reenable the webserver lately after rebooting, it is set to auto run but after restart it needs an "apply" to start.. Only thing I changed is setting up a lighttpd.cfg to facilitatie spotweb, newznab and my main webserver..

For some reason it seems like I need to reenable the webserver lately after rebooting, it is set to auto run but after restart it needs an "apply" to start.. Only thing I changed is setting up a lighttpd.cfg to facilitatie spotweb, newznab and my main webserver..

 

That is a known issue.

 

Hello guys new so please be gentle. I am having issues accessing simplefeatures GUI. I followed the instruction. copy to /boot/config/plugins folder then reboot. I also tried to install manually, however everytime I type in //tower it goes to the basic UI. I am not a linux expert.

 

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

installing plugin: simple-features.core.webGUI-1.0.5-noarch-1

 

Warning: simplexml_load_file(): I/O warning : failed to load external entity "si                                      mple-features.core.webGUI-1.0.5-noarch-1.plg" in /usr/local/sbin/installplg on l                                      ine 13

xml parse error

 

Hello guys new so please be gentle. I am having issues accessing simplefeatures GUI. I followed the instruction. copy to /boot/config/plugins folder then reboot. I also tried to install manually, however everytime I type in //tower it goes to the basic UI. I am not a linux expert.

 

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

installing plugin: simple-features.core.webGUI-1.0.5-noarch-1

 

Warning: simplexml_load_file(): I/O warning : failed to load external entity "si                                      mple-features.core.webGUI-1.0.5-noarch-1.plg" in /usr/local/sbin/installplg on l                                      ine 13

xml parse error

 

It is a known "race condition" existing in unRAID (it depends on your network settings).

 

Next version of SF has a workaround to overcome a not ready network condition. It will be released soon.

 

Meanwhile you can manually install the plugins (telnet into your box and issue the installplg command). Once a package is locally present it is not necessary to download it upon system reboot. In other words a system reboot will work fine...

 

bonienl,

 

Any new insight regarding the WEBUI crashing?

I can't reproduce your problem, that is the GUI stays stable for weeks (read: emhttp is accessible and responding all the time).

 

You may want to see what other plugins you have installed and remove them all or one by one to observe a different behaviour (my guess is something in your system is eating memory)...

 

my guess is something in your system is eating memory)...

But emhttp is still running...

my guess is something in your system is eating memory)...

But emhttp is still running...

 

But lack of memory can cause your running emhttp process to get into trouble...

Is there a reason the NFS rules box will only allow a certain amount of characters, is there a way to remove this limit?

Which memory should I look at? low or high?

 

I had a similar problem with the GUI no longer responding.  After reading through various threads, the common consensus is the OOM_killer is killing them off when it needs some additional memory.  I call this script as part of my boot sequence.  It sets the "emhttp" and samba shares to not be killed off.  I have not had any issues after I started using this script.  As this gets logged in my syslog when it runs, I do a before and after check.  It might help you and it might not depending on the source of your issues.

 

The bottom block of code is all you really need.  The other comments/info are notes to myself. 

 

#!/bin/bash
# Wait 120 seconds to ensure SAMBA has started.
# sleep 120
#############################################
# This adjusts the PID for UNRAID server and Shares process may never be killed in a low memory condition.
#############################################
# From http://lime-technology.com/forum/index.php?topic=20013.msg200115;topicseen#msg20011
# 
# 
# From https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s2-proc-pid.html
# and
# From http://www.kernel.org/doc/man-pages/online/pages/man5/proc.5.html
# # 
# There is also a special value of -17, which disables oom_killer for a process. 
# An oom_score of a value of 0, indicates that this process would not be killed.
# 
# Use the following command to view the score.  It should be "0" after running the commands below
#  cat /proc/[pid]/oom_score
# 
# To see the path for where the program lives.
# /usr/sbin/smbd
# 
# To view current PID use:
#  pgrep -f "/usr/local/sbin/emhttp"
#  pgrep -f "/usr/sbin/smbd"
# 
# Combined command to find the PID and show the score.
#  pgrep -f "/usr/local/sbin/emhttp" | while read PID; do cat /proc/$PID/oom_score; done
#  pgrep -f "/usr/sbin/smbd" | while read PID; do cat /proc/$PID/oom_score; done
# 
#############################################
# Set UNRAID webserver is never killed off.
# pgrep -f "/usr/local/sbin/emhttp" | while read PID; do echo -17 > /proc/$PID/oom_adj; done
# 
# Set SAMBA so shares are never killed off.
# pgrep -f "/usr/sbin/smbd" | while read PID; do echo -17 > /proc/$PID/oom_adj; done
#############################################
#
#
# Uses the new oom_score_adj
#############################################
# Check the OOM values before the change
pgrep -f "/usr/local/sbin/emhttp" | while read PID; do cat /proc/$PID/oom_score; done
pgrep -f "/usr/sbin/smbd" | while read PID; do cat /proc/$PID/oom_score; done

# Set UNRAID webserver is never killed off.
pgrep -f "/usr/local/sbin/emhttp" | while read PID; do echo -1000 > /proc/$PID/oom_score_adj; done
# 
# Set SAMBA so shares are never killed off.
pgrep -f "/usr/sbin/smbd" | while read PID; do echo -1000 > /proc/$PID/oom_score_adj; done
#
# Check the OOM values after the change
pgrep -f "/usr/local/sbin/emhttp" | while read PID; do cat /proc/$PID/oom_score; done
pgrep -f "/usr/sbin/smbd" | while read PID; do cat /proc/$PID/oom_score; done
#############################################

As I wrote before I already have these lines set (oom_score_adj).

Just to clarify - emhttp does not get killed, it is still running but unresponsive.

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.