Hi Jonathan - thanks for reporting this issue. From the attachments, it looks like your system may not have a /var/run and/or /run? Can you attach your /etc/fstab?
Also, do you only see this issue when you ssh into the systems to upgrade? To establish this, please can you run 'sudo telinit u' both via ssh and via a normal login. This command will request upstart restarts itself and if your systems remain responsive, the restart has worked. However, to get more details, please could you run the following for both scenarios: - boot system *without* 'quiet' and 'splash' - login directly or via ssh - clear ring buffer $ sudo dmesg -c >/dev/null - put upstart into debug mode $ sudo initctl log-priority debug - restart upstart $ sudo telinit u If the system is still responding, please can you attach: - /var/log/syslog - the output of 'dmesg' - the file /var/log/upstart/upstart.state if it exists -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1154040 Title: Upgrading to 1.7 on raring caused system to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1154040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
