RE: Cannot start snmpd plus "snmp dead but subsys locked" msg

"Lee, John (Sydney)" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <136A969E54082648AD45F9228A75F53C02F338AB@apac-syd-ex001.apac.cpwr.corp>
> "lsof -p 2796" output should contain all the information you need.
> If you can't locate the start/stop script, "kill 2796" (no, not
> "-9") will probably do it as well.
> 
# lsof -p 2796 (please see attached)
# kill 2796
# /usr/local/sbin/snmpd -f -Le udp:161
NET-SNMP version 5.4.1


Received TERM or STOP signal...  shutting down...

/usr/local/sbin/snmpd seems to stay on forever without doing anything.

What is happening?
>
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

_______________________________________________
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
snmpd-1.txt (text/plain, 2.4 KB)
# lsof -p 2796
COMMAND  PID USER   FD   TYPE    DEVICE     SIZE      NODE NAME
snmpd   2796 root  cwd    DIR     253,0     4096         2 /
snmpd   2796 root  rtd    DIR     253,0     4096         2 /
snmpd   2796 root  txt    REG     253,0    49869   2741157 /usr/local/sbin/snmpd (deleted)
snmpd   2796 root  mem    REG     253,0           16842780 /lib/libcrypt-2.6.so (path inode=16842754)
snmpd   2796 root  mem    REG     253,0           16842769 /lib/ld-2.6.so (path inode=16842831)
snmpd   2796 root  DEL    REG     253,0            2741147 /usr/local/lib/libnetsnmphelpers.so.15.1.0
snmpd   2796 root  DEL    REG     253,0            2741152 /usr/local/lib/libnetsnmpmibs.so.15.1.0
snmpd   2796 root  mem    REG     253,0           16842776 /lib/libc-2.6.so (path inode=16842846)
snmpd   2796 root  DEL    REG     253,0            2741139 /usr/local/lib/libnetsnmp.so.15.1.0
snmpd   2796 root  mem    REG     253,0           16842802 /lib/libresolv-2.6.so (path inode=16842975)
snmpd   2796 root  mem    REG     253,0           16842808 /lib/libutil-2.6.so (path inode=16843862)
snmpd   2796 root  DEL    REG     253,0            2741143 /usr/local/lib/libnetsnmpagent.so.15.1.0
snmpd   2796 root  mem    REG     253,0           16842782 /lib/libdl-2.6.so (path inode=16842860)
snmpd   2796 root  mem    REG     253,0           16842800 /lib/libpthread-2.6.so (path inode=16843859)
snmpd   2796 root  mem    REG     253,0           16842784 /lib/libm-2.6.so (path inode=16842862)
snmpd   2796 root  mem    REG     253,0           16842786 /lib/libnsl-2.6.so (path inode=16842858)
snmpd   2796 root  mem    REG     253,0            2951957 /usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so (path inode=2951960)
snmpd   2796 root  mem    REG     253,0 65179696   2722322 /usr/lib/locale/locale-archive
snmpd   2796 root    0u   CHR       1,3               1670 /dev/null
snmpd   2796 root    1u   CHR       1,3               1670 /dev/null
snmpd   2796 root    2u   CHR       1,3               1670 /dev/null
snmpd   2796 root    3w   REG     253,0      466  18973504 /var/log/snmpd.log
snmpd   2796 root    4r  FIFO       0,6          426932682 pipe
snmpd   2796 root    5w  FIFO       0,6          426932682 pipe
snmpd   2796 root    6u  IPv4 426947386                UDP *:snmp
# kill 2796
# /usr/local/sbin/snmpd -f -Le udp:161
NET-SNMP version 5.4.1


Received TERM or STOP signal...  shutting down...
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.