sojab0on Posted January 18, 2019 Share Posted January 18, 2019 My CA wont load the feeds anymore reinstalled the plugin but wont do it, i can find a plg link for the fix common problems does some one have it? Quote Link to comment
unsainted Posted January 31, 2019 Share Posted January 31, 2019 I posted this in General support but then realized its part of this plugin.. Any ideas? Quote Link to comment
trurl Posted January 31, 2019 Share Posted January 31, 2019 1 hour ago, unsainted said: I posted this in General support but then realized its part of this plugin.. Any ideas? Squid, the author of this plugin, has already commented in your other thread. Quote Link to comment
rctneil Posted February 2, 2019 Share Posted February 2, 2019 (edited) @Squid I'm running 6.7rc2 which may be the issue, Each time I try to install FCP, I get this log: 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 +============================================================================== | Installing new package /boot/config/plugins/fix.common.problems/fix.common.problems-2019.01.19-x86_64-1.txz +============================================================================== Verifying package fix.common.problems-2019.01.19-x86_64-1.txz. Unable to install /boot/config/plugins/fix.common.problems/fix.common.problems-2019.01.19-x86_64-1.txz: tar archive is corrupt (tar returned error code 2) ---------------------------------------------------- fix.common.problems has been installed. Copyright 2016, Andrew Zawadzki Version: 2019.01.19 ---------------------------------------------------- plugin: installed It looks like it's installed but there's no actual page for it. Any ideas? Edited February 2, 2019 by rctneil Quote Link to comment
Squid Posted February 2, 2019 Author Share Posted February 2, 2019 30 minutes ago, rctneil said: tar archive is corrupt It's not installed. I just tried a reinstall on my system, and there's no problem. Maybe try a reboot. Quote Link to comment
rctneil Posted February 2, 2019 Share Posted February 2, 2019 7 minutes ago, Squid said: It's not installed. I just tried a reinstall on my system, and there's no problem. Maybe try a reboot. Thanks, I realise it wasn't actually installed. I meant to emphasise the fact that it "looks" like it is installed as it shows up in the list of installed plugins etc. I have rebooted the system several times since 6.7rc2 was installed but it's still happening. Any ideas as to how I can get this working? Is there a local copy of the plugin somewhere that's corrupted that needs removing or something else? Quote Link to comment
Squid Posted February 2, 2019 Author Share Posted February 2, 2019 1 hour ago, rctneil said: /config/plugins/fix.common.problems/fix.common.problems-2019.01.19-x86_64-1.txz delete that file on the flash drive Quote Link to comment
rctneil Posted February 2, 2019 Share Posted February 2, 2019 8 minutes ago, Squid said: delete that file on the flash drive Thankyou so much. That fixed it. Quote Link to comment
geekazoid Posted February 7, 2019 Share Posted February 7, 2019 (edited) For the past week, this plugin has been hanging on my system. Sometimes, it eventually times out and no results are found. It appears that the daily background check isn't running either. This behavior persists across reboots. I've also removed the plugin and reinstalled, same condition. Edited February 7, 2019 by geekazoid Quote Link to comment
wgstarks Posted February 9, 2019 Share Posted February 9, 2019 FCP is generating an erroneous report regarding Now Showing V2 docker- Now Showing v1 was deprecated, not v2. Not sure if this is an error in a template by @ninthwalker or an error with FCP? This just started for me when I installed RC3 but I believe I saw a report in the docker's support thread about someone getting the same error in RC2. brunnhilde-diagnostics-20190209-1844.zip Quote Link to comment
dockerPolice Posted February 10, 2019 Share Posted February 10, 2019 1 hour ago, wgstarks said: FCP is generating an erroneous report regarding Now Showing V2 docker- Now Showing v1 was deprecated, not v2. Not sure if this is an error in a template by @ninthwalker or an error with FCP? This just started for me when I installed RC3 but I believe I saw a report in the docker's support thread about someone getting the same error in RC2. brunnhilde-diagnostics-20190209-1844.zip Ok I see now that they are the same repo, just different tags will rectify Quote Link to comment
apazzy Posted February 10, 2019 Share Posted February 10, 2019 Would it be possible to increase the frequency of troubleshooting mode captures? Quote Link to comment
juan11perez Posted February 14, 2019 Share Posted February 14, 2019 First thank you for the plugin. Running Unraid Version 6.7.0-rc3 2019-02-09 When scanning I get the following plugin error: Warning: simplexml_load_file(): I/O warning : failed to load external entity "" in /usr/local/emhttp/plugins/fix.common.problems/include/tests.php on line 1563 Warning: simplexml_load_file(): I/O warning : failed to load external entity "" in /usr/local/emhttp/plugins/fix.common.problems/include/tests.php on line 1563 Warning: simplexml_load_file(): I/O warning : failed to load external entity "" in /usr/local/emhttp/plugins/fix.common.problems/include/tests.php on line 1563 Warning: simplexml_load_file(): I/O warning : failed to load external entity "" in /usr/local/emhttp/plugins/fix.common.problems/include/tests.php on line 1563 Warning: simplexml_load_file(): I/O warning : failed to load external entity "" in /usr/local/emhttp/plugins/fix.common.problems/include/tests.php on line 1563 Warning: simplexml_load_file(): I/O warning : failed to load external entity "" in /usr/local/emhttp/plugins/fix.common.problems/include/tests.php on line 1563 ERRORS FOUNDSUGGESTED FIX I have no system errors. Quote Link to comment
Squid Posted February 16, 2019 Author Share Posted February 16, 2019 On 2/14/2019 at 1:39 AM, juan11perez said: First thank you for the plugin. Running Unraid Version 6.7.0-rc3 2019-02-09 When scanning I get the following plugin error: Probably fixed on today's update. But, it's a corrupted XML file. A new test will show which one. Quote Link to comment
Squid Posted February 16, 2019 Author Share Posted February 16, 2019 FYI @all Troubleshooting mode is now deprecated when running unRaid 6.7+ and the button will no longer appear 1 Quote Link to comment
geekazoid Posted February 17, 2019 Share Posted February 17, 2019 On 2/7/2019 at 9:08 AM, geekazoid said: this plugin has been hanging on my system FCP is still hanging after update. Squid? Quote Link to comment
Squid Posted February 17, 2019 Author Share Posted February 17, 2019 Get it to hang again then post your diagnostics Quote Link to comment
geekazoid Posted February 17, 2019 Share Posted February 17, 2019 13 hours ago, Squid said: Get it to hang again then post your diagnostics There isn't much in here about FCP. I've tailed every log I could find. fluffy-diagnostics-20190217-1051.zip Quote Link to comment
Squid Posted February 17, 2019 Author Share Posted February 17, 2019 ok Saw what I wanted (and expected to see). Do this cp /tmp/fix.common.problems/errors.txt /boot/errors.txt And upload here errors.txt and /config/plugins/fix.common.problems/settings.json from the flash drive Quote Link to comment
geekazoid Posted February 17, 2019 Share Posted February 17, 2019 4 hours ago, Squid said: upload here errors.txt and /config/plugins/fix.common.problems/settings.json from the flash drive If there are no errors in the list, the script runs automatically when you access https://<unraid>/Settings/FixProblems. I watch for this process: /usr/bin/php /usr/local/emhttp/plugins/fix.common.problems/scripts/scan.php 1 I moved some files from the cache recently which triggers an error in FCP. This actually helps me see what's going on. In /tmp/fix.common.problems/: errors.txt is generated 3mins after execution. The moderations and templates files timestamps are also updated. Watching process: scan.php closes in 4-5mins however the web page does not update, so the splash remains indefinitely. Refresh page after script is complete and its normal (not scanning again). This is new behavior today./tmp/fix.common.problems/errors.txt becomes errors.json after execution of the script. See below. Not very exciting. Contents of errors.json: { "errors": [ { "error": "<font color='red'><b>Default docker appdata</b> location is not a cache-only share</font>", "suggestion": "If the appdata share is not set to be cache-only, then the mover program will cause your docker applications to become inoperable when it runs (6.1.x). Under 6.2+, this setting should not affect the operation of the application, but it will definitely impact significantly the performance of the application. Fix it via <input type='button' value='appdata Settings' onclick='window.location.href="/Shares/Share?name=appdata"'>" } ], "warnings": null, "other": null, "ignored": null } Contents of settings.json: { "frequency": "daily", "notifications": "all", "disableSpinUp": "false", "hacksPerDay": "3", "logIgnored": "yes", "excludedPerms": "" } Quote Link to comment
Squid Posted February 17, 2019 Author Share Posted February 17, 2019 8 minutes ago, geekazoid said: 3mins And that's the problem. 120 seconds is the maximum time unRaid allows for something to execute using the process I am. Some year I'm going to change how this all works. 9 minutes ago, geekazoid said: "disableSpinUp": "false", Changing FCP to avoid disk spinups will probably fix you up. Quote Link to comment
juan11perez Posted February 18, 2019 Share Posted February 18, 2019 On 2/17/2019 at 3:41 AM, Squid said: Probably fixed on today's update. But, it's a corrupted XML file. A new test will show which one. Thank you. I confirm the release fixes the error for me. Quote Link to comment
geekazoid Posted February 18, 2019 Share Posted February 18, 2019 20 hours ago, Squid said: Changing FCP to avoid disk spinups will probably fix you up. Tried that, no change. The problem seems to be the scan.php not running in a timely fashion (it used to run for less than a minute) and not refreshing the page by clearing the 'scanning' splash. Other than that it seems to be working. But this behavior is an irritating change from the norm. Quote Link to comment
noja Posted February 19, 2019 Share Posted February 19, 2019 Runnin 6.6.6 - getting this error on trying to update FCP plugin: updating: fix.common.problems.plg plugin: downloading: https://raw.github.com/Squidly271/fix.common.problems/master/archive/fix.common.problems-2019.02.18-x86_64-1.txz ... failed (Invalid URL / Server error response) plugin: wget: https://raw.github.com/Squidly271/fix.common.problems/master/archive/fix.common.problems-2019.02.18-x86_64-1.txz download failure (Invalid URL / Server error response) Is this one of those updates that will only work on 6.7 RCxx or did I do something else wrong? Thanks! Quote Link to comment
trurl Posted February 19, 2019 Share Posted February 19, 2019 4 minutes ago, noja said: Runnin 6.6.6 - getting this error on trying to update FCP Probably your server is having a problem reaching the internet. Can you ping github from your server? 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.