Squid Posted December 10, 2016 Author Share Posted December 10, 2016 Added in a check for NerdPack installing inotify-tools on unRaid 6.3.0-rc6+ (its now included in the base OS - having NerdPack install it could potentially introduce dependency problems) Quote Link to comment
adyy48 Posted December 12, 2016 Share Posted December 12, 2016 Hello, I can't update the plug in to the latest version, "Update Available. Click Here to Install" does nothin from the apps, i have also tried uninstalling or install it traditional way with the url. Does anyone know how to fix it? when uninstalling i get this message: plugin: removing: fix.common.problems.plg Warning: simplexml_load_file(): /boot/config/plugins/fix.common.problems.plg:8: parser error : Input is not proper UTF-8, indicate encoding ! Bytes: 0xF0 0x2F 0x70 0x6C in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): /boot/config/plugins/fix.common.problems.plg:13: parser error : Entity 'pluginURL' not defined in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): " author="&author;" version="&version;" launch="&launch;" pluginURL="&pluginURL; in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): /boot/config/plugins/fix.common.problems.plg:162: parser error : Entity 'github' not defined in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): https://raw.github.com/&github;/master/archive/&name;-&version;-x86_64-1.tx in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 plugin: xml parse error Thank you! Quote Link to comment
Squid Posted December 12, 2016 Author Share Posted December 12, 2016 Hello, I can't update the plug in to the latest version, "Update Available. Click Here to Install" does nothin from the apps, i have also tried uninstalling or install it traditional way with the url. Does anyone know how to fix it? when uninstalling i get this message: plugin: removing: fix.common.problems.plg Warning: simplexml_load_file(): /boot/config/plugins/fix.common.problems.plg:8: parser error : Input is not proper UTF-8, indicate encoding ! Bytes: 0xF0 0x2F 0x70 0x6C in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): /boot/config/plugins/fix.common.problems.plg:13: parser error : Entity 'pluginURL' not defined in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): " author="&author;" version="&version;" launch="&launch;" pluginURL="&pluginURL; in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): /boot/config/plugins/fix.common.problems.plg:162: parser error : Entity 'github' not defined in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): https://raw.github.com/&github;/master/archive/&name;-&version;-x86_64-1.tx in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 plugin: xml parse error Thank you! Sounds like you've gotten a bad download somehow. Easiest way to fix is to delete /config/plugins/fix.common.problems.plg from the flash drive and reboot. Then reinstall it via the Apps Tab, CA Modules. Just tried reinstalling, and there's no problem with the .plg file Quote Link to comment
adyy48 Posted December 12, 2016 Share Posted December 12, 2016 Hello, I can't update the plug in to the latest version, "Update Available. Click Here to Install" does nothin from the apps, i have also tried uninstalling or install it traditional way with the url. Does anyone know how to fix it? when uninstalling i get this message: plugin: removing: fix.common.problems.plg Warning: simplexml_load_file(): /boot/config/plugins/fix.common.problems.plg:8: parser error : Input is not proper UTF-8, indicate encoding ! Bytes: 0xF0 0x2F 0x70 0x6C in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): /boot/config/plugins/fix.common.problems.plg:13: parser error : Entity 'pluginURL' not defined in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): " author="&author;" version="&version;" launch="&launch;" pluginURL="&pluginURL; in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): /boot/config/plugins/fix.common.problems.plg:162: parser error : Entity 'github' not defined in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): https://raw.github.com/&github;/master/archive/&name;-&version;-x86_64-1.tx in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 plugin: xml parse error Thank you! Sounds like you've gotten a bad download somehow. Easiest way to fix is to delete /config/plugins/fix.common.problems.plg from the flash drive and reboot. Then reinstall it via the Apps Tab, CA Modules. Just tried reinstalling, and there's no problem with the .plg file Thank's for your reply, i tried deleting the plugin from: /boot/config/plugins/ /usr/local/emhttp/plugins/dynamix.plugin.manager/ Now i am left with this error when i try to install: "plugin: installing: https://raw.githubusercontent.com/Squidly271/fix.common.problems/master/plugins/fix.common.problems.plg plugin: downloading https://raw.githubusercontent.com/Squidly271/fix.common.problems/master/plugins/fix.common.problems.plg plugin: downloading: https://raw.githubusercontent.com/Squidly271/fix.common.problems/master/plugins/fix.common.problems.plg ... done Warning: simplexml_load_file(): I/O warning : failed to load external entity "/boot/config/plugins/fix.common.problems.plg" in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 plugin: xml parse error" There is nothin left in /boot/... or /usr/... Any idea how to deal with it? Thank's for the support! Quote Link to comment
Squid Posted December 12, 2016 Author Share Posted December 12, 2016 Did you reboot after deleting the .plg? Quote Link to comment
adyy48 Posted December 12, 2016 Share Posted December 12, 2016 No, try it right now... That was it!!! Thankyou, apreciate your help! Quote Link to comment
Squid Posted December 17, 2016 Author Share Posted December 17, 2016 Added in to troubleshooting mode the output of sensors every 10 minutes to further assist in diagnosis. Your mileage will vary as to what sensors and information are present. I *highly* recommend to install the Dynamix System Temp plugin and load any/all drivers with it. Once that is setup, you will hopefully get an output similar to this: root@Server_A:/tmp/GitHub/fix.common.problems# sensors -A k10temp-pci-00c3 MB Temp: +0.6°C (high = +70.0°C) (crit = +80.0°C, hyst = +79.0°C) nct6791-isa-0290 Vcore: +0.90 V (min = +0.00 V, max = +1.74 V) in1: +1.00 V (min = +0.00 V, max = +0.00 V) ALARM AVCC: +3.36 V (min = +0.00 V, max = +0.00 V) ALARM +3.3V: +3.36 V (min = +0.00 V, max = +0.00 V) ALARM in4: +1.01 V (min = +0.00 V, max = +0.00 V) ALARM in5: +2.04 V (min = +0.00 V, max = +0.00 V) ALARM in6: +0.28 V (min = +0.00 V, max = +0.00 V) ALARM 3VSB: +3.34 V (min = +0.00 V, max = +0.00 V) ALARM Vbat: +3.30 V (min = +0.00 V, max = +0.00 V) ALARM in9: +0.00 V (min = +0.00 V, max = +0.00 V) in10: +0.16 V (min = +0.00 V, max = +0.00 V) ALARM in11: +0.17 V (min = +0.00 V, max = +0.00 V) ALARM in12: +1.01 V (min = +0.00 V, max = +0.00 V) ALARM in13: +1.00 V (min = +0.00 V, max = +0.00 V) ALARM in14: +0.21 V (min = +0.00 V, max = +0.00 V) ALARM Array Fan: 3146 RPM (min = 0 RPM) SYSTIN: +24.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor CPU Temp: +33.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor AUXTIN0: +108.0°C sensor = thermistor AUXTIN1: +106.0°C sensor = thermistor AUXTIN2: +105.0°C sensor = thermistor AUXTIN3: +106.0°C sensor = thermistor intrusion0: ALARM intrusion1: ALARM beep_enable: disabled Depending upon the sensors in your system, you may see even more items (or less). Either way, a useful addition in diagnosing random crashes, etc to see how the voltages / temperatures / fans are running in your system leading up to the crash. Quote Link to comment
tr0910 Posted December 25, 2016 Share Posted December 25, 2016 ipmitool is giving a false positive The plugin powerdown-x86_64.plg is not known to Community Applications and is possibly incompatible with your server https://lime-technology.com/forum/index.php?topic=42507.0 Quote Link to comment
Squid Posted December 25, 2016 Author Share Posted December 25, 2016 That's powerdown giving the warning. And its valid Sent from my LG-D852 using Tapatalk Quote Link to comment
bpage Posted January 9, 2017 Share Posted January 9, 2017 Is there anyway to get the full file path of an error? I had an error show up: "Unable to write to nextcloud.log" But have no idea how to solve it. All drives are working correctly. And I uninstalled nextcloud. Is there anyway to see the full file path of this file so I can delete it? thanks! Brian Quote Link to comment
Squid Posted January 9, 2017 Author Share Posted January 9, 2017 Is there anyway to get the full file path of an error? I had an error show up: "Unable to write to nextcloud.log" But have no idea how to solve it. All drives are working correctly. And I uninstalled nextcloud. Is there anyway to see the full file path of this file so I can delete it? thanks! Brian That's strange. Been quite a while since I've looked at that part of the code, but IIRC I attempt to write a randomly named file to the root of each disk. Those three errors *imply* that somehow you've created files / folders within /mnt inadvertently. Since next cloud isn't running (or nginx / apache), a reboot should solve the problem. But, nothing should ever get created by a docker in /mnt unless you've got the template misconfigured. But I'll look at the code tonight and confirm. Quote Link to comment
bpage Posted January 9, 2017 Share Posted January 9, 2017 Thanks Squid. There in /mnt. Not sure how I managed to do that. All fixed now. Thanks for the help! Quote Link to comment
Squid Posted January 9, 2017 Author Share Posted January 9, 2017 Thanks Squid. There in /mnt. Not sure how I managed to do that. All fixed now. Thanks for the help! If nothing else, you managed to prove that FCP's tests are flexible enough to come up with problems that I never even considered to be possible. Kudos! Quote Link to comment
bpage Posted January 9, 2017 Share Posted January 9, 2017 I do my best! Plugin works great! Quote Link to comment
Excessus Posted January 14, 2017 Share Posted January 14, 2017 I have been have a lot of problems with my unRAID build (see here if interested) so I ran the Extended Test on my system. Unfortunately, since I have about 1TB of stuff in lost+found I can't view the log in the browser since it's so big that it causes the browser to crash. I assume that it's stored somewhere on the disk and I'd like to view it from the console. Any idea where I can find it? Quote Link to comment
Squid Posted January 14, 2017 Author Share Posted January 14, 2017 I have been have a lot of problems with my unRAID build (see here if interested) so I ran the Extended Test on my system. Unfortunately, since I have about 1TB of stuff in lost+found I can't view the log in the browser since it's so big that it causes the browser to crash. I assume that it's stored somewhere on the disk and I'd like to view it from the console. Any idea where I can find it? Not quite following. How did you run the extended test. What log are you talking about? If its the syslog, and it crashes the system trying to display it, then run diagnostics and open the syslog from the zip file Quote Link to comment
trurl Posted January 14, 2017 Share Posted January 14, 2017 I have been have a lot of problems with my unRAID build (see here if interested) so I ran the Extended Test on my system. Unfortunately, since I have about 1TB of stuff in lost+found I can't view the log in the browser since it's so big that it causes the browser to crash. I assume that it's stored somewhere on the disk and I'd like to view it from the console. Any idea where I can find it? Not quite following. How did you run the extended test. What log are you talking about? If its the syslog, and it crashes the system trying to display it, then run diagnostics and open the syslog from the zip file Better yet post your diagnostics. Quote Link to comment
WannabeMKII Posted January 18, 2017 Share Posted January 18, 2017 Just after a bit of help with regards to problem being reported by this plugin. The following files / folders may not be accessible to the users allowed via each Share's SMB settings. This is often caused by wrong permissions being used on new downloads / copies by CouchPotato, Sonarr, and the like: The folders in question are the files created from the backup of appdata of Couchpotato using 'CA Backup / Restore Appdata' and state 'nobody/users (99/100) 0600'. Sonarr seems OK. This will also explain why CrashPlan is unable to backup the 'backup'. Why is this happen and how do I resolve? Quote Link to comment
Squid Posted January 19, 2017 Author Share Posted January 19, 2017 Just after a bit of help with regards to problem being reported by this plugin. The following files / folders may not be accessible to the users allowed via each Share's SMB settings. This is often caused by wrong permissions being used on new downloads / copies by CouchPotato, Sonarr, and the like: The folders in question are the files created from the backup of appdata of Couchpotato using 'CA Backup / Restore Appdata' and state 'nobody/users (99/100) 0600'. Sonarr seems OK. This will also explain why CrashPlan is unable to backup the 'backup'. Why is this happen and how do I resolve? If this is from the regular scans (not extended), then it sounds like your default appdata destination might not match what you've set for CrashPlan. (FCP tries to avoid giving errors on permissions for appdata because of the wildly varying permissions that are contained within) No guarantees on what would happen if you fix the permissions on Crashplan. You might make it completely inoperable if you attempt fixes. Quote Link to comment
WannabeMKII Posted January 19, 2017 Share Posted January 19, 2017 Just after a bit of help with regards to problem being reported by this plugin. The following files / folders may not be accessible to the users allowed via each Share's SMB settings. This is often caused by wrong permissions being used on new downloads / copies by CouchPotato, Sonarr, and the like: The folders in question are the files created from the backup of appdata of Couchpotato using 'CA Backup / Restore Appdata' and state 'nobody/users (99/100) 0600'. Sonarr seems OK. This will also explain why CrashPlan is unable to backup the 'backup'. Why is this happen and how do I resolve? If this is from the regular scans (not extended), then it sounds like your default appdata destination might not match what you've set for CrashPlan. (FCP tries to avoid giving errors on permissions for appdata because of the wildly varying permissions that are contained within) This is from an extended scan. The regular scan is reporting no issues. No guarantees on what would happen if you fix the permissions on Crashplan. You might make it completely inoperable if you attempt fixes. Well, CrashPlan isn't actually running on unraid, it's running on a different machine, a machine that does have read / write access to the backup share. What would you recommend? Quote Link to comment
hgeorges Posted January 22, 2017 Share Posted January 22, 2017 Hello, Thank you for sharing this application with the unraid community. I recently added your plugin to my unraid server. I'm reporting a couple of issues, and I have a couple of questions. 1) false positives Ignored Errors & Warnings Suggested Fix Docker Application tvheadend is currently set up to run in host mode The template for this application specifies that the application should run in bridge mode. For your reference this link: https://hub.docker.com/r/linuxserver/tvheadend/ "Host vs. Bridge If you use IPTV, SAT>IP or HDHomeRun, you need to create the container with --net=host and remove the -p flags. This is because of a limitation in docker and multicast." --------------------- Docker Application tvheadend, Container Port 9981 not found or changed on installed application When changing ports on a docker container, you should only ever modify the HOST port, as the application in question will expect the container port to remain the same as what the template author dictated. Fix this here: Application Support Thread Docker Application tvheadend, Container Port 9982 not found or changed on installed application When changing ports on a docker container, you should only ever modify the HOST port, as the application in question will expect the container port to remain the same as what the template author dictated. Fix this here: Application ------------------- Both lines are unjustified. I reinstalled tvheadend several times, and from a couple of sources, on this site. But the ports are the same. And I have tvheadend installed, but stopped. It has not been running for weeks. My questions : 1) is the program checking for a change of state in the previously identified state, and should that have happened, are the warnings/errors removed? If that is not the program behavior, is there any possibility to add a remove/hide option, so that messages which are not necessary should not be displayed. 2) I realize that is a matter of personal choice (I read your answer in the beginning of the thread) - but there is a semantic difference between an error and a warning. Seeing error messages I have two conscious choices to make, to go and check them each time, since an error must be treated with urgency, or, knowing that an error might not be exactly an error, I can choose to ignore it. (Remember Unraid is sending email notifications for various reasons, errors being one of them, and FCP is not the solely application generating notifications. There are other subsystems on unraid which can generate real errors). Desensitizing me to errors is the undesired effect of sending error messages when there are none. The same notion with "Crying wolf" if you want... That's it. Thanks for reviewing my reply. hg Quote Link to comment
trurl Posted January 22, 2017 Share Posted January 22, 2017 is there any possibility to add a remove/hide option, so that messages which are not necessary should not be displayed. This feature already exists. Quote Link to comment
Squid Posted January 22, 2017 Author Share Posted January 22, 2017 As stated, the ability to ignore warnings / errors (and you're correct that its purely semantics the difference between the two, and ultimately its what I think) has been implemented for a very long time. "False Positives" - Depending upon your viewpoint, any "false positives" are either valid or invalid. My opinion is that any and all errors / warnings are valid, but there may also be perfectly acceptable reasons to set up the server in such a way as to trigger those warnings. (I myself on my server have a number of warnings set to be ignored) Ultimately, FCP is designed around two philosophies: - How I think unRaid should get set up - What tends to trip people up. The host vs port thing does tend to trip up many people. But, if nothing else, at least the warning did force you to actually search out the postings that stated that this was ok to do under certain circumstances. It is not feasable for myself to include exceptions for any of the valid reasons to change any of the settings that may trigger a warning/error and then try and figure out - Did the user actually make a mistake? or - Is this what they actually want / need? In a nutshell, all the errors / warnings as set will stand as is. If/when errors / warnings on a general basis are proved to be false posisitives consistently then they will be removed and/or modified accordingly. (And this has happened previously with one test in particular) TLDR: It doesn't bother me in the least if yourself or anyone ignores any/all errors if you know what you're doing. Quote Link to comment
RobJ Posted January 22, 2017 Share Posted January 22, 2017 It works well enough as it is, and it's obviously not a big issue, but I suspect some of us would be happier if we had a way to suppress the ignored messages going to the syslog. Perhaps when you have time for a minor enhancement, you could add an option to suppress them even from the syslog, then add a view option to see the last set of ignored messages. So when you run a scan, send the messages either to the syslog or to an internal buffer, which can be viewed on button push ("Display ignored messages"). Quote Link to comment
Squid Posted January 22, 2017 Author Share Posted January 22, 2017 It works well enough as it is, and it's obviously not a big issue, but I suspect some of us would be happier if we had a way to suppress the ignored messages going to the syslog. Perhaps when you have time for a minor enhancement, you could add an option to suppress them even from the syslog, then add a view option to see the last set of ignored messages. So when you run a scan, send the messages either to the syslog or to an internal buffer, which can be viewed on button push ("Display ignored messages"). All it does is log that ignored errors were found. This was so that if in the event diagnostics were getting uploaded whomever was looking at it would see that the user has ignored something. On the GUI, any errors which are ignored (but found again) do appear on the ignored list Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.