OK, no worries Dave. I have started the snmpd deamon with -Dread_config and it is reading the config I specified (both the simple one and complex one when I changed it).
There was a syntax error, which I fixed - no change in operation. I also see about 8 MIB related errors. There are some values in various MIB files declared of type Counter32 (1..4294967295) this is a valid value. SNMPv2-SMI.txt declares the Counter32 range as (0..4294967295) Is there a known problem regarding the declaration of unsigned ranges in MIB files? This would be very odd. The last message from snmpd is Error opening specified endpoint "" Server Exiting with code 1 But the daemon is running, so I am not sure what state the daemon is in. I will try modifying the offending MIB files and see if this changes anything. Adam -----Original Message----- From: [EMAIL PROTECTED] [mailto:] On Behalf Of Dave Shield Sent: Tuesday, February 13, 2007 8:39 AM To: Adam Bell Cc: [email protected] Subject: Re: SNMP non binding to socket 161 [ First - *please* don't mail me privately, without copying any responses to the mailing list. I don't have the time or inclination to offer private, unpaid, SNMP consultancy. Keep discussions to the list, where others can both learn and offer advice. Thanks. ] On 13/02/07, Adam Bell <[EMAIL PROTECTED]> wrote: > Usually there is a state : LISTENING when it is operational. There willbe a state LISTENING for *TCP* services, yes. But SNMP is primarily a UDP-based protocol, so wouldn't necessarily be displayed as "LISTENING". (It depends on the underlying O/S) > Since the > packets are queuing in the Recv-Q and sticking there, it is not even getting > to the place where access control could decide. Fair comment. > The snmpd.conf file I was using was pretty paired down, I was starting with > v2c so just declared the community strings. I confirmed the get via a > packet sniffer and it was correct. One possibility is that the agent isn't reading the config file you expect. Try using the option '-Dread_config' to check what it's actually working with. > I am going to try the EXAMPLE.conf file today and see if that changes > anything. Hmmm... not sure that'll help. Particularly if you're working with a simple config file already. > Any other ideas? I would appreciate it. Try starting the agent using snmpd -f -Le (plus any other options you need) That will let you see any error messages that the agent might produce. Another thing to check - shut down the agent, and run "netstat" again. Does the "snmp" entry disappear? Dave The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ 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
