dhcp issueshttps://gitlab.isc.org/isc-projects/dhcp/-/issues2020-07-03T08:23:53Zhttps://gitlab.isc.org/isc-projects/dhcp/-/issues/24ISC DHCP crash while using failover function2020-07-03T08:23:53ZGhost UserISC DHCP crash while using failover functionI hit a crash in ISC dhcpd while using the failover function. It appears to be a double free error and happens when the connectivity to peer is broken. (crash signature is attached below)
Please review and share if this is seen before.
D...I hit a crash in ISC dhcpd while using the failover function. It appears to be a double free error and happens when the connectivity to peer is broken. (crash signature is attached below)
Please review and share if this is seen before.
Do you need more information from the system/configuration perspective?
Apparently this is happening on a error scenario of select returning failure in omapi_one_dispatch()
394 /* poll once */
395 count = select(max + 1, &r, &w, &x, &now); >>>> (count < 0)
Also, I would like to know whether ISC has a paid support scheme wherein individuals or corporates get expedited support from ISC.
Thanks,
Isaac.
p.s.
<Crash signature>
```
* #0 0x2ae2e774 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:67
* #1 0x2ae302c0 in abort () at abort.c:92
* #2 0x2ae6cb50 in __libc_message (do_abort=<value optimized out>, fmt=0x2af439c0 "*** glibc detected *** %s: %s: 0x%s ***\n") \nat ../sysdeps/unix/sysv/linux/libc_fatal.c:186
* #3 0x2ae73ebc in malloc_printerr (action=3, str=0x2af43c6c "double free or corruption (!prev)", ptr=<value optimized out>) at malloc.c:6267
* #4 0x2ae79d64 in __libc_free (mem=<value optimized out>) at malloc.c:3739
* #5 0x2add1ea8 in mm_chunk_free (handle=<value optimized out>, chunk=0x26d3, caller=<value optimized out>) at mm_chunk.c:186
* #6 0x2add17d8 in mm_free (h=0x528008, ptr=<value optimized out>, caller=<value optimized out>) at mm_main.c:222
* #7 0x0049edf0 in omapi_object_dereference (h=0x7feac178, file=0x4cc2ac "omapip/dispatch.c", line=476) at omapip/alloc.c:695
* #8 0x004a1d30 in omapi_one_dispatch (wo=<value optimized out>, t=0x7feac500) at omapip/dispatch.c:476
* #9 0x0043223c in dispatch () at dispatch.c:92
* #10 0x00462da4 in main (argc=<value optimized out>, argv=<value optimized out>) at dhcpd.c:1555
```
**To Reproduce**
Steps to reproduce the behavior:
1. Run dhcpd with 5 /24 pools and failover function to one peer
2. Connectivity among the peer goes off
3. The server then crashed
**Environment:**
- ISC DHCP version: which release? dhcpd-4.1-ESV-R12-P1
- OS: [e.g. Ubuntu 16.04 x64] Kernel 2.6.32
**Funding its development**
Is there a paid support contract option with ISC?
**Contacting you**
Email: isaactheogaraj@gmail.comOutstandinghttps://gitlab.isc.org/isc-projects/dhcp/-/issues/31ISC DHCP log_fatal aborts while using Failover function2020-07-03T08:23:19ZGhost UserISC DHCP log_fatal aborts while using Failover functionISC DHCP log_fatal aborts were seen in two scenarios while using the failover function. There was a WAN simulator in the testbed across the DHCP failover peers which simulates WAN like latencies/drops on packet exchanges across the Failo...ISC DHCP log_fatal aborts were seen in two scenarios while using the failover function. There was a WAN simulator in the testbed across the DHCP failover peers which simulates WAN like latencies/drops on packet exchanges across the Failover peers
The following scenarios log_fatal were hit
1. dhcpd[21099]: <299801> <21099> <DBUG> |dhcpd| Peer failover-partner: Invalid attempt to move from potential-conflict to communications-interrupted while local state is conflict-done.
2. dhcpd[29438]: <299801> <29438> <DBUG> |dhcpd| Peer failover-partner: Invalid attempt to move from communications-interrupted to communications-interrupted while local state is conflict-done.
```
#0 0x2ae2e774 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:67
#1 0x2ae302c0 in abort () at abort.c:92
#2 0x2ae2687c in __assert_fail (assertion=0x4be094 "0", file=0x4c5184 "dhcpd.c", line=234, function=0x4c5128 "exit_handler") at assert.c:81
#3 0x00460eec in exit_handler () at dhcpd.c:234
#4 0x2ae31d78 in __run_exit_handlers (status=1, listp=0x2af63354, run_list_atexit=true) at exit.c:78
#5 0x2ae31dc0 in exit (status=29438) at exit.c:100
#6 0x004a7424 in log_fatal (fmt=<value optimized out>) at omapip/errwarn.c:102
#7 0x00425594 in dhcp_failover_peer_state_changed (state=0x57131c, msg=<value optimized out>) at failover.c:2202
#8 0x004242bc in dhcp_failover_state_signal (o=0x57131c, name=<value optimized out>, ap=0x6) at failover.c:1468
#9 0x0042390c in dhcp_failover_listener_signal (o=0x576484, name=0x4cc8d8 "message", ap=<value optimized out>) at failover.c:1087
#10 0x004ac0ec in omapi_signal (handle=<value optimized out>, name=0x72fe <Address 0x72fe out of bounds>) at omapip/support.c:281
#11 0x004227c4 in dhcp_failover_link_signal (h=0x5b3824, name=<value optimized out>, ap=<value optimized out>) at failover.c:594
#12 0x004ac0ec in omapi_signal (handle=<value optimized out>, name=0x72fe <Address 0x72fe out of bounds>) at omapip/support.c:281
#13 0x0049faa4 in omapi_connection_reader (h=<value optimized out>) at omapip/buffer.c:259
#14 0x004a1a00 in omapi_one_dispatch (wo=<value optimized out>, t=0x7fbf78e0) at omapip/dispatch.c:514
#15 0x0043223c in dispatch () at dispatch.c:92
#16 0x00462da4 in main (argc=<value optimized out>, argv=<value optimized out>) at dhcpd.c:1555
```
Steps to reproduce the behavior:
1. Run DHCP server across 2 failover peers
2. Have a WAN simulator between the failover peers
**Environment:**
- OS: Linux kernel version 2.6.32
- ISC version dhcpd-4.1-ESV-R12-P1
Email: isaactheogaraj@h=gmail.comOutstandinghttps://gitlab.isc.org/isc-projects/dhcp/-/issues/121ISC-DHCP-Server appears abandoned on Ubuntu focal2021-06-10T16:12:44ZAndrew WelhamISC-DHCP-Server appears abandoned on Ubuntu focalIs the ISC-DHCP-Server for Ubuntu 20.04 abandoned ?
The reason for asking is there appear to be no updates since April 2020, and there are critical issues for example you can't launch ISC-DHCP in a cluster on Focal 20.04.
There are al...Is the ISC-DHCP-Server for Ubuntu 20.04 abandoned ?
The reason for asking is there appear to be no updates since April 2020, and there are critical issues for example you can't launch ISC-DHCP in a cluster on Focal 20.04.
There are also lots of reports left in undecided, with no activity that i can see of.
for example
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118
I've email the maintainer and no response.4.5.0-betahttps://gitlab.isc.org/isc-projects/dhcp/-/issues/128DHCP cluster crashes after a few hours2022-01-13T11:24:31ZRichard LaagerDHCP cluster crashes after a few hours**Describe the bug**
When running a cluster using dhcpd 4.4.1 or 4.4.2, at least with Ubuntu patches, dhcpd crashes after a few hours.
Here are two instances of the crash with the packaged 4.4.1 from Ubuntu 20.04:
```
2020-07-31T06:28:...**Describe the bug**
When running a cluster using dhcpd 4.4.1 or 4.4.2, at least with Ubuntu patches, dhcpd crashes after a few hours.
Here are two instances of the crash with the packaged 4.4.1 from Ubuntu 20.04:
```
2020-07-31T06:28:28.138646-05:00 salmon sh[764]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace
2020-07-31T06:28:28.138704-05:00 salmon sh[764]: #0 0x7fdd3f4b4a4a in ??
2020-07-31T06:28:28.138768-05:00 salmon sh[764]: #1 0x7fdd3f4b4980 in ??
2020-07-31T06:28:28.138809-05:00 salmon sh[764]: #2 0x7fdd3f4f07e1 in ??
2020-07-31T06:28:28.138849-05:00 salmon sh[764]: #3 0x7fdd3f297609 in ??
2020-07-31T06:28:28.138887-05:00 salmon sh[764]: #4 0x7fdd3f3d3103 in ??
2020-07-31T07:02:54.013649-05:00 salmon sh[32432]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace
2020-07-31T07:02:54.013674-05:00 salmon sh[32432]: #0 0x7fb12a7e0a4a in ??
2020-07-31T07:02:54.013693-05:00 salmon sh[32432]: #1 0x7fb12a7e0980 in ??
2020-07-31T07:02:54.013711-05:00 salmon sh[32432]: #2 0x7fb12a81c7e1 in ??
2020-07-31T07:02:54.013728-05:00 salmon sh[32432]: #3 0x7fb12a5c3609 in ??
2020-07-31T07:02:54.013753-05:00 salmon sh[32432]: #4 0x7fb12a6ff103 in ??
```
**To Reproduce**
At this point, I'm not certain that it has to be a cluster configuration, but everyone reporting it (including me) seems to be running a cluster.
It's also not clear how much configuration is relevant either.
For me, it crashes within a couple of hours on the secondary system.
**Expected behavior**
dhcpd does not crash.
**Environment:**
- ISC DHCP version: 4.4.1 as packaged by Ubuntu (4.4.1-2.1ubuntu5) or 4.4.2 with the same Ubuntu patches as 4.4.1-2.1ubuntu5
- OS: Ubuntu 20.04 x64
The version from 18.04, 4.3.5-3ubuntu7.1, is fine.
**Additional Information**
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118
and before that
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1870729
I am not the original reporter of either of those.
**Some initial questions**
**Contacting you**
Here is fine, or the Ubuntu bug, or rlaager@wiktel.com by email or XMPP. BTW, this item on the template references github, but you're now running your own GitLab instance, so that's probably old.4.5.0-betahttps://gitlab.isc.org/isc-projects/dhcp/-/issues/167omshell returns inconsistent results or segfaults2022-05-10T08:29:46ZBill MacAllisteromshell 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 omsh...---
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.
**To Reproduce**
1. Two DHCP servers need to be configured as failover peers.
2. 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
```
**Environment:**
- 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)
**Additional Information**
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?
Certainly
**Contacting you**
bill@ca-zephyr.org
#isc-dhcp IRC channel on freenode, my id is "iiibill"https://gitlab.isc.org/isc-projects/dhcp/-/issues/250Documentation - server-id and failover2022-07-07T06:37:40ZPeter DaviesDocumentation - server-id and failover**Documentation - server-id and failove**r.
We would like to see an article on server-id and how server-id check affects
failover as discussed above, the material in the man page covers this.
Perhaps it can be recycled into the KB i...**Documentation - server-id and failove**r.
We would like to see an article on server-id and how server-id check affects
failover as discussed above, the material in the man page covers this.
Perhaps it can be recycled into the KB if a separate page is really needed.
relates to [RT #15524](https://support.isc.org/Ticket/Display.html?id=15524) and 'lease owned by peer'