Hello folks, I got Nagios-1.4.1 on Gentoo up and running using the fine documentation and the template config files which I could easily edit to fit my needs.
But I ran into trouble with one single service: I do: server ~ # /usr/nagios/libexec/check_dhcp -v -s localhost -i eth0 DHCP socket: 3 Hardware address: 0050223937b4 DHCPDISCOVER to 255.255.255.255 port 67 DHCPDISCOVER XID: 162470487 (0x9AF1A57) DHCDISCOVER ciaddr: 0.0.0.0 DHCDISCOVER yiaddr: 0.0.0.0 DHCDISCOVER siaddr: 0.0.0.0 DHCDISCOVER giaddr: 0.0.0.0 send_dhcp_packet result: 548 No (more) data received Result=ERROR Total responses seen on the wire: 0 Valid responses for this machine: 0 DHCP problem: No DHCPOFFERs were received. server ~ # but at the same time in my logs: Jun 26 17:42:44 server dhcpd: DHCPDISCOVER from 00:50:22:39:37:b4 via eth0 Jun 26 17:42:45 server dhcpd: DHCPOFFER on 192.168.0.236 to 00:50:22:39:37:b4 via eth0 I tested on another host on my LAN and it works just fine. But that is not a solution for monitoring, because non of this clients is up all the time and I want the services to be checked 24x7. So I searched the web for a solution but I only found a french forum at wich this was once discussed. Unfortunately I don't speak french. ;) So I'd like to ask your help: Is it possible to monitor a dhcp server which is running on the same machine as nagios? And if yes, how to do that? Add a iptables rule to route back the DHCPOFFER or should it work out of the box? -- MfG Jan Open WebMail Project (http://openwebmail.org) 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 _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null