[Bug 592114] Re: upstart doesn't start cron automatically on boot in lucid for server on amd64

[Clint Byrum]

RoyK, its been difficult to work on this as its not clear how to
reproduce yet. I'm wondering if this has to do with alternative
user/group sources like ldap and such. runlevel 2 happens before the
network is up, so calls to getent() for users that don't exist might
cause a failure. This would affect systems using winbind, NIS, etc. etc.

Can somebody who is affected try changing /etc/init/cron.conf's start on
line to be

start on net-device-up IFACE!=lo

to confirm that?

Also it may help to just move the start on line to after all sysvinit
jobs..

start on stopped rc RUNLEVEL=[2345]

-- 
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/592114

Title:
  upstart doesn't start cron automatically on boot in lucid for server
  on amd64

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: upstart

  1)
  Description:    Ubuntu 10.04 LTS
  Release:        10.04
  2)
  upstart:
    Installed: 0.6.5-6
    Candidate: 0.6.5-6
    Version table:
   *** 0.6.5-6 0
          500 http://in.archive.ubuntu.com/ubuntu/ lucid/main Packages
          100 /var/lib/dpkg/status
  3) Cron should start on system boot and should respawn if it dies accidentally.
  4) On system boot, cron isn't starting by default. Also, somehow cron dies once every 6-7 hours and then it's not respawned by upstart.