touch-packages team mailing list archive

[xennex82 <ubuntu@xxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 847782 ***
    https://bugs.launchpad.net/bugs/847782

Introducing any kind of script to /etc/network/if-up.d/ that exits with
error for eth0 (or in any case static interfaces?) will cause this
script to fail, ie. introduce the 120 sec boot delay.

I think it is really bad behavior to consider static network up a must
for booting. Static services would already have executed (or tried to
execute) from /etc/network/if-up.d/ and they failed if they came after
the failing script.

In other words run-parts is executed with the fail-on-fail option (the
default).

Should network fail really cause a boot delay?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/845914

Title:
  Failsafe boot delay causes a real delay on every boot

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  Starting today, on each boot there is a non-interruptible long delay,
  apparently 2 minutes exactly. This started after shutting down
  computer normally, after having updated oneiric to the latest packages
  after yesterday.

  I do not have a clue what's causing the actual problem, but changing
  the sleep 120 in /etc/init/failsafe.conf to sleep 1 makes everything
  work again without problems, and returning it to 120 brings the delay
  back to the boot.

  From user point of view the problem is very worrying and confusing,
  since a) it happens also in the safe mode and b) it gives impression
  that either the computer or Ubuntu is simply broken, since also I
  didn't first wait for two full minutes of nothingness, especially
  since the problem also occurred in safe mode. I then (after noticing
  that actually the boot happens if I just wait long enough) started
  making a note about boot messages, and noted that the delay was
  slightly before AppArmor profiles loading and finally guessed to
  change the sleep value in /etc/init/failsafe.

  Filing upstart bug mostly because for whatever real need the failsafe
  boot delay is there (I read a few mailing messages), this shouldn't be
  a possible behavior. Of course, the real root reason might be
  somewhere else that causes this to happen. I think I might have been
  noticed "doing nothing" already before the current value of 120
  seconds that was changed a few days ago in upstart, but I'm not sure.
  This is a new laptop I just got and installed a fresh 64-bit beta 1
  Oneiric.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/845914/+subscriptions