See https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118
still no acknowledgement
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1870729
Title:
DHCP Server
This bug is marked fixed release. As I suggested in comment #13, please
file a new bug. This will allow you to use apport to upload any crash
information/etc that will assist developers in fixing this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Problem still exists even after disabling apparmor completely:
May 14 09:46:18 dc sh[4241]: ../../../../lib/isc/unix/socket.c:3361:
INSIST(!sock->pending_send) failed, back trace
May 14 09:46:18 dc sh[4241]: #0 0x7fdeeb0dca4a in ??
May 14 09:46:18 dc sh[4241]: #1 0x7fdeeb0dc980 in ??
May 14
This bug was fixed in the package isc-dhcp - 4.4.1-2.1ubuntu5
---
isc-dhcp (4.4.1-2.1ubuntu5) focal; urgency=medium
* debian/apparmor/usr.sbin.dhcpd: also allow write on /proc/*/comm and
/proc/*/task/*/comm (LP: #1870729)
-- Jamie Strandboge Fri, 10 Apr 2020 17:21:12 +
** Also affects: isc-dhcp (Ubuntu Focal)
Importance: High
Assignee: Jamie Strandboge (jdstrand)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
I will update the policy for the write access. I suggest removing the
crash file in /var/crash, then if you see the crash again, file a new
bug with the crash information (eg, apport-cli if on a server) so it can
be analyzed.
--
You received this bug notification because you are a member of
ran for a few hours then crashed with
ERROR: apport (pid 3789) Fri Apr 10 15:34:35 2020: called for pid 1900, signal
6, core limit 0, dump mode 2
ERROR: apport (pid 3789) Fri Apr 10 15:34:35 2020: not creating core for pid
with dump mode of 2
ERROR: apport (pid 3789) Fri Apr 10 15:34:35 2020:
dhcp-primary started to log the same errors so applied the same fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1870729
Title:
DHCP Server regularly killed
FIXED
on the backup DHCP server I kept seeing
Apr 10 11:10:08 dhcp-backup kernel: [ 86.045487] audit: type=1400
audit(1586513408.708:44): apparmor="DENIED" operation="open"
profile="/usr/sbin/dhcpd" name="/proc/1404/task/1417/comm" pid=1404
comm="dhcpd" requested_mask="w" denied_mask="w"
Just checked a day later, only one kill on the primary dhcp server, 2nd
server will not start
** Changed in: isc-dhcp (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
incorrect statement above, since i have been bouncing the dhcp servers
to try to find a pattern, the primary dhcp server logged a single error
but continues to work
Apr 8 06:32:36 dhcp-primary systemd[1]: isc-dhcp-server.service: Main
process exited, code=killed, status=6/ABRT
--
You received
I tried this.
If you stop the primary dhcp server
Start the backup (This time it works)
Restart the primary dhcp server
Secondary dhcp server fails with the error
Apr 8 06:26:00 dhcp-backupl dhcpd[1360]: failover peer failover-partner: peer
moves from communications-interrupted to normal
Apr
The primary DHCP server is now fine, but the secondary won't start any more
(although it did immediately after patching)
I now get the error
Apr 8 06:14:11 dhcp-backup dhcpd[1181]:
Apr 8 06:14:11 dhcp-backup dhcpd[1181]: Sending on
Socket/fallback/fallback-net
Apr 8 06:14:11 dhcp-backup
Now that there are no apparmor denials, this sounds like something for
the server team to take a look at. Can you file a new bug since this one
was used to address the apparmor denials? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
The bug is still present for me with
ii isc-dhcp-server 4.4.1-2.1ubuntu4
amd64ISC DHCP server for automatic IP address assignment.
apparmor rules are up to date with:
owner @{PROC}/[0-9]*/comm r,
owner @{PROC}/[0-9]*/task/[0-9]*/comm r,
This bug was fixed in the package isc-dhcp - 4.4.1-2.1ubuntu4
---
isc-dhcp (4.4.1-2.1ubuntu4) focal; urgency=medium
* debian/apparmor/usr.sbin.dhcpd: allow owner read on /proc/*/comm and
/proc/*/task/*/comm (LP: #1870729)
-- Jamie Strandboge Mon, 06 Apr 2020 21:58:35 +
4.4.1-2.1ubuntu4 was uploaded for the above. Please let us know if it
doesn't fix the issue for you.
** Changed in: isc-dhcp (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Does adjusting /etc/apparmor.d/usr.sbin.dhcpd to have:
owner @{PROC}/[0-9]*/comm r,
owner @{PROC}/[0-9]*/task/[0-9]*/comm r,
resolve the issue for you? Be sure to load the policy into the kernel
with: sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.dhcpd before
performing your testing.
**
18 matches
Mail list logo
