pod-mon.sh and mist-cleanup.sh to run forever even sometimes crashing #1387
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pwilczynskiclearcode
changed the title
leszko
approved these changes
Nov 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are logs from pod-mon.sh that we start from catalyst-api but I they started missing on sto-1 and sto-3 for some reason. On sto-1 the catalyst-api has been running for 11 days and logs stopped appearing on 2024-11-02 17:48:43 with a log line cmd: failed to start pod-mon.sh. It also lines up with the high CPU spike on this node. Same story with sto-1 catalyst pod.
I guess we fail to run
pod-mon.shor mist cleanup script on high CPU/memory or it times out what results in never running these two scripts again.