Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

SNMPD dies daily

SNMPD dies daily

SNMPD dies daily

SNMP Version: net-snmp-5.6.1-intel-x64

Currently after starting my snmp client it eventually shuts down about 10/11 hours later after using all file handles. It currently uses all the File descriptors allowed to a process and is monitored quite easily with lsof -p <pid> with output as below:

snmpd 27079 jboss_se 381u sock 0,5 939974836 can't identify protocol
snmpd 27079 jboss_se 382u sock 0,5 939975503 can't identify protocol
snmpd 27079 jboss_se 383u sock 0,5 939976201 can't identify protocol

Final messages to output log before the snmpd dies:

could not create socket
cannot open /proc/net/dev ...
/proc/partitions: Too many open files
/proc/stat: Too many open files
/proc/partitions: Too many open files
/proc/stat: Too many open files
/proc/partitions: Too many open files
/proc/stat: Too many open files
/proc/partitions: Too many open files
/proc/stat: Too many open files
/proc/partitions: Too many open files
/proc/stat: Too many open files
could not open /proc/net/arp
cannot open /proc/net/snmp ...
client: socket() Error
: Bad file descriptor
could not create socket

So far I have added -D to my snmpd for debug (very verbose) the only error that is consistent is this client connect Error highlighted in bold.

trace: run_alarms(): snmp_alarm.c, 245:
snmp_alarm: run alarm 2
trace: send_status_notification(): mibgroup/apache2/serverStatus.c, 114:
serverStatus: NOTIFICATION - Init
trace: check_estado(): mibgroup/apache2/serverStatus.c, 198:
serverStatus: FCN - check_estado - Init
client: connect() Error
: Connection refused

trace: send_http_get(): mibgroup/apache2/totalAccess.c, 193:
totalAccess: send_http_get --> Connect Error
trace: check_estado(): mibgroup/apache2/serverStatus.c, 235:
serverStatus: FCN - check_estado - Can't open Pidfile
trace: check_estado(): mibgroup/apache2/serverStatus.c, 236:
serverStatus: Pidfile -
trace: check_estado(): mibgroup/apache2/serverStatus.c, 254:
serverStatus: FCN - check_estado - End (0)
trace: send_status_notification(): mibgroup/apache2/serverStatus.c, 116:
serverStatus: NOTIFICATION -0 0

Is anyone familiar with this problem or have any ideas or tips on how to troubleshoot this problem?

RE: SNMPD dies daily

You better off posting this to the net-snmp site. Guys there will have much more experience than anyone here.

That or start digging through the code yourself.


Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close