cjwatson jhunt: is anything happening with bug 580319 for 11.04?
jhunt not at the present. I spoke to Daviey earlier and since we are unsure
if it occurs with isc-dhcp (v4) at this stage, we don't think it's in the
running.
jhunt Presumably the milestone might need changing?
cjwatson jhunt: yes,
And what happens with users of Ubuntu 10.04 LTS???
I am running a server with Ubuntu 10.04 *LTS* which I thought that was
supported for up to 5 years and now you are telling me that you will not
fix this because you are replacing dhcp3 with dhcp4 on the next Ubuntu
release? Isn't this crazy?
--
Carlos, apologies if our status change has alarmed you. The status is
invalid in Natty only, because its been removed from natty.
Notice that it is status == Triaged in Lucid which means we plan to
fix it. I've also targetted it at 10.04.3, which is the next stable
point release for 10.04.
This
That finally fixed the issue. I had tested it and now dhcp3-server
starts properly at boot. Thanks!
Nevertheless smbd daemon still fails to bind to the interface and I had
to start it manually.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
dhcp3 is no longer in Natty archive, it's been replaced by a
transitional package to isc-dhcp (v4), marking Natty task invalid for
dhcp3.
** Changed in: dhcp3 (Ubuntu Natty)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Changed in: dhcp3 (Ubuntu Natty)
Milestone: ubuntu-11.04-beta-2 = ubuntu-11.04
** Changed in: upstart (Ubuntu Natty)
Milestone: ubuntu-11.04-beta-2 = ubuntu-11.04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in
Please can someone confirm if they have encountered this with isc-dhcp
(v4)?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in Ubuntu.
https://bugs.launchpad.net/bugs/580319
Title:
dhcp3-server launches before
** Changed in: upstart (Ubuntu Natty)
Milestone: ubuntu-11.04-beta-1 = ubuntu-11.04-beta-2
** Changed in: dhcp3 (Ubuntu Natty)
Milestone: ubuntu-11.04-beta-1 = ubuntu-11.04-beta-2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
I am running a server with Ubuntu 10.04 LTS and I switched eth0 into br0
in order to be able to use it as a bridge for OpenVPN TAP device.
Since I did the change dhcpd refuses to start at boot time with this
message but not only dhcp fails, also Samba stop working.
Both nmbd and smbd daemons
I spoke with Keybuk briefly about changing the startup conditions for
runlevel 2, and he warned that there may be one unforseen circumstance.
Its possible right now to have a sysvinit script that supports a network
interface coming up. Meaning that there may be an interface that will
spin while
** Tags added: server-nro
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
https://bugs.launchpad.net/bugs/580319
Title:
dhcp3-server launches before upstart brings all interface, thus
failing to start
--
** Changed in: upstart (Ubuntu Natty)
Assignee: Canonical Foundations Team (canonical-foundations) = Robbie
Williamson (robbie.w)
** Changed in: upstart (Ubuntu Natty)
Assignee: Robbie Williamson (robbie.w) = James Hunt (jamesodhunt)
** Changed in: upstart (Ubuntu Natty)
If we are going to change the rc-sysinit startup condition, this needs
to happen before beta-1.
** Changed in: upstart (Ubuntu Natty)
Milestone: None = ubuntu-11.04-beta-1
** Changed in: upstart (Ubuntu Natty)
Assignee: (unassigned) = Canonical Foundations Team
(canonical-foundations)
Adding a Lucid task as I've run into this on Lucid.
** Also affects: dhcp3 (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: upstart (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: dhcp3 (Ubuntu Lucid)
Importance: Undecided = Medium
**
** Changed in: dhcp3 (Ubuntu Natty)
Milestone: None = natty-alpha-3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
https://bugs.launchpad.net/bugs/580319
Title:
dhcp3-server launches before upstart brings all
Seems to me that the appropriate time to start dhcpd is when all of the
devices it is configured on are up.
The issue here is that /etc/rc2.d/S* are run after this condition is
met:
start on filesystem and net-device-up IFACE=lo
Because ifup -a is run in parallel with mountall essentially
Adding upstart task since rc-sysinit.conf is owned by the upstart
package, and IMO, its running too soon.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
https://bugs.launchpad.net/bugs/580319
Title:
dhcp3-server
Confirmed here as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
https://bugs.launchpad.net/bugs/580319
Title:
dhcp3-server launches before upstart brings all interface, thus failing to
start
--
I wrote such upstart script :
description Dhcp server
author Rafal Magda
start on filesystem and net-device-up IFACE=br0
stop on runlevel[!2345]
respawn
expect fork
exec dhcpd3
Put in in /etc/init/dhcp.conf
dhcpd will be started when interface br0 will be up.
Iface (br0) should be the same
** Also affects: dhcp3 (Ubuntu Natty)
Importance: Medium
Status: Confirmed
** Changed in: dhcp3 (Ubuntu Natty)
Status: Confirmed = Triaged
** Changed in: dhcp3 (Ubuntu Maverick)
Status: Confirmed = Triaged
--
dhcp3-server launches before upstart brings all interface,
The workaround pointed out by Ian McMichael worked for me, using Ubuntu
Server 10.04 (Lucid).
--
dhcp3-server launches before upstart brings all interface, thus failing to start
https://bugs.launchpad.net/bugs/580319
You received this bug notification because you are a member of Ubuntu
Server
** Also affects: dhcp3 (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: dhcp3 (Ubuntu Maverick)
Status: New = Confirmed
** Changed in: dhcp3 (Ubuntu Maverick)
Importance: Undecided = Medium
--
dhcp3-server launches before upstart brings all interface, thus
Please note that simply making an upstart config file starting on
started networking will NOT work, as that signal is emitted before
bridges are brought up. The problem may be solved by integrating upstart
conversion with Ian McMichael solution, and making dhcp3 start when net-
device-up has been
Confirmed as still being an issue on a fresh installation of Maverick
(10.10) RC AM64 server.
--
dhcp3-server launches before upstart brings all interface, thus failing to start
https://bugs.launchpad.net/bugs/580319
You received this bug notification because you are a member of Ubuntu
Server
As another proposed workaround, I have found that editing /etc/init/rc-
sysinit.conf to change the line:
start on filesystem and net-device-up IFACE=lo
to:
start on filesystem and net-device-up IFACE=br0
also appears to produce the desired result by delaying running of legacy
Perhaps the best way to fix this is to make a
/etc/init/dhcp3-server.conf file for upstart,, and remove
/etc/rc2.d/Sxxdhcp3-server.
--
dhcp3-server launches before upstart brings all interface, thus failing to start
https://bugs.launchpad.net/bugs/580319
You received this bug notification
My work-around for this problem was to remove network-manager, then
configure /etc/networking/interfaces.
--
dhcp3-server launches before upstart brings all interface, thus failing to start
https://bugs.launchpad.net/bugs/580319
You received this bug notification because you are a member of
I made the following (hmm ... ugly ) workaround on my system until an
update for dhcp3 is available:
Install a service for following python script in init.d. The script will
spin until the bridge interface is up and running (looking for the
routing table) and will the start the dhcp server.
Thanks for the bug report, Ill take a closer look at this.
Regards
chuck
** Changed in: dhcp3 (Ubuntu)
Importance: Undecided = Medium
** Changed in: dhcp3 (Ubuntu)
Status: New = Confirmed
--
dhcp3-server launches before upstart brings all interface, thus failing to start
Relevant section of /var/log/syslog showing failure of dhcp3 server to
start
** Attachment added: /var/log/syslog section
http://launchpadlibrarian.net/48427309/syslog
--
dhcp3-server launches before upstart brings all interface, thus failing to start
https://bugs.launchpad.net/bugs/580319
30 matches
Mail list logo
