[ovirt-users] Failed to execute stage 'Environment setup': Command'/bin/systemctl' failed to execute
Jürgen Brandl
lists at jbrandl.com
Sun Nov 30 12:12:32 UTC 2014
Hello,
I did a bit of debugging the issue, here are all the errors, which i found
useful:
# yum install ovirt-hosted-engine-setup
[...]
Installing : vdsm-4.16.7-1.gitdb83943.el7.x86_64
277/281
SELinux: Could not downgrade policy file
/etc/selinux/targeted/policy/policy.29, searching for an older version.
SELinux: Could not open policy file <=
/etc/selinux/targeted/policy/policy.29: No such file or directory
/sbin/load_policy: Can't load policy: No such file or directory
libsemanage.semanage_reload_policy: load_policy returned error code 2.
SELinux: Could not downgrade policy file
/etc/selinux/targeted/policy/policy.29, searching for an older version.
SELinux: Could not open policy file <=
/etc/selinux/targeted/policy/policy.29: No such file or directory
/sbin/load_policy: Can't load policy: No such file or directory
libsemanage.semanage_reload_policy: load_policy returned error code 2.
Traceback (most recent call last):
File "/usr/bin/vdsm-tool", line 209, in main
return tool_command[cmd]["command"](*args)
File "/usr/lib/python2.7/site-packages/vdsm/tool/seboolsetup.py", line
66, in sebool_config
setup_booleans(True)
File "/usr/lib/python2.7/site-packages/vdsm/tool/seboolsetup.py", line
53, in setup_booleans
sebool_obj.finish()
File "/usr/lib/python2.7/site-packages/seobject/__init__.py", line 281,
in finish
self.commit()
File "/usr/lib/python2.7/site-packages/seobject/__init__.py", line 274,
in commit
raise ValueError(_("Could not commit semanage transaction"))
ValueError: Could not commit semanage transaction
[...]
# hosted-engine --deploy
[ INFO ] Stage: Initializing
Continuing will configure this host for serving as hypervisor and
create a VM where you have to install oVirt Engine afterwards.
Are you sure you want to continue? (Yes, No)[Yes]:
[ INFO ] Generating a temporary VNC password.
[ INFO ] Stage: Environment setup
Configuration files: []
Log file:
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20141130125118-ax6wm0.log
Version: otopi-1.3.0 (otopi-1.3.0-1.el7)
[ INFO ] Hardware supports virtualization
[ INFO ] Stage: Environment packages setup
[ INFO ] Stage: Programs detection
[ INFO ] Stage: Environment setup
[ ERROR ] Failed to execute stage 'Environment setup': Command
'/bin/systemctl' failed to execute
[ INFO ] Stage: Clean up
[ INFO ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf'
[ INFO ] Answer file '/etc/ovirt-hosted-engine/answers.conf' has been
updated
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
# cat
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20141130125118-ax6wm0.log
[...]
2014-11-30 12:51:22 DEBUG otopi.plugins.otopi.services.systemd
plugin.execute:866 execute-output: ('/bin/systemctl', 'start',
'vdsmd.service') stderr:
Job for vdsmd.service failed. See 'systemctl status vdsmd.service' and
'journalctl -xn' for details.
2014-11-30 12:51:22 DEBUG otopi.context context._executeMethod:152 method
exception
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in
_executeMethod
method['method']()
File
"/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/system/vdsmenv.py",
line 155, in _late_setup
state=True
File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 138, in
state
'start' if state else 'stop'
File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 77, in
_executeServiceCommand
raiseOnError=raiseOnError
File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 871, in
execute
command=args[0],
RuntimeError: Command '/bin/systemctl' failed to execute
[...]
# journalctl -xn
-- Logs begin at Sat 2014-11-29 22:42:03 CET, end at Sun 2014-11-30
12:54:48 CET. --
Nov 30 12:51:26 CentOS-70-64-minimal systemd[1]: Starting Virtual Desktop
Server Manager...
-- Subject: Unit vdsmd.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit vdsmd.service has begun starting up.
Nov 30 12:51:26 CentOS-70-64-minimal systemd[1]: vdsmd.service start
request repeated too quickly, refusing to start.
Nov 30 12:51:26 CentOS-70-64-minimal systemd[1]: Failed to start Virtual
Desktop Server Manager.
-- Subject: Unit vdsmd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit vdsmd.service has failed.
--
-- The result is failed.
Nov 30 12:51:26 CentOS-70-64-minimal systemd[1]: Unit vdsmd.service entered
failed state.
# systemctl status vdsmd
vdsmd.service - Virtual Desktop Server Manager
Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)
Active: failed (Result: start-limit) since Sun 2014-11-30 12:51:26 CET;
5min ago
Process: 26400 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh
--pre-start (code=exited, status=1/FAILURE)
Nov 30 12:51:26 CentOS-70-64-minimal systemd[1]: vdsmd.service: control
process exited, code=exited status=1
Nov 30 12:51:26 CentOS-70-64-minimal systemd[1]: Failed to start Virtual
Desktop Server Manager.
Nov 30 12:51:26 CentOS-70-64-minimal systemd[1]: Unit vdsmd.service entered
failed state.
Nov 30 12:51:26 CentOS-70-64-minimal systemd[1]: vdsmd.service holdoff time
over, scheduling restart.
Nov 30 12:51:26 CentOS-70-64-minimal systemd[1]: Stopping Virtual Desktop
Server Manager...
Nov 30 12:51:26 CentOS-70-64-minimal systemd[1]: Starting Virtual Desktop
Server Manager...
Nov 30 12:51:26 CentOS-70-64-minimal systemd[1]: vdsmd.service start
request repeated too quickly, refusing to start.
Nov 30 12:51:26 CentOS-70-64-minimal systemd[1]: Failed to start Virtual
Desktop Server Manager.
Nov 30 12:51:26 CentOS-70-64-minimal systemd[1]: Unit vdsmd.service entered
failed state.
# systemctl start vdsmd
Job for vdsmd.service failed. See 'systemctl status vdsmd.service' and
'journalctl -xn' for details.
# journalctl -xn
-- Logs begin at Sat 2014-11-29 22:42:03 CET, end at Sun 2014-11-30
13:01:05 CET. --
Nov 30 13:01:05 CentOS-70-64-minimal vdsmd_init_common.sh[26770]: vdsm:
stopped during execute unified_network_persistence_upgrade task (task
returned with error code 1).
Nov 30 13:01:05 CentOS-70-64-minimal systemd[1]: vdsmd.service: control
process exited, code=exited status=1
Nov 30 13:01:05 CentOS-70-64-minimal systemd[1]: Failed to start Virtual
Desktop Server Manager.
-- Subject: Unit vdsmd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit vdsmd.service has failed.
--
-- The result is failed.
# vdsm-tool upgrade-unified-persistence
MainThread::ERROR::2014-11-30
13:06:03,633::upgrade::95::upgrade::(apply_upgrade) Failed to run
upgrade-unified-persistence
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/tool/upgrade.py", line 93, in
apply_upgrade
upgrade.run(ns, args)
File "/usr/lib/python2.7/site-packages/vdsm/tool/unified_persistence.py",
line 170, in run
run()
File "/usr/lib/python2.7/site-packages/vdsm/tool/unified_persistence.py",
line 44, in run
networks, bondings = _getNetInfo()
File "/usr/lib/python2.7/site-packages/vdsm/tool/unified_persistence.py",
line 130, in _getNetInfo
netinfo = NetInfo()
File "/usr/lib/python2.7/site-packages/vdsm/netinfo.py", line 903, in
__init__
_netinfo = get()
File "/usr/lib/python2.7/site-packages/vdsm/netinfo.py", line 822, in get
d['nics'][dev.name] = _nicinfo(dev, paddr, ipaddrs)
File "/usr/lib/python2.7/site-packages/vdsm/netinfo.py", line 653, in
_nicinfo
info = _devinfo(link, ipaddrs)
File "/usr/lib/python2.7/site-packages/vdsm/netinfo.py", line 681, in
_devinfo
ipv4addr, ipv4netmask, ipv4addrs, ipv6addrs = getIpInfo(link.name,
ipaddrs)
File "/usr/lib/python2.7/site-packages/vdsm/netinfo.py", line 370, in
getIpInfo
ipv4addr, prefix = addr['address'].split('/')
ValueError: need more than 1 value to unpack
Any suggestions?
Jürgen
2014-11-30 3:09 GMT+01:00 鎖心□愛妳 <mzcwlong at vip.qq.com>:
> hi，guy：
> Can you provide the log file in the
> /var/log/ovirt-hosted-engine-setup/ directory?
>
>
>
> ------------------ 原始邮件 ------------------
> *发件人:* Jürgen Brandl <lists at jbrandl.com>
> *发送时间:* 2014年11月30日 03:57
> *收件人:* users <users at ovirt.org>
> *主题:* [ovirt-users] Failed to execute stage 'Environment setup':
> Command'/bin/systemctl' failed to execute
>
> Hey,
>
> I'm desperately trying to install oVirt hosted engine on a fresh centos 7
> system.
> After the following steps:
>
> [root@ Centos7 ~]# yum localinstall -y
> http://resources.ovirt.org/pub/yum-repo/ovirt-release35.rpm
> [root@ Centos7 ~]# yum install -y ovirt-hosted-engine-setup screen
> glusterfs-server nfs-utils vdsm-gluster system-storage-manager
>
> [user at Centos7 ~]$ sudo su
>
> [root at WesterOS ~]# screen
> >hosted-engine --deploy
>
> I get the following error log:
>
> [ INFO ] Stage: Initializing
>
> Continuing will configure this host for serving as hypervisor
> and create a VM where you have to install oVirt Engine afterwards.
>
> Are you sure you want to continue? (Yes, No)[Yes]:
>
> [ INFO ] Generating a temporary VNC password.
>
> [ INFO ] Stage: Environment setup
>
> Configuration files: []
>
> Log file:
> /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20141129204526-sl1lwm.log
>
> Version: otopi-1.3.0 (otopi-1.3.0-1.el7)
>
> [ INFO ] Hardware supports virtualization
>
> [ INFO ] Stage: Environment packages setup
>
> [ INFO ] Stage: Programs detection
>
> [ INFO ] Stage: Environment setup
>
> [ ERROR ] Failed to execute stage 'Environment setup': Command
> '/bin/systemctl' failed to execute
>
> [ INFO ] Stage: Clean up
>
> [ INFO ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf'
>
> [ INFO ] Answer file '/etc/ovirt-hosted-engine/answers.conf' has been
> updated
>
> [ INFO ] Stage: Pre-termination
>
> [ INFO ] Stage: Termination
>
> I have neither firewalld nor networkmanager running and still get this
> error after a reboot.
> Please help me.
>
> Jürgen
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20141130/0dd41686/attachment-0001.html>
More information about the Users
mailing list