You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm using the system-log-monitor to detect the node problem and update the respective NodeCondition, which can match logs in /dev/kmsg of specific pattern.
I noticed that the NPD updates the NodeCondtion Status to True when it gets the target log. But after digging into the code of systemlogmonitor, I didn't find anything which will reset the NodeCondition to False after recovery.
I want to know who will take the responsibility to update the NodeCondtion to False after recovery in the best practice. Is it the job of remedy system?
The text was updated successfully, but these errors were encountered:
Congrool
changed the title
[QuestionWho will update the NodeCondition to "False"
[Question] Who will update the NodeCondition to "False" after the problem recovery
Aug 10, 2024
IIUC, this needs to be done manually. We currently use a custom script to implement this internally. npd is a inspect system that is responsible for reporting problems but not for recovery. Recovery requires manual recovery and manual recovery of the status.
Hi, I'm using the system-log-monitor to detect the node problem and update the respective NodeCondition, which can match logs in
/dev/kmsg
of specific pattern.I noticed that the NPD updates the NodeCondtion Status to True when it gets the target log. But after digging into the code of systemlogmonitor, I didn't find anything which will reset the NodeCondition to False after recovery.
I want to know who will take the responsibility to update the NodeCondtion to False after recovery in the best practice. Is it the job of remedy system?
The text was updated successfully, but these errors were encountered: