snmpd Error opening specified endpoint

2004-02-10 Thread Antoine Jacoutot
Hi :)

I'm having a problem starting snmpd under FreeBSD-5.2-p2...
I tried several options but I always get some strange errors.
Note that I launch snmpd as root...

---
# snmpd -p /var/run/snmpd.pid -c /usr/local/share/snmp/snmpd.conf -Ls d 
127.0.0.1

snmpd: Error opening specified endpoint 127.0.0.1
snmpd: Server Exiting with code 1
---
# snmpd -p /var/run/snmpd.pid -c /usr/local/share/snmp/snmpd.conf


snmpd: Error opening specified endpoint udp:161
snmpd: Server Exiting with code 1
---
# netstat -a | grep snm
udp4   0  0  *.snmp *.*

# ps ax | grep snmp
-- nothing !!!
---

If you have any idea on what's happening, I would really appreciate.
Thanks in advance.

Antoine
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: snmpd Error opening specified endpoint

2004-02-10 Thread Saint Aardvark the Carpeted
Antoine Jacoutot disturbed my sleep to write:
 I'm having a problem starting snmpd under FreeBSD-5.2-p2...
 I tried several options but I always get some strange errors.

Hm...it looks like you may already have snmp running, or at least
something else listening on UDP port 161:

 # netstat -a | grep snm
 udp4   0  0  *.snmp *.*

Try running sockstat | grep 161 and posting the results.

Also, a quick Google for snmp specified endpoint turns up a fair
number of newsgroup messages; some seem to suggest that there may be
problems with the very latest version of net-snmpd.  By any chance, are
you compiling a very recent version?

Hugh

--
Saint Aardvark the Carpeted
[EMAIL PROTECTED]
Because the plural of Anecdote is Myth.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: snmpd Error opening specified endpoint

2004-02-10 Thread Antoine Jacoutot
On Tuesday 10 February 2004 15:52, Saint Aardvark the Carpeted wrote:
 something else listening on UDP port 161:
  # netstat -a | grep snm
  udp4   0  0  *.snmp *.*

Yes, strange, isn't it ?
Especially since this is a brand new system not even connected to the internet 
(I mean, there can't be any rootkit or so...).

 Try running sockstat | grep 161 and posting the results.

Pfuhh, why didn't I do this before, what an idiot...
I can't reach the server right now, so I'll post the output as soon as I get 
to the box...

 Also, a quick Google for snmp specified endpoint turns up a fair
 number of newsgroup messages; some seem to suggest that there may be
 problems with the very latest version of net-snmpd.  By any chance, are
 you compiling a very recent version?

Yes, I've seen all those google posts before asking here, BUT:
- I compiled net-snmp from the ports collection
- the latest port is from January 2nd, so I guess someone would have caught 
this problem before me if it was specifically FreeBSD/port related.

Obviously, there's something wrong on my box...
I'll try to give more information soon.

Thanks.

Antoine
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]