Web - 10/11/17 are not responding - Resolved
- Thread starter SachinK
- Start date
This is the 3rd time a node (different node) has seen an issue in less than 24 hours. We are bringing it up, and it is doing fsck due to length since last scan just like the others.
I am also checking if there is any remote exploit or bug that can make a kernel panic that is triggering these events because it does not seem likely all would just have an error otherwise.
There is nothing abnormal here to trigger and each has been on different power, switches etc to this point so that is out of the question, yet two of these nodes have had flawless execution (one has for the last almost years but did have issue prior), without any problems in their performance or execution.
I am also checking if there is any remote exploit or bug that can make a kernel panic that is triggering these events because it does not seem likely all would just have an error otherwise.
There is nothing abnormal here to trigger and each has been on different power, switches etc to this point so that is out of the question, yet two of these nodes have had flawless execution (one has for the last almost years but did have issue prior), without any problems in their performance or execution.