This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.
Log in to ask a question

NodeSysctlChange

Posted on 08-06-2024 06:36 AM
aebouel
Bronze 1
Bronze 1
Reply posted on --/--/---- --:-- AM

A google monitoring alert  is firing with the reason : `NodeSysctlChange`.  Here is the message:

`Problem State for xxxxxx-gke-xxxx1-staging-e2-standard2-40g--72e0145e-97n5 with metric labels {instance_name=gke-xxxx-staging-e2-standard2-40g--72e0145e-97n5, reason=NodeSysctlChange, type=SysctlChanged} is above the threshold of 0.750 with a value of 0.800.`

aebouel_0-1722950709960.png

We have 3 GKE clusters and the problem occurs on all nodes. But each alarm resolves itself after about 7 days.
I don't understand what's happening or how to fix it. Need help please.

 

0 3 834
Topic Labels
0 Likes
3 REPLIES 3

Posted on --/--/---- --:-- AM
yrhsk
Bronze 4
Bronze 4
Reply posted on --/--/---- --:-- AM

The `NodeSysctlChange` alert means sysctl settings on your GKE nodes are changing. This could be due to automatic updates, scripts, or config tools. Check for recent updates, review node configs, and compare sysctl settings. If it resolves after 7 days, it might be a scheduled update.

Posted on --/--/---- --:-- AM
garisingh
Staff
Reply posted on --/--/---- --:-- AM

Are you using GKE Usage Metering on those clusters by chance?

0 Likes

Posted on --/--/---- --:-- AM
aebouel2
Bronze 2
Bronze 2
In response to garisingh
Reply posted on --/--/---- --:-- AM

No. It is disabled on all clusters.

aebouel2_0-1723120827096.png

 

0 Likes
Top Labels in this Space