[Bug 839595] Re: failsafe.conf's 30 second time out is too low

[Scott Moser]

On Thu, 8 Sep 2011, Leo Milano wrote:

> Scott, is this how things are intended to work? My current understanding
> is:
>
>
> * "pre-start exec sleep N" means "wait up to N seconds for the
> preconditions to be satisfied". In this case, these are a network up and
> a fs up. I thought it meant "Wait at least N seconds", but I guess I was
> wrong.

No.  'pre-start exec sleep N' means that it will sleep for N in the
pre-start.  And then nothing happens anywhere else (no 'start').

So basically all this job does is sleep for 120 seconds.

Then, rc.sysinit starts on :
  start on (filesystem and static-network-up) or started failsafe

So, it will start on the filesystem being available (which will happen
very early) and the network is up, *or* 120 seconds have passed since
'failsafe' started.

> * The current change makes the system to wait up to 120 seconds if the
> network is not brought up according to /etc/network/interfaces
>
> I think the latter is something that is not unlikely to happen for
> people who have been using different network managers and upgrading to
> new releases.

What network manager would have said to have that entry in
/etc/network/interfaces ?  Even in the old behavior, having that entry
would stop NetworkManager from working for 'eth0'.
>
> Why would we do this? Isn't it better to proceed with the boot up even
> if the network is not fully up? Why is a network fully up a requirement
> to run rc-sysinit.conf?

Because things in svsvinit often expect (reasonably) to have a network.
Prior to there being upstart, the jobs there would have expected network,
and were sane in that expectation.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/839595

Title:
  failsafe.conf's 30 second time out is too low

Status in “upstart” package in Ubuntu:
  Fix Released

Bug description:
  as far as I can understand, the 30 second sleep in failsafe.conf means
  that /etc/init/rc-sysinit.conf will start within at most 30 seconds of
  'filesystem' and 'ifup lo' having occurred.

  I think that is really to small a number.   You're only safeguarding
  against the case where a user had an entry in /etc/network/interfaces
  that where the device was removed or is not connected.  Thats a very
  rare case.  Increasing the timeout to 60 seconds would make it less
  likely to have a false positive and have rc-sysinit start early.  (Ie,
  the case where a dhcp took 35 seconds).

  The user will only be punished by waiting an additional 30 seconds in
  the case that they have a  misconfigured or out of date
  /etc/network/interfaces.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: upstart 1.3-0ubuntu6
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic x86_64
  Architecture: amd64
  Date: Fri Sep  2 10:02:10 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to oneiric on 2010-11-15 (290 days ago)

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