Squid Posted February 6, 2017 Author Share Posted February 6, 2017 I think of it as an error because at that point plugins and Dockers won't install. No update checks will work etc. It's not a check on github per se but a check against internet access as a whole Sent from my LG-D852 using Tapatalk I've got this exact same problem. What would cause this error to appear? This error message is causing all my docker and plugin updates to fail yet I can get to github.com without a problem on my PC. Usually Going to network settings, and making sure the default gateway points to your router and setting static DNS addresses of 8.8.8.8 and 8.8.4.4 will fix you up Quote Link to comment
Bigdady92 Posted February 6, 2017 Share Posted February 6, 2017 I think of it as an error because at that point plugins and Dockers won't install. No update checks will work etc. It's not a check on github per se but a check against internet access as a whole Sent from my LG-D852 using Tapatalk I've got this exact same problem. What would cause this error to appear? This error message is causing all my docker and plugin updates to fail yet I can get to github.com without a problem on my PC. Usually Going to network settings, and making sure the default gateway points to your router and setting static DNS addresses of 8.8.8.8 and 8.8.4.4 will fix you up I set google's DNS to be my 2nd/3rd DNS left my router as 1st when I thought that was the problem. I'll revise the order and see if that helps. I'll be mega irritated if it's that simple. Quote Link to comment
olympia Posted February 7, 2017 Share Posted February 7, 2017 Is it possible to find/ view/ copy the results of the extended tests from the file system? I have a huge log with dupes and it is difficult to process it based on the "view results" window from the GUI. I presume these results should be saved somewhere? However, I cannot locate it. Quote Link to comment
t33j4y Posted February 12, 2017 Share Posted February 12, 2017 After upgrading to unRaid 6.3, Fix Common Problems throws a warning: "inotify-tools set to install - inotify-tools is set to be installed by the NerdPack plugin. This package is now included in unRaid 6.3RC6+, and NerdPack should be set to not install it." The issue is that when I go to NerdTools to uncheck "inotify-tools" it isn't there at all. I have the following versions running: * Fix Common Problems version: 2017.02.03b * NerdTools version: 2017.02.06 Altthough I can't find evidence of it in the release notes, I figure that NerdTools has already build in check for unRaid version and removed install option for inotify-tools if it senses 6.3 RC6 or later. Perhaps you can update Fix Common problems to handle accordingly? Thank you for a great plugin! Quote Link to comment
trurl Posted February 12, 2017 Share Posted February 12, 2017 After upgrading to unRaid 6.3, Fix Common Problems throws a warning: "inotify-tools set to install - inotify-tools is set to be installed by the NerdPack plugin. This package is now included in unRaid 6.3RC6+, and NerdPack should be set to not install it." The issue is that when I go to NerdTools to uncheck "inotify-tools" it isn't there at all. I have the following versions running: * Fix Common Problems version: 2017.02.03b * NerdTools version: 2017.02.06 Altthough I can't find evidence of it in the release notes, I figure that NerdTools has already build in check for unRaid version and removed install option for inotify-tools if it senses 6.3 RC6 or later. Perhaps you can update Fix Common problems to handle accordingly? Thank you for a great plugin! See the Nerdpack sticky starting here Quote Link to comment
t33j4y Posted February 12, 2017 Share Posted February 12, 2017 Thanks trurl - that fixed it :-) Quote Link to comment
neurocis Posted February 13, 2017 Share Posted February 13, 2017 Just updated to 6.3.1 and now receiving: Feb 12 20:09:43 QUAZAR root: error: plugins/fix.common.problems/include/fixExec.php: wrong csrf_token And FCP will not scan, just gives above error. Has anybody else seen this? Thanks. Quote Link to comment
Squid Posted February 13, 2017 Author Share Posted February 13, 2017 Odds on you've got an open browser session from before the boot still running. Sent from my SM-T560NU using Tapatalk Quote Link to comment
neurocis Posted February 13, 2017 Share Posted February 13, 2017 Odds on you've got an open browser session from before the boot still running. Sent from my SM-T560NU using Tapatalk Ding Ding, we have a winner, that appears to exactly have been the case for that issue, now a new issue: Warning: basename() expects parameter 1 to be string, array given in /usr/local/emhttp/plugins/fix.common.problems/include/tests.php on line 837 when accessing FCP via Settings just above the "Errors Found" section. Cheers! Quote Link to comment
Gico Posted February 13, 2017 Share Posted February 13, 2017 Odds on you've got an open browser session from before the boot still running. Sent from my SM-T560NU using Tapatalk Ding Ding, we have a winner, that appears to exactly have been the case for that issue, now a new issue: Warning: basename() expects parameter 1 to be string, array given in /usr/local/emhttp/plugins/fix.common.problems/include/tests.php on line 837 when accessing FCP via Settings just above the "Errors Found" section. Cheers! Same here, right after 6.3.1 upgrade. Restarted (Chrome) browser and still having this warning. Quote Link to comment
Squid Posted February 13, 2017 Author Share Posted February 13, 2017 Odds on you've got an open browser session from before the boot still running. Sent from my SM-T560NU using Tapatalk Ding Ding, we have a winner, that appears to exactly have been the case for that issue, now a new issue: Warning: basename() expects parameter 1 to be string, array given in /usr/local/emhttp/plugins/fix.common.problems/include/tests.php on line 837 when accessing FCP via Settings just above the "Errors Found" section. Cheers! Same here, right after 6.3.1 upgrade. Restarted (Chrome) browser and still having this warning. That's going to be related to the template errors that neccessitated an update to CA. I'll fix tonight Quote Link to comment
luca2 Posted February 13, 2017 Share Posted February 13, 2017 Hi, I get this error Warning: basename() expects parameter 1 to be string, array given in /usr/local/emhttp/plugins/fix.common.problems/include/tests.php on line 837 after only changing this in Unraid: -installing Tips and Tweaks (did change the following: Disable NIC Flow Control?: yes Disable NIC Offload?: yes Disk Cache 'vm.dirty_background_ratio' (%): 5 Disk Cache 'vm.dirty_ratio (%): 10 Disable FTP Server & Telnet?: yes -adding to my syslinux: isolcpus=2,3,6,7 My server keeps running, just want to make sure waht can cause this. I posted here: https://lime-technology.com/forum/index.php?topic=56527.msg539414#msg539414 also another error I got when re-starting the server. Today after running fix common problems I got the first error I described at the beginning of this post. Rgds. Quote Link to comment
saarg Posted February 13, 2017 Share Posted February 13, 2017 Hi, I get this error Warning: basename() expects parameter 1 to be string, array given in /usr/local/emhttp/plugins/fix.common.problems/include/tests.php on line 837 after only changing this in Unraid: -installing Tips and Tweaks (did change the following: Disable NIC Flow Control?: yes Disable NIC Offload?: yes Disk Cache 'vm.dirty_background_ratio' (%): 5 Disk Cache 'vm.dirty_ratio (%): 10 Disable FTP Server & Telnet?: yes -adding to my syslinux: isolcpus=2,3,6,7 My server keeps running, just want to make sure waht can cause this. I posted here: https://lime-technology.com/forum/index.php?topic=56527.msg539414#msg539414 also another error I got when re-starting the server. Today after running fix common problems I got the first error I described at the beginning of this post. Rgds. Look at the post above yours.... Quote Link to comment
luca2 Posted February 13, 2017 Share Posted February 13, 2017 If I understand what is posted before, if I reboot the array and also my laptop it should be gone, rigth? Not my case. EDIT: I just started Tips and Tweaks and my screen (gpu out of Unraid) shows this message: grep: /etc/php-fpm.d/www.conf: no such file or direct If I change anything in this plugin, after clicking Apply I get the same message. Quote Link to comment
saarg Posted February 13, 2017 Share Posted February 13, 2017 If I understand what is posted before, if I reboot the array and also my laptop it should be gone, rigth? Not my case. EDIT: I just started Tips and Tweaks and my screen (gpu out of Unraid) shows this message: grep: /etc/php-fpm.d/www.conf: no such file or direct If I change anything in this plugin, after clicking Apply I get the same message. Doesn't squid say he will fix the problem? Quote Link to comment
luca2 Posted February 13, 2017 Share Posted February 13, 2017 Sorry Did miss this line! Quote Link to comment
saarg Posted February 13, 2017 Share Posted February 13, 2017 Sorry Did miss this line! Go sit in the corner for 15 minutes Quote Link to comment
phorse Posted February 13, 2017 Share Posted February 13, 2017 I updated to 6.3.1 today and am getting this warning when scanning for errors, but does not detect any errors and otherwise seems to be working OK. Any ideas? Plugins Installed: CA Auto Update Applications, CA Backup/Restore Appdata, CA Cleanup Appdata, Community Applications, Dynamix Active Streams, Dynamix Cache Directories, Dynamix S3 Sleep, Dynamix System Buttons, Dynamix System Information, Dynamix System Statistics, Dynamix System Temperature, Dynamix webGui, Fix Common Problems, Nerd Tools, Preclear Disks, Statistics, Unassigned Devices. Dockers Installed: Diagnostics File: https://goo.gl/AVAapZ Quote Link to comment
wgstarks Posted February 13, 2017 Share Posted February 13, 2017 I updated to 6.3.1 today and am getting this warning when scanning for errors, but does not detect any errors and otherwise seems to be working OK. Any ideas? Already reported- http://lime-technology.com/forum/index.php?topic=48972.msg539675#msg539675 Quote Link to comment
phorse Posted February 13, 2017 Share Posted February 13, 2017 I updated to 6.3.1 today and am getting this warning when scanning for errors, but does not detect any errors and otherwise seems to be working OK. Any ideas? Already reported- http://lime-technology.com/forum/index.php?topic=48972.msg539675#msg539675 Thanks for the speedy response. I should have taken more time to read/search Quote Link to comment
Squid Posted February 14, 2017 Author Share Posted February 14, 2017 And it's fixed. Caused by a specific error in an application template that an author made... Hard to anticipate every template error... Quote Link to comment
Gico Posted February 14, 2017 Share Posted February 14, 2017 Still having this error message. Restarted chrome, closed all chrome windows on all relevant PCs, and still have this error. Quote Link to comment
Squid Posted February 14, 2017 Author Share Posted February 14, 2017 Still having this error message. Restarted chrome, closed all chrome windows on all relevant PCs, and still have this error. Hopefully a stupid question, but did you update FCP? Show a screenshot of the error as if its still present it should have changed slightly. Its not showing on my systems after the update Quote Link to comment
phorse Posted February 14, 2017 Share Posted February 14, 2017 And it's fixed. Caused by a specific error in an application template that an author made... Hard to anticipate every template error... The update fixed it for me. Many thanks! Quote Link to comment
Gico Posted February 14, 2017 Share Posted February 14, 2017 Still having this error message. Restarted chrome, closed all chrome windows on all relevant PCs, and still have this error. Hopefully a stupid question, but did you update FCP? Show a screenshot of the error as if its still present it should have changed slightly. Its not showing on my systems after the update Good question but yes, I updated FCP. It says version 2017.02.03b now. Screenshot attached. 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.