[Bug 1295596] Re: init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE

2017-12-11 Thread Sistemas
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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295596

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1295596] Re: init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE

2016-09-05 Thread peter swain
(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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295596

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1295596] Re: init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE

2015-01-07 Thread Alberto Salvia Novella
** Changed in: upstart (Ubuntu)
   Status: Expired => Confirmed

** Changed in: upstart (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295596

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1295596] Re: init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE

2015-01-07 Thread Sbisolo
Appears in dmesg. System initialization completed without problems
(Ubuntu Utopic 14.10)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295596

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1295596] Re: init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE

2015-01-05 Thread Launchpad Bug Tracker
[Expired for upstart (Ubuntu) because there has been no activity for 60
days.]

** Changed in: upstart (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295596

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1295596] Re: init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE

2014-11-05 Thread Alberto Salvia Novella
Does it prevent the system to initialize?

** Changed in: upstart (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295596

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1295596] Re: init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE

2014-09-19 Thread martin suc
** Tags added: utopic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295596

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1295596] Re: init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE

2014-04-16 Thread Brian Murray
** Tags added: trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295596

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1295596] Re: init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE

2014-04-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: upstart (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295596

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs