I have had this issue off and on for a couple of weeks. After much tearing of
hair and gnashing of teeth I believe I fixed it. In the upstart configuration
for isc-dhcp-server there is no stanza of the form:
/lib/init/apparmor-profile-load usr.sbin.dhcpd
I don't know about systems running NM
I'm running 4.2.4-1ubuntu10.3 and still experiencing the error. Adding
'network packet raw' to usr.sbin.dhcpd fixed the issue for now.
have I somehow skipped the apparmor config during the update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: isc-dhcp (Ubuntu)
Status: New = Triaged
** Changed in: isc-dhcp (Ubuntu)
Importance: Undecided = High
** Also affects: isc-dhcp (Ubuntu Quantal)
Importance: Undecided
Status: New
** Changed in: isc-dhcp (Ubuntu)
Status: Triaged = Fix Released
**
For anyone affected by this bug and who can't wait for the bugfix to
land, you can simply edit /etc/apparmor.d/usr.sbin.dhcpd and apply the
following diff, then do sudo /etc/init.d/apparmor reload.
diff -Nru isc-dhcp-4.2.4/debian/apparmor-profile.dhcpd
Hello cp, or anyone else affected,
Accepted isc-dhcp into quantal-proposed. The package will build now and
be available at http://launchpad.net/ubuntu/+source/isc-
dhcp/4.2.4-1ubuntu10.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
The fix was independently verified by two people. What should we have
done differently to catch this during verification?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171838
Title:
Last nights
Well, I should have noticed it when reviewing the patch as the patch
quite clearly uses raw sockets...
To catch this in testing, we'd have required a larger hardware pool to
hit both machines with checksum offloading and without, also check that
the test results where from machine where apparmor
Enabled proposed and apt-get install isc-dhcp-server isc-dhcp-client
and it works.
# ps auwx|grep dhcp
dhcpd 9201 0.0 0.1 7792 4892 ?Ss 20:37 0:00 dhcpd -user
dhcpd -group dhcpd -f -q -4 -pf /run/dhcp-server/dhcpd.pid -cf
/etc/ltsp/dhcpd.conf
Thanks!
--
You received
cp: Did you have a problem with the first update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171838
Title:
Last nights isc-dhcp-server update fails to start
To manage notifications about this
kitterman: Yes 4.2.4-1ubuntu10.2 failed to start. I reported this bug.
4.2.4-1ubuntu10.3 is currently working fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171838
Title:
Last nights
Excellent. Based on that and that this is a regression in updates, I'll
release the package early.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package isc-dhcp - 4.2.4-1ubuntu10.3
---
isc-dhcp (4.2.4-1ubuntu10.3) quantal-proposed; urgency=low
* Allow network packet raw in the apparmor profile for dhcpd.
This fixes dhcpd failing to start when used on InfiniBand and on setups
that do
12 matches
Mail list logo