Hi all,
Seeking an explanation to why LXC containers popping up in Check-MK monitoring after x time regarding shared memory.
The only solution to get rid of the notification in Check_MK monitoring for now is to just bluntly reboot the container.
What i am after is an understanding as to what is happening here, and to be exact :
- Glowsome
Seeking an explanation to why LXC containers popping up in Check-MK monitoring after x time regarding shared memory.
The only solution to get rid of the notification in Check_MK monitoring for now is to just bluntly reboot the container.
What i am after is an understanding as to what is happening here, and to be exact :
- Is this an issue with ProxMox?
- Are thresholds in Check_MK wrong?
- Is the default (.deb) agent which i am using unfit/the wrong way for monitoring ProxMox unsuited for this type of host?
- Glowsome