Hi
I have been using snmp for 'years' but never came accross this issue before.
On starting i get this
Apr 17 15:42:20 server snmpd: snmpd startup succeeded Apr 17 15:42:21 server snmpd[29630]: Error opening specified endpoint "udp:161" Apr 17 15:42:21 server snmpd[29630]: Server Exiting with code 1
i have googled this but cant find a solution - does anyone have any hints?
thanks
Is something else already listening on udp:161?
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Tom Brown Sent: Tuesday, April 17, 2007 10:47 AM To: CentOS mailing list Subject: [CentOS] CentOS 3 - net-snmp startup issue
Hi
I have been using snmp for 'years' but never came accross this issue before.
On starting i get this
Apr 17 15:42:20 server snmpd: snmpd startup succeeded Apr 17 15:42:21 server snmpd[29630]: Error opening specified endpoint "udp:161" Apr 17 15:42:21 server snmpd[29630]: Server Exiting with code 1
i have googled this but cant find a solution - does anyone have any hints?
thanks _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Is something else already listening on udp:161?
well making the startup a little more verbose gave me this
Apr 17 15:44:54 server portsentry[937]: attackalert: Connect from host: xxx.xxx.xxx.xxx/xxx.xxx.xxx.xxx to UDP port: 161 Apr 17 15:44:54 server portsentry[937]: attackalert: Host: xxx.xxx.xxx.xxx is already blocked. Ignoring Apr 17 15:44:59 server portsentry[937]: attackalert: Connect from host: xxx.xxx.xxx.xxx/xxx.xxx.xxx.xxx to UDP port: 161 Apr 17 15:44:59 server portsentry[937]: attackalert: Host: xxx.xxx.xxx.xxx is already blocked. Ignoring
so i fixed that and now all is well
-
Drew Weaver -
Tom Brown