tuxbass Posted January 23, 2017 Share Posted January 23, 2017 Accidentally clicked 'Ignore Error' for unclean shutdown detected error. How can the ignored errors/warnings be unignored? Is the course of action still to delete ignoredList.json? Don't see the ignored section on UI (think I acknowledged the err as well). Quote Link to comment
Squid Posted January 23, 2017 Author Share Posted January 23, 2017 Next time any ignored errors are found you can hit re-monitor on them. But in your case, probably the best would be to delete this file /config/plugins/fix.common.problems/ignoreList.json on the flash drive Quote Link to comment
Squid Posted January 23, 2017 Author Share Posted January 23, 2017 Is the course of action still to delete ignoredList.json? Don't see the ignored section on UI (think I acknowledged the err as well). There are 2 errors (unclean shutdown and OOM errors) that have the acknowledgement. This is because of how the errors are found. With all other errors, once they are ignored, when they are found again (a simple rescan will do it) they can be remonitored. Shutdown and OOM can't be found again by the rescan because they were acknowledged. So pretty much 3 options: Pull the plug on the server to generate another unclean shutdown (I don't recommend this) Delete the file (you'll have to ignore any errors previously ignored again) This is the simplest way Edit the file with Notepad++ and remove the appropriate line (and making sure that the last entry does not have a comma after it). Quote Link to comment
dlandon Posted January 27, 2017 Share Posted January 27, 2017 I have this in my syslog and it also shows on the console: Jan 27 02:08:57 BackupServer root: Fix Common Problems Version 2017.01.24 Jan 27 02:08:57 BackupServer root: Fix Common Problems: Error: Unable to communicate with GitHub.com ** Ignored Not sure if this is a problem or not. It does show up as an error though. I have multiple vlans and it might be from a delay in the network coming up. Quote Link to comment
Squid Posted January 27, 2017 Author Share Posted January 27, 2017 I have this in my syslog and it also shows on the console: Jan 27 02:08:57 BackupServer root: Fix Common Problems Version 2017.01.24 Jan 27 02:08:57 BackupServer root: Fix Common Problems: Error: Unable to communicate with GitHub.com ** Ignored Not sure if this is a problem or not. It does show up as an error though. I have multiple vlans and it might be from a delay in the network coming up. Probably. The test is a ping github.com But it's showing up on the console? Quote Link to comment
dlandon Posted January 27, 2017 Share Posted January 27, 2017 I have this in my syslog and it also shows on the console: Jan 27 02:08:57 BackupServer root: Fix Common Problems Version 2017.01.24 Jan 27 02:08:57 BackupServer root: Fix Common Problems: Error: Unable to communicate with GitHub.com ** Ignored Not sure if this is a problem or not. It does show up as an error though. I have multiple vlans and it might be from a delay in the network coming up. Probably. The test is a ping github.com But it's showing up on the console? Yes, the error shows on the console also. Quote Link to comment
Squid Posted January 27, 2017 Author Share Posted January 27, 2017 I have this in my syslog and it also shows on the console: Jan 27 02:08:57 BackupServer root: Fix Common Problems Version 2017.01.24 Jan 27 02:08:57 BackupServer root: Fix Common Problems: Error: Unable to communicate with GitHub.com ** Ignored Not sure if this is a problem or not. It does show up as an error though. I have multiple vlans and it might be from a delay in the network coming up. Probably. The test is a ping github.com But it's showing up on the console? Yes, the error shows on the console also. Something like this?root@Server_A:~# ping blahblahblah ping: unknown host blahblahblah Quote Link to comment
dlandon Posted January 27, 2017 Share Posted January 27, 2017 I have this in my syslog and it also shows on the console: Jan 27 02:08:57 BackupServer root: Fix Common Problems Version 2017.01.24 Jan 27 02:08:57 BackupServer root: Fix Common Problems: Error: Unable to communicate with GitHub.com ** Ignored Not sure if this is a problem or not. It does show up as an error though. I have multiple vlans and it might be from a delay in the network coming up. Probably. The test is a ping github.com But it's showing up on the console? Yes, the error shows on the console also. Something like this?root@Server_A:~# ping blahblahblah ping: unknown host blahblahblah Yes. Quote Link to comment
Squid Posted January 27, 2017 Author Share Posted January 27, 2017 I have this in my syslog and it also shows on the console: Jan 27 02:08:57 BackupServer root: Fix Common Problems Version 2017.01.24 Jan 27 02:08:57 BackupServer root: Fix Common Problems: Error: Unable to communicate with GitHub.com ** Ignored Not sure if this is a problem or not. It does show up as an error though. I have multiple vlans and it might be from a delay in the network coming up. Probably. The test is a ping github.com But it's showing up on the console? Yes, the error shows on the console also. Something like this?root@Server_A:~# ping blahblahblah ping: unknown host blahblahblah Yes. K. I don't have stderr redirected to null. Will fix at some point Sent from my LG-D852 using Tapatalk Quote Link to comment
dlandon Posted January 27, 2017 Share Posted January 27, 2017 I have this in my syslog and it also shows on the console: Jan 27 02:08:57 BackupServer root: Fix Common Problems Version 2017.01.24 Jan 27 02:08:57 BackupServer root: Fix Common Problems: Error: Unable to communicate with GitHub.com ** Ignored Not sure if this is a problem or not. It does show up as an error though. I have multiple vlans and it might be from a delay in the network coming up. Probably. The test is a ping github.com But it's showing up on the console? Yes, the error shows on the console also. Something like this?root@Server_A:~# ping blahblahblah ping: unknown host blahblahblah Yes. K. I don't have stderr redirected to null. Will fix at some point Sent from my LG-D852 using Tapatalk Should it be downgraded to a Warning and not an error? Quote Link to comment
Squid Posted January 27, 2017 Author Share Posted January 27, 2017 I have this in my syslog and it also shows on the console: Jan 27 02:08:57 BackupServer root: Fix Common Problems Version 2017.01.24 Jan 27 02:08:57 BackupServer root: Fix Common Problems: Error: Unable to communicate with GitHub.com ** Ignored Not sure if this is a problem or not. It does show up as an error though. I have multiple vlans and it might be from a delay in the network coming up. Probably. The test is a ping github.com But it's showing up on the console? Yes, the error shows on the console also. Something like this?root@Server_A:~# ping blahblahblah ping: unknown host blahblahblah Yes. K. I don't have stderr redirected to null. Will fix at some point Sent from my LG-D852 using Tapatalk Should it be downgraded to a Warning and not an error? 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 Quote Link to comment
Squid Posted January 28, 2017 Author Share Posted January 28, 2017 Added in tests for Call Traces which should cover just about any big error from the Kernel (Kernel Oops, General Protection Faults, etc) Quote Link to comment
WannabeMKII Posted February 1, 2017 Share Posted February 1, 2017 The last couple of days, fix common problems has reported an issue with 'call traces' and on checking the logs, it appears to be; Jan 30 17:59:57 TechNAS kernel: CPU: 1 PID: 0 Comm: swapper/1 Tainted: G W 4.4.30-unRAID #2 Jan 30 17:59:57 TechNAS kernel: Hardware name: HP ProLiant MicroServer, BIOS O41 07/29/2011 Jan 30 17:59:57 TechNAS kernel: 0000000000000000 ffff88011fc83dd0 ffffffff8136f79f ffff88011fc83e18 Jan 30 17:59:57 TechNAS kernel: 0000000000000132 ffff88011fc83e08 ffffffff8104a4ab ffffffff8155871e Jan 30 17:59:57 TechNAS kernel: ffff88011afba000 ffff8800c3ad6e00 ffff88011afba3a0 0000000000000001 Jan 30 17:59:57 TechNAS kernel: Call Trace: I'm guessing it's something to do with the BIOS or CPU? Is it something to be worried about, or something I can fix? Quote Link to comment
Squid Posted February 1, 2017 Author Share Posted February 1, 2017 You would need to post your diagnostics. Call traces are meaningless without knowing what leads up to them. Sent from my LG-D852 using Tapatalk Quote Link to comment
WannabeMKII Posted February 1, 2017 Share Posted February 1, 2017 You would need to post your diagnostics. Call traces are meaningless without knowing what leads up to them. As requested, diagnostics attached... Thanks. technas-diagnostics-20170201-1648.zip Quote Link to comment
John_M Posted February 3, 2017 Share Posted February 3, 2017 Hi Squid, is there any chance the troubleshooting syslog that's saved to the boot flash could be given a slightly different name to distinguish it easily from the other syslog that's contained within the diagnostic zip, please? Quote Link to comment
Squid Posted February 3, 2017 Author Share Posted February 3, 2017 Hi Squid, is there any chance the troubleshooting syslog that's saved to the boot flash could be given a slightly different name to distinguish it easily from the other syslog that's contained within the diagnostic zip, please? Why? Quote Link to comment
John_M Posted February 3, 2017 Share Posted February 3, 2017 Hi Squid, is there any chance the troubleshooting syslog that's saved to the boot flash could be given a slightly different name to distinguish it easily from the other syslog that's contained within the diagnostic zip, please? Why? Because people asking for help often forget to include it and when requested manage to attach the wrong file. Quote Link to comment
Squid Posted February 3, 2017 Author Share Posted February 3, 2017 Hi Squid, is there any chance the troubleshooting syslog that's saved to the boot flash could be given a slightly different name to distinguish it easily from the other syslog that's contained within the diagnostic zip, please? Why? Because people asking for help often forget to include it and when requested manage to attach the wrong file. lol Everyone forgets to include it, and when they do Trurl et al bug them that there's no reason to include it, because diagnostics already includes it (but with troubleshooting mode, the syslog.txt will contain up to 30minutes more logging than the last diagnostics) Quote Link to comment
John_M Posted February 3, 2017 Share Posted February 3, 2017 Hi Squid, is there any chance the troubleshooting syslog that's saved to the boot flash could be given a slightly different name to distinguish it easily from the other syslog that's contained within the diagnostic zip, please? Why? Because people asking for help often forget to include it and when requested manage to attach the wrong file. lol Everyone forgets to include it, and when they do Trurl et al bug them that there's no reason to include it, because diagnostics already includes it (but with troubleshooting mode, the syslog.txt will contain up to 30minutes more logging than the last diagnostics) All the more reason to give it a slightly different name. If I'm trying to help someone and I want to see the log for that last 30 minutes, the last thing I need is a copy of the syslog I already have from the diagnostics zip. Quote Link to comment
WannabeMKII Posted February 3, 2017 Share Posted February 3, 2017 You would need to post your diagnostics. Call traces are meaningless without knowing what leads up to them. As requested, diagnostics attached... Thanks. Just wondering if anyone with far more knowledgable than me has managed to work out what might be causing the trace issues? Thanks. Quote Link to comment
Squid Posted February 3, 2017 Author Share Posted February 3, 2017 You would need to post your diagnostics. Call traces are meaningless without knowing what leads up to them. As requested, diagnostics attached... Thanks. Just wondering if anyone with far more knowledgable than me has managed to work out what might be causing the trace issues? Thanks. You should post a new thread in general support where more eyes will see it. Quote Link to comment
WannabeMKII Posted February 3, 2017 Share Posted February 3, 2017 You would need to post your diagnostics. Call traces are meaningless without knowing what leads up to them. As requested, diagnostics attached... Thanks. Just wondering if anyone with far more knowledgable than me has managed to work out what might be causing the trace issues? Thanks. You should post a new thread in general support where more eyes will see it. No problem, done. Quote Link to comment
John_M Posted February 3, 2017 Share Posted February 3, 2017 Hi Squid, is there any chance the troubleshooting syslog that's saved to the boot flash could be given a slightly different name to distinguish it easily from the other syslog that's contained within the diagnostic zip, please? Why? Because people asking for help often forget to include it and when requested manage to attach the wrong file. lol Everyone forgets to include it, and when they do Trurl et al bug them that there's no reason to include it, because diagnostics already includes it (but with troubleshooting mode, the syslog.txt will contain up to 30minutes more logging than the last diagnostics) All the more reason to give it a slightly different name. If I'm trying to help someone and I want to see the log for that last 30 minutes, the last thing I need is a copy of the syslog I already have from the diagnostics zip. Any chance you could take a look at this thread, please? I'm confused. 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. 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.