[Bug 1295596] Re: init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE
peter swain
swine at pobox.com
Mon Sep 5 23:54:49 UTC 2016
(not related to the issue, but to a hang just after this message
appears, for which people may be googling the startpar-bridge message)
I found this continually as the last suspicious event before hang on an arm64 with an old 14.04 nfsroot system.
After this it would always hang at "nfs: server xx.xx.xx.xx not responding, still trying".
System used to work, but I was using this nfsroot on a new board.
It had hung partway thru apt-upgrade to modern 14.04 packages (before intended update to 16.10).
That hang was due to kernel issues on the new hardware.
Root cause of the hang was /run/shm being a directory, not a symlink.
Removing /nfsroot/run/shm fixed the hang.
Somewhere in the evolution of 14.04 the implementation of /run/shm
apparently changed, and interrupting update leaves system unbootable
--
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/1295596
Title:
init: Failed to obtain startpar-bridge instance: Unknown parameter:
INSTANCE
Status in upstart package in Ubuntu:
Confirmed
Bug description:
Hi,
I have came accross the failure of init in /var/log/dmesg
init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE
# ---
Ubuntu development branch Trusty 14.04
kernel Linux 3.13.0-18-lowlatency #38-Ubuntu SMP PREEMPT Mon Mar 17 22:08:57 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
apt-cache policy upstart
upstart:
Installed: 1.12.1-0ubuntu1
Candidate: 1.12.1-0ubuntu1
Version table:
*** 1.12.1-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
Kind Regards,
Martin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1295596/+subscriptions
More information about the foundations-bugs
mailing list