Hi everyone, first time here.
I have an AlmaLinux 9 vm that runs a GitLab instance.
Almost everytime GitLab runs a CI pipeline, snmpd crashes.
Here is an extract of /var/log/messages
Aug 26 07:37:38 code gitlab-runner <Many GitLab job stuff here>
Aug 26 07:37:47 code snmpd[1277]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
Aug 26 07:37:47 code systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Aug 26 07:38:47 code snmpd[1277]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
Aug 26 07:39:47 code snmpd[1277]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
Aug 26 07:40:47 code snmpd[1277]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
Aug 26 07:41:47 code snmpd[1277]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
Aug 26 07:42:06 code snmpd[1277]: error on subcontainer 'ifTable container' remove (-1)
Aug 26 07:42:09 code snmpd[1277]: free(): invalid pointer
Aug 26 07:42:09 code systemd[1]: Created slice Slice /system/systemd-coredump.
Aug 26 07:42:09 code systemd[1]: Started Process Core Dump (PID 423302/UID 0).
Aug 26 07:42:09 code systemd-coredump[423303]: Resource limits disable core dumping for process 1277 (snmpd).
Aug 26 07:42:09 code systemd-coredump[423303]: Process 1277 (snmpd) of user 0 dumped core.
Aug 26 07:42:09 code systemd[1]: systemd-coredump@0-423302-0.service: Deactivated successfully.
Aug 26 07:42:09 code systemd[1]: snmpd.service: Main process exited, code=dumped, status=6/ABRT
Aug 26 07:42:09 code systemd[1]: snmpd.service: Failed with result 'core-dump'.
Aug 26 07:42:09 code systemd[1]: snmpd.service: Consumed 2min 16.325s CPU time.
The GitLab runner uses Docker intensively for my CI, and dozens of containers as spun up everytime.
I see that RHEL has this in their KB, but behind a paywall : RHEL9: snmpd crashes regularly with "error on subcontainer 'ifTable container' remove (-1)" message - Red Hat Customer Portal
It is mentioned :
This usually occurs on systems running Docker workloads, hence having many non-persistent
veth
interfaces configured
Has anybody encounter this, or has any clue ?
Thanks for your help
Regards