[Bug 1244197] [NEW] sysv init scripts not started on boot with cloud ubuntu raring

[Krzysztof]

Public bug reported:

Hello,

I'm using up to date vagrant-ubuntu-raring-64 from http://cloud-
images.ubuntu.com/vagrant/raring/current/raring-server-cloudimg-amd64
-vagrant-disk1.box with virtualbox 4.3 and sysv init scripts (nginx,
supervisor, maybe others) are not started after reboot.

I'm not sure what more informations I can provide. This is 100%
reproducible on my system. I traced this to 'console output' in
/etc/init/rc.conf file. If I change this to 'console log' or 'console
none', or if I edit /etc/init.d/rc file and append something like 'exec
>/dev/null; exec 2>/dev/null', then no output goes to /dev/console and
scripts are started. If in /etc/init.d/rc I do something like 'echo asdf
> /dev/console' then, even with 'console none' in /etc/init/rc.conf,
jobs will not start.

For now I'm using 'console log' as workaround. I can provide more
informations if needed.

lsb_release -rd:
Description:    Ubuntu 13.04
Release:        13.04

apt-cache policy nginx:
nginx:
  Installed: 1.2.6-1ubuntu3.2
  Candidate: 1.2.6-1ubuntu3.2
  Version table:
 *** 1.2.6-1ubuntu3.2 0
        500 http://archive.ubuntu.com/ubuntu/ raring-updates/universe amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ raring-security/universe amd64 Packages
        100 /var/lib/dpkg/status
     1.2.6-1ubuntu3 0
        500 http://archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages

what is expected to happen:
nginx should be started after reboot

what happened instead:
nginx was not started after reboot. In fact, no sysv job was started after reboot.

** Affects: upstart (Ubuntu)
     Importance: Undecided
         Status: New

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

Title:
  sysv init scripts not started on boot with cloud ubuntu raring

Status in “upstart” package in Ubuntu:
  New

Bug description:
  Hello,

  I'm using up to date vagrant-ubuntu-raring-64 from http://cloud-
  images.ubuntu.com/vagrant/raring/current/raring-server-cloudimg-amd64
  -vagrant-disk1.box with virtualbox 4.3 and sysv init scripts (nginx,
  supervisor, maybe others) are not started after reboot.

  I'm not sure what more informations I can provide. This is 100%
  reproducible on my system. I traced this to 'console output' in
  /etc/init/rc.conf file. If I change this to 'console log' or 'console
  none', or if I edit /etc/init.d/rc file and append something like
  'exec >/dev/null; exec 2>/dev/null', then no output goes to
  /dev/console and scripts are started. If in /etc/init.d/rc I do
  something like 'echo asdf > /dev/console' then, even with 'console
  none' in /etc/init/rc.conf, jobs will not start.

  For now I'm using 'console log' as workaround. I can provide more
  informations if needed.

  lsb_release -rd:
  Description:    Ubuntu 13.04
  Release:        13.04

  apt-cache policy nginx:
  nginx:
    Installed: 1.2.6-1ubuntu3.2
    Candidate: 1.2.6-1ubuntu3.2
    Version table:
   *** 1.2.6-1ubuntu3.2 0
          500 http://archive.ubuntu.com/ubuntu/ raring-updates/universe amd64 Packages
          500 http://security.ubuntu.com/ubuntu/ raring-security/universe amd64 Packages
          100 /var/lib/dpkg/status
       1.2.6-1ubuntu3 0
          500 http://archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages

  what is expected to happen:
  nginx should be started after reboot

  what happened instead:
  nginx was not started after reboot. In fact, no sysv job was started after reboot.

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