NET-SNMP getting killed by oom-killer
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 692
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Hello
We have installed snmpd on photon os 4
tdnf install -y net-snmp net-snmp-devel
net-snmp-create-v3-user -ro -A XXXXXXXXXXXXX -X XXXXXXXXXXXX -a SHA -x AES vmware
systemctl enable --now snmpd
systemctl start snmpd
But every once in a while the snmpd process gets killed by oom-killer. Please see the logs in attachment.
This actually happens with all the snmpd processes that run on different photonOS 4 servers. I don't know if photonOS 3 is also affected.
Before the snmpd gets killed it reportedly uses 2.8G of RAM which is unusual for such a lightweight process.
NET-SNMP version 5.8
root@vclouddr-tunnel [ /etc/systemd/system ]# cat /etc/os-release
NAME="VMware Photon OS"
VERSION="4.0"
ID=photon
VERSION_ID=4.0
PRETTY_NAME="VMware Photon OS/Linux"
ANSI_COLOR="1;34"
HOME_URL="https://vmware.github.io/photon/"
BUG_REPORT_URL="https://github.com/vmware/photon/issues"
Reproduction steps
...
Expected behavior
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached journalctl.txt and the snmpd service running on Photon OS 4, then inspect the reported memory growth and OOM-killer events. Done means identifying a reproducible cause or confirming the affected component and documenting the evidence needed for a fix.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100