CheckMK: lib-ares-cli2

[acozine]

lib-ares-cli2 was generating warnings and critical alerts all weekend, mostly memory usage levels, plus some 'unreachable' warnings, and some 'DOWN' warnings.

[acozine]

The lib-ares-cli3 VM also alerted for memory usage.
So did lib-staff999 - I created #111 for that one.

The lib-ares-cli* VMs are still alerting:

Service PROBLEM notification
Host: [lib-ares-cli2.princeton.edu]
Service: Memory
State: WARNING
Additional Info
RAM: 88.35% - 7.07 GiB of 8.00 GiB (warn/crit at 80.00%/90.00% used)(!), Commit charge: 84.74% - 8.64 GiB of 10.2 GiB (warn/crit at 80.00%/90.00% used)(!)
Please take a look: @ansible, @jkazmier, @tmincher

[acozine]

Still happening on the lib-ares boxes, and it's definitely memory usage, not that DotNet warning:

Service PROBLEM notification
Host: [lib-ares-cli2.princeton.edu]
Service: Memory
State: WARNING
Additional Info
RAM: 85.09% - 6.81 GiB of 8.00 GiB (warn/crit at 80.00%/90.00% used)(!), Commit charge: 65.74% - 6.08 GiB of 9.25 GiB
Please take a look: @tmincher, @ansible, @jkazmier
Check_MK notification: Wed Oct 2 04:01:12 EDT 2024

Service PROBLEM notification
Host: lib-ares-cli2.princeton.edu
Service: Memory
State: CRITICAL
Additional Info
RAM: 95.11% - 7.61 GiB of 8.00 GiB (warn/crit at 80.00%/90.00% used)(!!), Commit charge: 80.25% - 7.42 GiB of 9.25 GiB (warn/crit at 80.00%/90.00% used)(!)
Please take a look: @ansible, @jkazmier, @tmincher
Check_MK notification: Wed Oct 2 04:02:13 EDT 2024

[kayiwa]

Happened again

Service PROBLEM notification
Host: [lib-ares-cli2.princeton.edu](http://lib-ares-cli2.princeton.edu/) (IP: 128.112.203.71)
Service: Memory
State: CRITICAL
Additional Info
RAM: 92.90% - 7.43 GiB of 8.00 GiB (warn/crit at 80.00%/90.00% used)(!!), Commit charge: 81.94% - 7.58 GiB of 9.25 GiB (warn/crit at 80.00%/90.00% used)(!)
Please take a look: @jkazmier, @tmincher, @ansible
Check_MK notification: Tue Oct 8 04:03:24 EDT 2024