You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
KVM dualtor may fail in test_pretest.py::test_disable_rsyslog_rate_limit for memory leak because config syslog rate-limit-feature enable would use more than 300M memory
Results you see
Before enable:
admin@vlab-06:~$ sudo monit status $HOSTNAME
Monit 5.20.0 uptime: 36m
System 'vlab-06'
status Running
monitoring status Monitored
monitoring mode active
on reboot start
load average [0.23] [0.78] [0.79]
cpu 7.4%us 4.2%sy 0.3%wa
memory usage 3.0 GB [79.9%]
swap usage 0 B [0.0%]
uptime 37m
boot time Tue, 03 Dec 2024 05:43:00
data collected Tue, 03 Dec 2024 06:19:34
After enable:
admin@vlab-06:~$ sudo monit status $HOSTNAME
Monit 5.20.0 uptime: 32m
System 'vlab-06'
status Running
monitoring status Monitored
monitoring mode active
on reboot start
load average [1.59] [1.05] [0.83]
cpu 21.5%us 10.6%sy 2.8%wa
memory usage 3.5 GB [94.0%]
swap usage 0 B [0.0%]
uptime 33m
boot time Tue, 03 Dec 2024 05:43:00
data collected Tue, 03 Dec 2024 06:15:33
May cause error:
2024 Dec 3 03:49:17.025361 vlab-06 ERR memory_threshold_check: Free memory 125816 is less then min free memory threshold 204800.0
2024 Dec 3 03:49:39.700813 vlab-06 INFO containerd[670]: time="2024-12-03T03:49:37.956483972Z" level=error msg="get state for 143b9e60c4ecaea7313b63362701155435e039876eac33bed00f5a750dbad1e0" error="context deadline exceeded: unknown"
2024 Dec 3 03:49:39.753047 vlab-06 INFO containerd[670]: time="2024-12-03T03:49:39.394693139Z" level=warning msg="unknown status" status=0
Results you expected to see
No errors
Is it platform specific
generic
Relevant log output
No response
Output of show version
No response
Attach files (if any)
No response
The text was updated successfully, but these errors were encountered:
Issue Description
KVM dualtor may fail in test_pretest.py::test_disable_rsyslog_rate_limit for memory leak because
config syslog rate-limit-feature enable
would use more than 300M memoryResults you see
Before enable:
After enable:
May cause error:
Results you expected to see
No errors
Is it platform specific
generic
Relevant log output
No response
Output of
show version
No response
Attach files (if any)
No response
The text was updated successfully, but these errors were encountered: