Bug 1381666 - Failed to activate service locale and machine
Summary: Failed to activate service locale and machine
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: 3.6.9
Hardware: All
OS: Linux
medium
high
Target Milestone: ovirt-3.6.10
: ---
Assignee: Douglas Schilling Landgraf
QA Contact: dguo
URL:
Whiteboard:
: 1378304 (view as bug list)
Depends On:
Blocks: 1369400
TreeView+ depends on / blocked
 
Reported: 2016-10-04 16:42 UTC by Douglas Schilling Landgraf
Modified: 2017-01-23 14:25 UTC (History)
9 users (show)

Fixed In Version: rhev-hypervisor7-7.3-20161007.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-23 14:25:21 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0185 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update for RHEV 3.6.10 2017-01-24 17:55:58 UTC
oVirt gerrit 64357 0 None MERGED post el7: comment PrivateDevices for systemd-[localed/machined] 2020-10-24 10:25:04 UTC
oVirt gerrit 64361 0 None MERGED post el7: comment PrivateDevices for systemd-[localed/machined] 2020-10-24 10:25:18 UTC

Description Douglas Schilling Landgraf 2016-10-04 16:42:17 UTC
RHEV-H 7.3 boot is failing to start these services affecting the hypervisor TUI and virtual machine start.

Version-Release number of selected component (if applicable):

systemd-python-219-30.el7.x86_64
systemd-sysv-219-30.el7.x86_64
systemd-libs-219-30.el7.x86_64
systemd-219-30.el7.x86_64

dbus-glib-0.100-7.el7.x86_64
dbus-1.6.12-17.el7.x86_64
dbus-libs-1.6.12-17.el7.x86_64
dbus-python-1.1.1-9.el7.x86_64

kernel-3.10.0-506.el7.x86_64

How reproducible:
- Install rhev-hypervisor7-7.3-20160921.1
- After auto-registration, storage added into RHEV-M the virtual machine fails to start.(systemd-machined)
or
- In the TUI Menu it will generate an exception when trying to configure keyboard (systemd-localed.service) 

Additional data:

Selinux doesn't seem related 

# /bin/systemctl status  -l dbus.service
● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
   Active: active (running) since Thu 2016-09-22 03:55:21 UTC; 42min ago
 Main PID: 1162 (dbus-daemon)
   CGroup: /system.slice/dbus.service
           └─1162 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

Sep 22 03:55:21 localhost systemd[1]: Started D-Bus System Message Bus.
Sep 22 03:55:22 localhost systemd[1]: Starting D-Bus System Message Bus...
Sep 22 03:56:12 localhost dbus[1162]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Sep 22 03:56:12 localhost dbus-daemon[1162]: dbus[1162]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Sep 22 03:56:37 localhost dbus[1162]: [system] Failed to activate service 'org.freedesktop.locale1': timed out
Sep 22 03:56:37 localhost dbus-daemon[1162]: dbus[1162]: [system] Failed to activate service 'org.freedesktop.locale1': timed out
Sep 22 03:59:49 localhost dbus[1162]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Sep 22 04:00:14 localhost dbus[1162]: [system] Failed to activate service 'org.freedesktop.locale1': timed out
Sep 22 04:02:32 localhost dbus[1162]: [system] Activating via systemd: service name='org.freedesktop.machine1' unit='dbus-org.freedesktop.machine1.service'
Sep 22 04:02:57 localhost dbus[1162]: [system] Failed to activate service 'org.freedesktop.machine1': timed out


# /bin/systemctl status  -l systemd-machined.service.service
● systemd-machined.service - Virtual Machine and Container Registration Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-machined.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2016-09-22 04:02:32 UTC; 39min ago
     Docs: man:systemd-machined.service(8)
           http://www.freedesktop.org/wiki/Software/systemd/machined
  Process: 18317 ExecStart=/usr/lib/systemd/systemd-machined (code=exited, status=226/NAMESPACE)
 Main PID: 18317 (code=exited, status=226/NAMESPACE)

Sep 22 04:02:32 localhost systemd[1]: Starting Virtual Machine and Container Registration Service...
Sep 22 04:02:32 localhost systemd[1]: systemd-machined.service: main process exited, code=exited, status=226/NAMESPACE
Sep 22 04:02:32 localhost systemd[1]: Failed to start Virtual Machine and Container Registration Service.
Sep 22 04:02:32 localhost systemd[1]: Unit systemd-machined.service entered failed state.
Sep 22 04:02:32 localhost systemd[1]: systemd-machined.service failed.


Exception when trying to configure keyboard via TUI

Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
  File "/usr/lib/python2.7/site-packages/ovirtnode/ovirtfunctions.py", line 1726, in load_keyboard_config
    kbd = osystem.Keyboard()
  File "/usr/lib/python2.7/site-packages/ovirt/node/utils/system.py", line 726, in __init__
    self.kbd = system_config_keyboard.keyboard.Keyboard()
  File "/usr/lib/python2.7/site-packages/system_config_keyboard/keyboard.py", line 60, in __init__
    self._localed_wrap = localed.LocaledWrapper()
  File "/usr/lib/python2.7/site-packages/system_config_keyboard/localed.py", line 48, in __init__
    raise LocaledWrapperError("Failed to get locale object")
system_config_keyboard.localed.LocaledWrapperError: Failed to get locale object


/bin/systemctl status  -l systemd-localed.service
● systemd-localed.service - Locale Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-localed.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2016-09-22 04:40:22 UTC; 715ms ago
     Docs: man:systemd-localed.service(8)
           man:locale.conf(5)
           man:vconsole.conf(5)
           http://www.freedesktop.org/wiki/Software/systemd/localed
  Process: 21147 ExecStart=/usr/lib/systemd/systemd-localed (code=exited, status=226/NAMESPACE)
 Main PID: 21147 (code=exited, status=226/NAMESPACE)

Sep 22 04:40:22 localhost systemd[1]: Starting Locale Service...
Sep 22 04:40:22 localhost systemd[1]: systemd-localed.service: main process exited, code=exited, status=226/NAMESPACE
Sep 22 04:40:22 localhost systemd[1]: Failed to start Locale Service.
Sep 22 04:40:22 localhost systemd[1]: Unit systemd-localed.service entered failed state.
Sep 22 04:40:22 localhost systemd[1]: systemd-localed.service failed.


# ldd /usr/lib/systemd/systemd-localed 
	linux-vdso.so.1 =>  (0x00007ffd3ad24000)
	libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fef783a4000)
	librt.so.1 => /lib64/librt.so.1 (0x00007fef7819c000)
	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fef77f85000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fef77d69000)
	libc.so.6 => /lib64/libc.so.6 (0x00007fef779a8000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fef7862c000)
	libpcre.so.1 => /lib64/libpcre.so.1 (0x00007fef77746000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007fef77542000)

# cat /lib/systemd/system/systemd-localed.service
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Locale Service
Documentation=man:systemd-localed.service(8) man:locale.conf(5) man:vconsole.conf(5)
Documentation=http://www.freedesktop.org/wiki/Software/systemd/localed

[Service]
ExecStart=/usr/lib/systemd/systemd-localed
BusName=org.freedesktop.locale1
CapabilityBoundingSet=
WatchdogSec=3min
PrivateTmp=yes
PrivateDevices=yes
PrivateNetwork=yes
ProtectSystem=yes
ProtectHome=yes

Comment 2 Douglas Schilling Landgraf 2016-10-04 16:45:32 UTC
*** Bug 1378304 has been marked as a duplicate of this bug. ***

Comment 4 Ying Cui 2016-10-10 06:46:59 UTC
Daijie, could you reproduce this issue in QE env.?

Comment 6 dguo 2016-10-11 07:09:54 UTC
Use rhev-hypervisor7-7.3-20161007.0 to verify, no above issue appear

1. Install rhev-hypervisor7-7.3-20161007.0
2. Auto install with the kernel command "storage_init=/dev/sda adminpw=OKr05SbCu3D3g management_server=10.66.150.183 firstboot"
3. The host were added to the engine, create storage and create a virtual machine

Additional info: 
[root@dhcp-8-217 ~]# /bin/systemctl status  -l dbus.service
● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
   Active: active (running) since Tue 2016-10-11 02:05:17 UTC; 1h 37min ago
 Main PID: 1150 (dbus-daemon)
   CGroup: /system.slice/dbus.service
           └─1150 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

Oct 11 02:11:26 dhcp-8-217.nay.redhat.com dbus[1150]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Oct 11 02:11:26 dhcp-8-217.nay.redhat.com dbus[1150]: [system] Successfully activated service 'org.freedesktop.locale1'
Oct 11 02:27:20 dhcp-8-217.nay.redhat.com dbus[1150]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Oct 11 02:27:20 dhcp-8-217.nay.redhat.com dbus[1150]: [system] Successfully activated service 'org.freedesktop.locale1'
Oct 11 02:57:19 dhcp-8-217.nay.redhat.com dbus[1150]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Oct 11 02:57:19 dhcp-8-217.nay.redhat.com dbus[1150]: [system] Successfully activated service 'org.freedesktop.locale1'
Oct 11 03:40:21 dhcp-8-217.nay.redhat.com dbus[1150]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Oct 11 03:40:21 dhcp-8-217.nay.redhat.com dbus[1150]: [system] Successfully activated service 'org.freedesktop.locale1'
Oct 11 03:40:56 dhcp-8-217.nay.redhat.com dbus[1150]: [system] Activating via systemd: service name='org.freedesktop.machine1' unit='dbus-org.freedesktop.machine1.service'
Oct 11 03:40:56 dhcp-8-217.nay.redhat.com dbus[1150]: [system] Successfully activated service 'org.freedesktop.machine1'
[root@dhcp-8-217 ~]# /bin/systemctl status  -l systemd-machined.service.service
● systemd-machined.service.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
[root@dhcp-8-217 ~]# /bin/systemctl status  -l systemd-machined
● systemd-machined.service - Virtual Machine and Container Registration Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-machined.service; static; vendor preset: disabled)
   Active: active (running) since Tue 2016-10-11 03:40:56 UTC; 2min 24s ago
     Docs: man:systemd-machined.service(8)
           http://www.freedesktop.org/wiki/Software/systemd/machined
 Main PID: 21954 (systemd-machine)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-machined.service
           └─21954 /usr/lib/systemd/systemd-machined

Oct 11 03:40:56 dhcp-8-217.nay.redhat.com systemd[1]: Starting Virtual Machine and Container Registration Service...
Oct 11 03:40:56 dhcp-8-217.nay.redhat.com systemd[1]: Started Virtual Machine and Container Registration Service.
Oct 11 03:40:57 dhcp-8-217.nay.redhat.com systemd-machined[21954]: New machine qemu-2-dguovm1.

Besides, No exception were found when trying to configure keyboard via TUI

Comment 7 Laurent Almeras 2016-12-04 12:17:17 UTC
Hi,

I encounter the systemd-localed failure on a fresh Fedora 24 → Fedora 25 update. As there is no output in log about the cause of the failure, after some googling, I read duplicate issue https://bugzilla.redhat.com/show_bug.cgi?id=1378304 and do what it suggested : comment out Protect* and Private* systemd's unit entries to find the problematic one.

For me it was "ProtectHome" one. And it appears it was because my /home folder is a symbolic link. So, something changes between Fedora 24 and Fedora 25 about this ProtectHome as my /home folder already was a symbolic link.

I hope this information may help you to fix or workaround your issue.


Note You need to log in before you can comment on or make changes to this bug.