concise procedure to install/unintall plugins?

[CaptainTivo]

I have just upgraded from 4.7 to 5.0, thinking that it MUST be stable by now :-).

I installed Simple Features and everything seems to be going to hell, so I tried to uninstall it.

Problem is: no one seems to know exactly how plugins are uninstalled.

 

Here is my boot flash config:

 

/boot
   	bzimage*
bzroot*
config/
ldlinux.sys*
license.txt*
logs/
make_bootable.bat*
memtest*
menu.c32*
packages/
plugins/
preclear_reports/
readme.txt*
syslinux.cfg*
syslinux.exe*
unmenu/

here is config:

Pro2.key*
disk.cfg*
go*
go.old47*
ident.cfg*
my_scripts/
network.cfg*
plugins/
share.cfg*
shares/
simpleFeatures/
smb-extra.conf*
smb-extra.conf~*
snap/
super.dat*

 

here is /boot/config/plugins:

mysql-ikosa.plg.hide*
simpleFeatures.active.streams-1.0.10-noarch-1.plg*
simpleFeatures.activity.monitor-1.0.11-noarch-1.plg*
simpleFeatures.cache.dirs-1.0.11-noarch-1.plg*
simpleFeatures.core.webGUI-1.0.11-noarch-1.plg*
simpleFeatures.disk.health-1.0.11-noarch-1.plg*
simpleFeatures.disk.preclear-1.0.10-noarch-1.plg.hide*
simpleFeatures.email.notify-1.0.10-noarch-1.plg*
simpleFeatures.log.viewer-1.0.10-noarch-1.plg*
simpleFeatures.s3.sleep-1.0.10-noarch-1.plg*
simpleFeatures.system.info-1.0.10-noarch-1.plg*
simpleFeatures.system.stats-1.0.10-noarch-1.plg*
simpleFeatures.system.temp-1.0.11-noarch-1.plg*
simpleFeatures.web.server-1.0.11-noarch-1.plg.hide*

 

I renamed some of the plugins ".hide" to prevent them from being installed because they did not seem to work.

 

I did a bit of searching in the forum and found the consensus to uninstall plugins is the simply delete them from /boot/config/plugins.  I tried simply renaming /boot/plugins to /boot/plugins.hide and /boot/config/plugins to /boot/config/plugins.hide.

 

This caused continuous messages on the console:

 

"Could not open input file: plugins/simpleFeatures/include/SystemTemp.php"

and the web page gui would not open.

So I renamed /boot/plugins.hide back to /boot/plugins and the messages stopped.

 

So the question is: EXACTLY how are plugins "installed/enabled" and how are they "disabled"?

 

 

 

 

[Influencer]

If the plug-in is present in /boot/config/plugins and named with extension .plg it will be installed at boot. To uninstall you either need to 1) know what files were installed and where, then delete them or 2) remove/rename the plug-in and reboot the server.

 

Rebooting the server is easiest and you'll know for sure that it is uninstalled.

 

In /boot/config/plugins I have another directory named "disabled", that's where I put any plug-ins I don't want reinstalled when I reboot.

[CaptainTivo]

Well, no joy.  I removed the plugins directory completely from /boot/config and I still have this message continuously printing on the console:

 

"Could not open input file: plugins/simpleFeatures/include/SystemTemp.php"

 

here is /boot/config:

root@Tower:/boot/config# ls -1
Pro2.key*
disk.cfg*
go*
go.old47*
ident.cfg*
my_scripts/
network.cfg*
share.cfg*
shares/
smb-extra.conf*
smb-extra.conf~*
snap/
super.dat*
root@Tower:/boot/config#

here is my go script:

root@Tower:/boot/config# cat go
#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &
#/boot/unmenu/uu

#cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c

 

So there is no plugins directory at all.  Why are the simple features plugins include files still needed?  I am starting to think that simpleFeatures has actually altered the unRaid installation in some way.  Is this correct?  Can anyone point me to documentation on plugins?  How to install/uninstall, etc?

 

Also, my log file is filling up with this sequence.  It is repeated every 20 seconds.  Can this be right?

 

Nov  2 09:43:38 Tower kernel: md: unRAID driver removed
Nov  2 09:43:38 Tower emhttp: shcmd (11): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger
Nov  2 09:43:38 Tower emhttp: shcmd (12): udevadm settle
Nov  2 09:43:38 Tower kernel: md: unRAID driver 2.1.6 installed
Nov  2 09:43:38 Tower emhttp: Device inventory:
Nov  2 09:43:38 Tower emhttp: WDC_WD30EZRX-00DC0B0_WD-WCC1T1338318 (sdb) 2930266584
Nov  2 09:43:38 Tower emhttp: WDC_WD20EARS-00MVWB0_WD-WCAZA4336067 (sdc) 1953514584
Nov  2 09:43:38 Tower emhttp: ST2000DL003-9VT166_5YD5VLHE (sdd) 1953514584
Nov  2 09:43:38 Tower emhttp: ST32000542AS_6XW15Y6A (sde) 1953514584
Nov  2 09:43:38 Tower emhttp: SAMSUNG_HD103UI_S1LMJ90QC35509 (sdf) 976762584
Nov  2 09:43:38 Tower emhttp: WDC_WD20EARX-00PASB0_WD-WMAZA6041844 (sdg) 1953514584
Nov  2 09:43:38 Tower emhttp: ST31000528AS_9VP6J2BT (sdh) 976762584
Nov  2 09:43:38 Tower emhttp: WDC_WD20EARS-00MVWB0_WD-WCAZA0765138 (sdi) 1953514584
Nov  2 09:43:38 Tower emhttp: WDC_WD10EADS-00L5B1_WD-WCAU46849918 (sdj) 976762584
Nov  2 09:43:38 Tower kernel: mdcmd (1): import 0 8,16 2930266532 WDC_WD30EZRX-00DC0B0_WD-WCC1T1338318
Nov  2 09:43:38 Tower kernel: md: import disk0: [8,16] (sdb) WDC_WD30EZRX-00DC0B0_WD-WCC1T1338318 size: 2930266532
Nov  2 09:43:38 Tower kernel: mdcmd (2): import 1 8,32 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA4336067
Nov  2 09:43:38 Tower kernel: md: import disk1: [8,32] (sdc) WDC_WD20EARS-00MVWB0_WD-WCAZA4336067 size: 1953514552
Nov  2 09:43:38 Tower kernel: mdcmd (3): import 2 8,48 1953514552 ST2000DL003-9VT166_5YD5VLHE
Nov  2 09:43:38 Tower kernel: md: import disk2: [8,48] (sdd) ST2000DL003-9VT166_5YD5VLHE size: 1953514552
Nov  2 09:43:38 Tower kernel: mdcmd (4): import 3 8,64 1953514552 ST32000542AS_6XW15Y6A
Nov  2 09:43:38 Tower kernel: md: import disk3: [8,64] (sde) ST32000542AS_6XW15Y6A size: 1953514552
Nov  2 09:43:38 Tower kernel: mdcmd (5): import 4 8,80 976762552 SAMSUNG_HD103UI_S1LMJ90QC35509
Nov  2 09:43:38 Tower kernel: md: import disk4: [8,80] (sdf) SAMSUNG_HD103UI_S1LMJ90QC35509 size: 976762552
Nov  2 09:43:38 Tower kernel: mdcmd (6): import 5 8,128 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA0765138
Nov  2 09:43:38 Tower kernel: md: import disk5: [8,128] (sdi) WDC_WD20EARS-00MVWB0_WD-WCAZA0765138 size: 1953514552
Nov  2 09:43:38 Tower emhttp: shcmd (13): /usr/local/sbin/emhttp_event driver_loaded
Nov  2 09:43:38 Tower kernel: mdcmd (7): import 6 8,144 976762552 WDC_WD10EADS-00L5B1_WD-WCAU46849918
Nov  2 09:43:38 Tower kernel: md: import disk6: [8,144] (sdj) WDC_WD10EADS-00L5B1_WD-WCAU46849918 size: 976762552
Nov  2 09:43:38 Tower kernel: mdcmd (: import 7 8,112 976762552 ST31000528AS_9VP6J2BT
Nov  2 09:43:38 Tower kernel: md: import disk7: [8,112] (sdh) ST31000528AS_9VP6J2BT size: 976762552
Nov  2 09:43:38 Tower kernel: mdcmd (9): import 8 0,0
Nov  2 09:43:38 Tower kernel: mdcmd (10): import 9 0,0
Nov  2 09:43:38 Tower kernel: mdcmd (11): import 10 0,0
Nov  2 09:43:38 Tower kernel: mdcmd (12): import 11 0,0
Nov  2 09:43:38 Tower kernel: mdcmd (13): import 12 0,0
Nov  2 09:43:38 Tower kernel: mdcmd (14): import 13 0,0
Nov  2 09:43:38 Tower kernel: mdcmd (15): import 14 0,0
Nov  2 09:43:38 Tower kernel: mdcmd (16): import 15 0,0
Nov  2 09:43:38 Tower kernel: mdcmd (17): import 16 0,0
Nov  2 09:43:38 Tower kernel: mdcmd (18): import 17 0,0
Nov  2 09:43:38 Tower kernel: mdcmd (19): import 18 0,0
Nov  2 09:43:38 Tower kernel: mdcmd (20): import 19 0,0
Nov  2 09:43:38 Tower kernel: mdcmd (21): import 20 0,0
Nov  2 09:43:38 Tower kernel: mdcmd (22): import 21 0,0
Nov  2 09:43:38 Tower kernel: mdcmd (23): import 22 0,0
Nov  2 09:43:38 Tower kernel: mdcmd (24): import 23 0,0
Nov  2 09:43:38 Tower emhttp_event: driver_loaded
Nov  2 09:43:38 Tower emhttp: shcmd (14): rmmod md-mod |& logger
Nov  2 09:43:38 Tower emhttp: shcmd (15): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger
Nov  2 09:43:38 Tower kernel: md: unRAID driver removed

[Influencer]

Do you have anything in /boot/extra? or /boot/plugins?

 

There is no real documentation on plug-ins yet as the framework was laid out and users ran with it, but there is no official support. It is being worked on.

[CaptainTivo]

Do you have anything in /boot/extra? or /boot/plugins?

 

There is no real documentation on plug-ins yet as the framework was laid out and users ran with it, but there is no official support. It is being worked on.

 

I don't have anything left in /boot related to the plugins.  I created a directory "hide" and put everything in there.  Unless the plugin installer does some kind of "find *.plg" command, I don't see how it would know they are there.

 

here is /boot:

bzimage*
bzroot*
config/
hide/
ldlinux.sys*
license.txt*
logs/
make_bootable.bat*
memtest*
menu.c32*
packages/
preclear_reports/
readme.txt*
syslinux.cfg*
syslinux.exe*
unmenu/

 

As you can see, I was running unmenu (not at present while I debug this).

 

Here is what is in /boot/hide:

root@Tower:/boot# ls -1 hide
plugins/
plugins.hide/
simpleFeatures.hide/

 

Unless it searches, it should not be able to see the plugins here.

 

What do you think?  Should I delete all the plugin-related files?

 

 

 

 

[CaptainTivo]

Since I am getting these messages on the console,

 

Could not open input file: plugins/simpleFeatures/include/SystemTemp.php
and Could not open input file: plugins/simpleFeatures/include/Notify.php

 

I thought I would search for this include directory.  Executing "find /boot -name "*include*"" gets no output!  The include directory does not exist within /boot.  Maybe the unraid executable ("/usr/local/sbin/emhttp"?) has to decompress some .tgz file to make this directory?  This implies, though, that a .plg filedoes not have to be parsed before these include files are needed, which implies that something OTHER than simply searching /boot/plugins for .pkg files is needed to "install" a plugin.  I am completely confused now.

 

[Influencer]

no, the file its looking for is not located on the flash drive, it is located at /usr/local/emhttp/plugins/simpleFeatures/include/SystemTemp.php

 

Although the very reason that it cannot open it tells me the file most likely will not exist.

 

There is something left over looking for that file, did you do a reboot after removing/hiding all of the plug-ins?

 

Is your unraid installation "normal"? For instance, you have unraid installed to the flash drive and not a disk, not a esxi build, etc?

[CaptainTivo]

no, the file its looking for is not located on the flash drive, it is located at /usr/local/emhttp/plugins/simpleFeatures/include/SystemTemp.php

 

Although the very reason that it cannot open it tells me the file most likely will not exist.

 

There is something left over looking for that file, did you do a reboot after removing/hiding all of the plug-ins?

 

Is your unraid installation "normal"? For instance, you have unraid installed to the flash drive and not a disk, not a esxi build, etc?

 

Yes.  In fact, I just powered it down to be sure.  The messages are still appearing after reboot.

 

My installation is an upgrade from 4.7 to 5.0 using the procedure in the post from Limetech.  I then re-installed unmenu and then installed simpleFeatures.  I did not even know you could install on a hard disk.

 

Anyway, how is that no plugin is being installed and yet the software running is looking for a file that is in the ramfs?  If I guess about how how this stuff works, the only persistent state is in the flash drive.  The include files that it is looking for seem to have something to do with the web interface?  Is it possible that simplefeatures modified this code on the flash drive?

 

 

[itimpi]

Have you checked under /boot/config/plugins in case here is something there that is causing these messages.

[CaptainTivo]

Have you checked under /boot/config/plugins in case here is something there that is causing these messages.

 

Yes.  As I said above, I have removed the plugins folder from /boot/config so, theoretically, there should be NO plugins being loaded.  My real confusion is how, after removing the plugins and the plugins directory, and rebooting,  there is still some behavior that seems to be caused by a plugin.

 

The lack of definitive documentation on how plugins work, how they are installed and uninstalled makes me very wary of them.  I ran 4.7 with unmenu packages for 2 years without any problems.  This does seem to be an improvement to me.

 

I probably should have steered clear of "simpFeatures" when I saw that there are almost 200 pages of posts in the thread.

 

[Influencer]

Actually, simpleFeatures was very stable in the Beta's and I believe only causes issues with unraid if Limetech's upgraded webgui is installed (which is a port of simpleFeatures). Almost 200 pages in a thread is no reason to steer clear, I have a thread that is at 148 pages, a lot of it is questions, some bug reports and feature requests. SimpleFeatures has been around for quite some time, something assuredly wouldn't happen if it was that buggy.

 

There is very little documentation ATM and I haven't ran into any plug-ins that change any system files permanently. Almost all changes are done on the Ramfs and are reversed by a reboot, some changes, such as the VFS_recycle plug-in I just released, modifies a file on the flash drive to include the recycle bin, but disabling it removes the modifications.

 

Again, plug-ins are in their infancy, there is little to no documentation at this time as the system has not been completely designed yet. 5.0 included more framework but plug-ins are a long way from being called mature.

 

Would you be interested in a teamviewer session to see if we can find the cause of the error?

[CaptainTivo]

Actually, simpleFeatures was very stable in the Beta's and I believe only causes issues with unraid if Limetech's upgraded webgui is installed (which is a port of simpleFeatures). Almost 200 pages in a thread is no reason to steer clear, I have a thread that is at 148 pages, a lot of it is questions, some bug reports and feature requests. SimpleFeatures has been around for quite some time, something assuredly wouldn't happen if it was that buggy.

 

There is very little documentation ATM and I haven't ran into any plug-ins that change any system files permanently. Almost all changes are done on the Ramfs and are reversed by a reboot, some changes, such as the VFS_recycle plug-in I just released, modifies a file on the flash drive to include the recycle bin, but disabling it removes the modifications.

 

Again, plug-ins are in their infancy, there is little to no documentation at this time as the system has not been completely designed yet. 5.0 included more framework but plug-ins are a long way from being called mature.

 

Would you be interested in a teamviewer session to see if we can find the cause of the error?

 

You have a point.  Lots of chatter on a topic does not necessarily mean that the project is bad.  However, I have read a lot of the later pages (but certainly not all) and the gist is not good.

 

Anyway, I shut down the server and mounted the flash drive on my normal PC.  The modification dates on the executable files have not changed since I installed them on Oct. 19 so that rules out any kind of permanent change to them.  Next, I could scour the hard drives for evidence, but unless I pull the drives, I will have to do that when Unraid is running, which would negate any evidence, so that's a non-starter.

 

I dont understand your comment about simpleFeatures working until Limetech upgraded the gui.  The simpleFeatures page does not mention this.  Does this mean that it is broken now?  Is there any way to downgrade the Limetch gui?  Is this recommended?

 

My problems with simpleTech started with this: http://lime-technology.com/forum/index.php?topic=29972.msg269371#msg269371.  I did so searching and found this:  http://lime-technology.com/forum/index.php?topic=12698.msg267509;topicseen#msg267509.  I edited the .plg file as noted and the time zone error disappeared.  But then I started getting email messages fomr the cosole "cron for user root /usr/lib/sa/sa1 2 1 & >/dev/null"  saying "Cannot write data to system activity file: No space left on device".  Soon after the web gui was unresponsive and I had to power down from the console.  Thinking this was due to the now-fixed web server, I disabled simpleFeatures.web.server-1.0.11-noarch-1.plg.  This is when I started noticing other anomalies.  Like the syslog having that sequence of "unRAID driver removed" then "unRAID drive installed" over and over.  This may have been coincidental, though.

 

Anyway, I think you can see why I dont have much trust in simpleFeatures.  And I really dont need them anyway.  I have been quite happy to run 4.7 for years.  I use the array for my backup target machine and to store media.  I also run mySQL for XBMC.  I would not mind moving my logitech media server (for my Squeezebox) onto the server, but that is not a high priority.  I just wanted to expand my capacity and 3 TB drives are the sweet spot now, hence the need for 5.0.  Otherwise, I am very much "if ain't broke, dont fix it".

 

BTW, what is "teamviewer"?  Is this some sort of remote login thing?  That could be fun.  How is this done?

[Influencer]

Since 5.0 there have been issues between SF and unraid, mainly (and possibly only) if the user upgraded to limetech's webgui. Its an optional step that you would have had to select to upgrade (I think its on the settings page?). If you upgraded you can downgrade by removing the webgui plug-in and package from /boot/plugins/ (which you don't have so its safe to say you didn't do).

 

It means parts of Sf are not working, which are of no fault to the SF dev(s).

 

I can see how you don't have much trust in SF, and to each their own. I've never ran most of the extensions for Sf myself but have used it for quite a while now with no hiccups. Sf did a lot with very little adding a lot of functionality to the webgui, but is done in spare time so sometimes there are bugs that aren't squashed immediately.

 

Teamviewer is a remote login type of application, basically you can download an executable that you do not have to install, run it and it will give you a unique access ID and pin number. You give the other person this information and they can access your desktop. Once you are done (you retain control of the system during this), you can exit out of the application and the next time you open it up the access ID is the same but the pin is different, so even if I've remote accessed your pc before, I can't do it again.

 

Teamviewer is also handy if you have not-so-technologically inclined family members or friends. I have Teamviewer installed on my parents PC as well as my wifes and sons, it starts when the pc does and I can access their pc from mine or even from my phone, making fixing something for them very quick. Of course they can always shut down the application and run it when they need help.