*** This bug is a duplicate of bug 1565617 ***
https://bugs.launchpad.net/bugs/1565617
@brsriniv: From my point of view this is fixed in 16.04 LTS, the master
bug of this (bug 1565617) is closed. What is still missing?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1564220
Title:
ISST-LTE:pVM:pinelp3:ubuntu 16.04: systemctl daemon-reload failed in
emergency mode
Status in systemd package in Ubuntu:
New
Bug description:
== Comment: #0 - Ping Tian Han <[email protected]> - 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@pinelp3:~# systemctl daemon-reload
Error getting authority: Error initializing authority: Could not connect: No
such file or directory (g-io-error-quark, 1)
root@pinelp3:~#
This command works in normal mode though.
Contact Information = Ping Tian Han/[email protected], Mikhail
Afanasiev/[email protected]
---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
---Debugger---
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@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/[email protected], Mikhail
Afanasiev/[email protected]:
-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 <[email protected]> - 2016-03-30 21:39:23 ==
Hi,
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.
thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1564220/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
