init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE

Bug #1295596 reported by martin suc on 2014-03-21
168
This bug affects 37 people
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)
Medium
Unassigned

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

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in upstart (Ubuntu):
status: New → Confirmed
tags: added: trusty
martin suc (martin-suc) on 2014-09-19
tags: added: utopic

Does it prevent the system to initialize?

Changed in upstart (Ubuntu):
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for upstart (Ubuntu) because there has been no activity for 60 days.]

Changed in upstart (Ubuntu):
status: Incomplete → Expired
Sbisolo (sbisolo) wrote :

Appears in dmesg. System initialization completed without problems (Ubuntu Utopic 14.10)

Changed in upstart (Ubuntu):
status: Expired → Confirmed
importance: Undecided → Medium
peter swain (swine) wrote :

(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

Sistemas (genos) wrote :

Hi:

I have the same error on dmesg "init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE"
We have a server with a volume Group (VG) and two logical volumes (LV). About two 11 days ago it worked fine and we could see information when we run "lvs -a" or "vgs -a".
But if I run "lvs -a" or "vgs -a" or "lvdisplay" or "vgdisplay" I got no information.
Even if I run "lvs --help" or "lvdisplay --help", nothing is printed on screen.
It seems there is an error related to LVM, but We don't know what.

About two 11 days ago it worked fine and we could see information when we run "lvs -a" or "vgs -a", but now nothing is shown.
I restarted the server and try several things but no luck.

Any idea if this problem is related with the error on dmesg?
Any idea to resolve it?

Regards

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers