Re: Inform socket overflow issue

Raja Mon, 08 Jun 2026 17:11:11 -0700

Hi,

Never mind. I am able to solve it. It was in the custom code.

Thanks.

On Jun 4, 2026, at 5:14 PM, raja vankam <[email protected]> wrote:

Hi,
I am seeing an issue with net-SNMP-5.9.1 configured to send informs where I get an error that maximum sockets 1024 are opened and no more files can be opened.
I even tried net-SNMP-5.9.5.2 as well.

This issue surfaces after a time frame of about 240 days with 4 Informs every day. To accelerate the issue, I configured it to send informs every 10 sec with a retry of 1 min. I see an error after about 2 hours of run time.
I did run a tcpdump command during the testing to confirm I receive acknowledgements from the trap receiver. There are occasional missed acknowledgements and I see a retry with a successful acknowledgement. watch -n 1 "ls /proc/<PID>/fd | wc -l" gives output as 1024 which is the default socket limit in our Linux.

I tried SNMP GET for every 5 sec with no issue in the number of sockets. So GETs are not a problem.

Errors I see are:
/proc/stat: Too many open files
interface_linux: cannot open /proc/net/dev: Too many open files
interface_linux: cannot open /proc/net/dev: Too many open files
/proc/stat: Too many open files
interface_linux: cannot open /proc/net/dev: Too many open files

Agent configuration:
compiled for V2C agent
Agent is generating Informs from a posix thread that is actively waiting for the events.
send_v2trap() is used to generate Informs.

snmpd.conf file: (retry count is 72, interval is 1 min)
rwcommunity private
trapsess -v 2c -Ci -c tech -r 72 -t 60 192.168.1.100:162

Any inputs in this regard are greatly appreciated.

Regards,
Raj.

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Re: Inform socket overflow issue

Reply via email to