[Bug 1564220] Comment bridged from LTC Bugzilla

bugproxy bugproxy at us.ibm.com
Wed May 18 10:49:33 UTC 2016

*** This bug is a duplicate of bug 1565617 ***

------- Comment From brsriniv at in.ibm.com 2016-05-18 06:45 EDT-------
Hello Canonical,

Do you need more information from us? Can you please let us know if
there are any updates on this issue?


You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.

  ISST-LTE:pVM:pinelp3:ubuntu 16.04: systemctl daemon-reload failed in
  emergency mode

Status in systemd package in Ubuntu:

Bug description:
  == Comment: #0 - Ping Tian Han <pthan at cn.ibm.com> - 2016-03-24 23:19:51 ==
  ---Problem Description---
  After dropping into emergency mode and do some modification to the system's config files, I want to let systemd reload them but failed:

  root at pinelp3:~# systemctl daemon-reload
  Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)
  root at pinelp3:~#

  This command works in normal mode though.
  Contact Information = Ping Tian Han/pthan at cn.ibm.com, 	Mikhail Afanasiev/epidemike at us.ibm.com 
  ---uname output---
  Linux pinelp3 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:06:23 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
  Machine Type = IBM,8408-E8E,lpar 
  A debugger was configured, however the system did not enter into the debugger
  ---Steps to Reproduce---
   1. adding a nonexistent  partition entry in /etc/fstab:
  /dev/mapper/mpathw-part3 /fs_test/mapper/mpathw-part3        xfs     defaults       1 2
  2. reboot the system
  3. drop into emergency mode:

  Give root password for maintenance
  (or press Control-D to continue):
  root at pinelp3:~#

  4. removee the nonexistent partition entry from /etc/fstab
  5. run 'systemctl daemon-reload'

  Userspace tool common name: systemd 

  Userspace rpm: systemd 
  The userspace tool has the following bit modes: 64-bit 

  Userspace tool obtained from project website:  na 
  *Additional Instructions for Ping Tian Han/pthan at cn.ibm.com, 	Mikhail Afanasiev/epidemike at us.ibm.com: 
  -Post a private note with access information to the machine that the bug is occuring on.
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - Ping Tian Han <pthan at cn.ibm.com> - 2016-03-30 21:39:23 ==

  For how to drop into the emergency mode, I just add a nonexistent
  partition item, something like

  /dev/nonexistent1 /nonexistent1        xfs     defaults       1 2

  then reboot the system. So systemd won't find the device and will drop
  into emergency mode.


To manage notifications about this bug go to:

More information about the foundations-bugs mailing list