omshell returns inconsistent results or segfaults
name: Bug report about: Create a report to help us improve
Describe the bug I have just built a Ubuntu 20.04 server and installed isc-dhcp-server 4.4.1 on it and I am seeing inconsistent returns from omshell. Initially omshell returns data as expected, but when I exit and re-enter omshell connections fail.
- Two DHCP servers need to be configured as failover peers.
- Issue the following commands using omshell
# omshell > server localhost > port 7911 > key omapi_key <the key> > connect Segmentation fault (core dumped)
Note, the connect works occasionally after a cold server restart, but once the failure starts there is no recovery. The connect does not always result is a segfault. Frequently the connect just hangs.
Expected behavior This is a successful interaction from a version 4.3.5. server.
# omshell > server localhost > port 7911 > key omapi_key <the key> > connect obj: <null> > new failover-state obj: failover-state > set name = "dhcp-failover" obj: failover-state name = "dhcp-failover" > open obj: failover-state name = "dhcp-failover" partner-address = c0:9d:e9:76:e9:55:00:00 partner-port = 00:00:02:07 local-address = 10:9d:e9:76:e9:55:00:00 local-port = 00:00:02:07 max-outstanding-updates = 00:00:00:0a mclt = 00:00:01:2c load-balance-max-secs = 00:00:00:03 load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 partner-state = 00:00:00:02 local-state = 00:00:00:02 partner-stos = 60:36:d0:68 local-stos = 60:36:8b:3b hierarchy = 00:00:00:01 last-packet-sent = 00:00:00:00 last-timestamp-received = 00:00:00:00 skew = 00:00:00:00 max-response-delay = 00:00:00:3c cur-unacked-updates = 00:00:00:00
ISC DHCP version: This failure happens with both the 4.4.1 build from Ubuntu and 4.4.2 built using ubuntu/debian packaging tools.
OS: Ubuntu 20.04 (focal)
Our current test environment is failover peers, one running Ubuntu 18.04 with isc-dhcp 4.3.5 and one running Ubuntu 20.04 with isc-dhcp 4.4.2. From the 18.04 system the OMAPI failover connects are all successful and the DHCP servers on both systems appear to be working as expected.
Some initial questions
- Have you discussed your idea on dhcp-users and/or dhcp-workers mailing lists? We have brought up the issued on the user lists and not gotten any response. I have also submitted a bug to Ubuntu without response. https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1916931
Describe the solution you'd like I need to be able to determine the failover state of a DHCP server and to be able to set a server into failover when needed.
Describe alternatives you've considered We have considered moving to the Kea server, but we have an infrastructure built around ISC DHCP LDAP backend functionality. Since that is a big enough change if we cannot get this working we will take a look at what DHCP servers are available in addition to the Kea server.
Funding its development ISC DHCP is run by ISC, which is a small non-profit organization without any government funding or any permanent sponsorship organizations. Are you able and willing to participate financially in the development costs?
We would consider it, but it appears that ISC is not interested in developing ISC DHCP any further.
Participating in development Are you willing to take part in the design discussions? Are you willing to test an unreleased engineering code?
Contacting you firstname.lastname@example.org #isc-dhcp IRC channel on freenode, my id is "iiibill"