Send dhcp-users mailing list submissions to
        dhcp-users@lists.isc.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
        dhcp-users-requ...@lists.isc.org

You can reach the person managing the list at
        dhcp-users-ow...@lists.isc.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."


Today's Topics:

   1. omapi problems with isc-dhcp-server 4.4.1 (Bill MacAllister)


----------------------------------------------------------------------

Message: 1
Date: Wed, 24 Feb 2021 14:41:30 -0800
From: Bill MacAllister <b...@ca-zephyr.org>
To: dhcp-users@lists.isc.org
Subject: omapi problems with isc-dhcp-server 4.4.1
Message-ID: <fc106984d86c6eb5a03a8a2ef700d...@ca-zephyr.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed

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.

Here is the initial, working, session:

# 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

Here is what I see when the connect fails.  Well, just hangs really.

# omshell
> server localhost
> port 7911
> key omapi_key <the key>
> connect

And then I hit ctrl-c to break out and tried again:

# omshell
> server localhost
> port 7911
> key omapi_key <the key>
> connect
Segmentation fault (core dumped)

Note, the peer to this server is still running Ubuntu 18.04 with 
isc-dhcp-server 4.3.5.  Running the exact same commands on the peer 
works reliably.  (They are using the same python script to drive 
omshell.)  The DHCP server
on the new system appears to be working just fine.

Is this a known problem?  I don't see omapi mentioned in the 4.4.2 
release notes, but is this potentially fixed in the newer version?

Bill


-- 
Bill MacAllister <b...@ca-zephyr.org>


------------------------------

Subject: Digest Footer

_______________________________________________
ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.

dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users


------------------------------

End of dhcp-users Digest, Vol 148, Issue 3
******************************************

Reply via email to