Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have submitted this question to the sourceforge mailing list for opennms, but it is not getting posted for some reason, so I'm posting it here in the event that someone here has run into this issue before:
I have recently deployed OpenNMS across a network, and all desired functions are working well except for the DHCP discovery. I have looked through the FAQ and through the discussion lists and have seen others mention this error. The suggested resolutions are to ensure that dhclient (or any form of dhcp) is not being used to obtain the OpenNMS server's IP address and to make sure that the MAC address of the OpenNMS server is listed in dhcpd-configuration.xml. I tried both of these resolutions and neither worked. I was originally running OpenNMS as a test on a Xen virtualization box but moved it onto it's own hardware to make sure that none of Xen's bridging was causing problems, but that did not solve the problem either.
The error I get in the capsd.log is:
2007-04-19 13:04:45,116 ERROR [Capsd Suspect Pool-fiber0] Poller: IO Exception during socket connection establishment with DHCP client daemon.
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2213)
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2226)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2694)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:761)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:277)
at org.opennms.netmgt.dhcpd.Poller.<init>(Poller.java:245)
I am currently running on Debian Etch with the following /etc/network/interfaces configuration:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet static
I have the correct IP/DNS/Gateway addresses configured in this file as well.
If I run ps -auwx and grep for dhclient or just dh nothing is returned.
I have tested 2 different boxes that are currently functional dhcp servers and neither of them are detected as dhcp servers in OpenNMS. I am currently running version 1.3.2.
Does anyone have any suggestions for me to try or is this looking like a bug?
you're really *much* better off on the mailing lists, only thing i could suggest, as an opennms user, is that isn't dhcp disabled in the services.xml file by default?
I do have it enabled in the service-configuration.xml file. I didn't think I would get much response here to this particular question, it was just an act of desperation . Thanks for your response.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.