On Tue, 16 Nov 2004 21:53:19 -0600 [EMAIL PROTECTED] wrote: DC> 3)Next ran the snmpd and snmpdtrapd DC> ./snmpd -f -L -d DC> ./snmptrapd -Le -d
Try starting snmptrapd before snmpd. DC> Then i issued command to send trap: DC> snmptrap -v 2c -c public localhost '' .1.3.6.1.4.1.20 21.991.17 DC> .1.3.6.1.2.1.1.6.0 s "just here" DC> the snmptrap printed and stopped. listed below was what printed out. DC> DC> "snmptrapd -P -F "22:28 TRAP0.0 from 0.0.0.0 DC> ""Broken pipe DC> DC> It seemed that the trap was sent and also was received by the trap dameon. DC> But why then it stopped and what does "Broken pipe" mean? Are you sure snmptrapd stopped? Does it receive further traps if you send them using snmptrap? Broken pipe means that either a trap hander is being called but not reading all of its input, or the AgentX sub-agent component of snmptrapd is getting disconnected from the master agent. In either case, it should recover and continue to receive traps. What version are you using? What platform are you on? -- Robert Story; NET-SNMP Junkie Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-users> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ 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
