Warnigs from cmk for my commited Memory on my Check MK Host (Debian)

(Alex ) #1

Hello,
d
Iam not sure what kind of problem I have. But maybe someone know what it is :wink:
Description of my System and Situation:
I’m running Check MK 1.5.0p21 RAW on a Debian 10.1 Server. (newest updates installed)
There are 330 Hosts and 4017 Services at one monitoring site. (160 of the Hosts are only monitored with a PING, the other uses SNMP and the cmk Agent; Servers, Switches, etc)
The CMK Host is a Hyper-V Machine (HyperV Host running with Win Server 2016) with 4GB RAM and 4 virtual CPU Cores.

On my CMK Server also the CMK Agent is running in the same Version (1.5.0p21) for monitoring themself.
Here is the “problem” why I’m writing this text:

Summary

Tuesday, 2019-09-10
Time Event Type Output
2019-09-10 12:03:34 SERVICE ALERT HARD WARN - RAM used: 1.80 GB of 3.84 GB, Swap used: 224.50 MB of 2.07 GB, Total virtual memory used: 2.02 GB of 5.91 GB (34.1%), Committed: 6.13 GB (103.7% of RAM + Swap, warn/crit at 100.0%/150.0%) WARN ,
2019-09-10 12:02:28 SERVICE ALERT HARD OK - RAM used: 1.62 GB of 3.84 GB, Swap used: 224.50 MB of 2.07 GB, Total virtual memory used: 1.84 GB of 5.91 GB (31.0%),
2019-09-10 12:00:28 SERVICE ALERT HARD WARN - RAM used: 1.63 GB of 3.84 GB, Swap used: 224.50 MB of 2.07 GB, Total virtual memory used: 1.85 GB of 5.91 GB (31.3%), Committed: 6.36 GB (107.6% of RAM + Swap, warn/crit at 100.0%/150.0%) WARN ,
2019-09-10 11:59:28 SERVICE ALERT HARD OK - RAM used: 1.69 GB of 3.84 GB, Swap used: 224.50 MB of 2.07 GB, Total virtual memory used: 1.91 GB of 5.91 GB (32.3%),
2019-09-10 11:58:34 SERVICE ALERT HARD WARN - RAM used: 1.81 GB of 3.84 GB, Swap used: 224.50 MB of 2.07 GB, Total virtual memory used: 2.03 GB of 5.91 GB (34.2%), Committed: 6.16 GB (104.2% of RAM + Swap, warn/crit at 100.0%/150.0%) WARN ,
2019-09-10 11:56:34 SERVICE ALERT HARD OK - RAM used: 1.61 GB of 3.84 GB, Swap used: 224.50 MB of 2.07 GB, Total virtual memory used: 1.83 GB of 5.91 GB (30.9%),
2019-09-10 11:55:31 SERVICE ALERT HARD WARN - RAM used: 1.62 GB of 3.84 GB, Swap used: 224.50 MB of 2.07 GB, Total virtual memory used: 1.84 GB of 5.91 GB (31.0%), Committed: 5.93 GB (100.2% of RAM + Swap, warn/crit at 100.0%/150.0%) WARN ,
2019-09-10 11:54:34 SERVICE ALERT HARD OK - RAM used: 1.70 GB of 3.84 GB, Swap used: 224.50 MB of 2.07 GB, Total virtual memory used: 1.91 GB of 5.91 GB (32.4%),
2019-09-10 11:53:35 SERVICE ALERT HARD WARN - RAM used: 1.77 GB of 3.84 GB, Swap used: 224.50 MB of 2.07 GB, Total virtual memory used: 1.99 GB of 5.91 GB (33.6%), Committed: 6.07 GB (102.6% of RAM + Swap, warn/crit at 100.0%/150.0%) WARN ,
2019-09-10 11:49:29 SERVICE ALERT HARD OK - RAM used: 1.72 GB of 3.84 GB, Swap used: 224.50 MB of 2.07 GB, Total virtual memory used: 1.94 GB of 5.91 GB (32.8%),
2019-09-10 11:48:36 SERVICE ALERT HARD WARN - RAM used: 1.80 GB of 3.84 GB, Swap used: 224.50 MB of 2.07 GB, Total virtual memory used: 2.02 GB of 5.91 GB (34.1%), Committed: 6.12 GB (103.5% of RAM + Swap, warn/crit at 100.0%/150.0%) WARN ,

Should I change the Thresholds of the Service?
Or is something wrong with my Server / Memory / Settings?
If so, is it a generel Linux(Debian) Problem or CheckMK caused?
There are no other applications on the machine than CheckMK.
I don’t have the needed knowledge, either about Linux or Check MK, to determine what to do.

If its only a problem caused by the operating system itself I would ask in a specialised debian forum but first I want to ask someone with better checkMK knowledge :slight_smile:

(Alex ) #2

I will just change the thresholds and ignore it…The server is running without any problems so I don’t have time to search for a problem when I’m not sure if it exists…

(Philipp Näther) #3

Commited RAM exceeding the actual RAM + SWAP means that the processes claim/reserve more RAM than there actually is but they don’t use it. That is a common behaviour.

You could

  1. determine which process reserves a lot of RAM and try to “fix” the application or
  2. simply set the thresholds to your needs as you already did

As long as you are actually not out of RAM on your server everything is fine.