RE: Cannot start snmpd plus "snmp dead but subsys locked" msg
"Lee, John (Sydney)" <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <136A969E54082648AD45F9228A75F53C02F336C5@apac-syd-ex001.apac.cpwr.corp> |
> You've probably got another agent running in the background, > and listening on port 161. > Try shutting that down before starting your agent. > # ps waux | grep snmp root 1529 0.0 0.0 4008 700 pts/0 S+ 17:18 0:00 grep snmp root 2796 0.0 0.1 8864 3396 ? S Oct09 0:02 snmpd root 32714 0.6 0.1 48380 3076 ? Ssl Sep27 249:32 /opt/dell/srvadmin/dataeng/bin/dsm_sa_snmp32d # /opt/dell/srvadmin/dataeng/bin/dataeng stop Stopping Systems Management Data Engine: Stopping dsm_sa_snmp32d: [ OK ] Stopping dsm_sa_eventmgr32d: [ OK ] Stopping dsm_sa_datamgr32d: [ OK ] # ps waux | grep snmp root 1568 0.0 0.0 4008 724 pts/0 S+ 17:19 0:00 grep snmp root 2796 0.0 0.1 8864 3396 ? S Oct09 0:02 snmpd # /usr/local/sbin/snmpd -f -Le udp:161 Error opening specified endpoint "udp:161" Server Exiting with code 1 Sorry, my guess is probably wrong that the DELL snmp32d was also using udp:161. Could you please enlighten me on how to locate the other agent? 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