[ovirt-users] Hosted Engine-Setup issue additional host

Sven Achtelik Sven.Achtelik at mailpool.us
Sun Apr 26 15:57:06 UTC 2015


On the node that fails to start the ha-broker and ha-agent I'm using:

ovirt-engine-sdk-python.noarch                3.5.2.1-1.el7.centos  @ovirt-3.5-pre
ovirt-host-deploy.noarch                            1.3.1-1.el7                 @ovirt-3.5
ovirt-hosted-engine-ha.noarch                  1.2.5-1.el7.centos     @ovirt-3.5
ovirt-hosted-engine-setup.noarch        1.2.3-1.el7.centos      @ovirt-3.5-pre
ovirt-release35.noarch                                003-1                         @/ovirt-release35


Von: users-bounces at ovirt.org [mailto:users-bounces at ovirt.org] Im Auftrag von Roy Golan
Gesendet: Sonntag, 26. April 2015 16:59
An: users at ovirt.org; Yedidyah Bar David
Betreff: Re: [ovirt-users] Hosted Engine-Setup issue additional host

On 04/26/2015 05:38 PM, Sven Achtelik wrote:
Hi All,

after a successful setup of hosted-engine on the first node I'm having trouble completing it on an additional node. The Setup fails with:
---------------------------------
[ INFO  ] Waiting for the host to become operational in the engine. This may take several minutes...
[ INFO  ] Still waiting for VDSM host to become operational...
[ INFO  ] The VDSM Host is now operational
[ INFO  ] Enabling and starting HA services
[ ERROR ] Failed to execute stage 'Closing up': Command '/bin/systemctl' failed to execute
[ INFO  ] Stage: Clean up
[ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20150426080028.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
---------------------------------
After that the node is added to the cluster and is operational from the GUI, but the hosted  engine broker and agent fail to start with error messages:
----------------------------------
[root at ovirt-node2 ~]# systemctl status ovirt-ha-agent.service -l
ovirt-ha-agent.service - oVirt Hosted Engine High Availability Monitoring Agent
   Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-agent.service; enabled)
   Active: failed (Result: exit-code) since Sun 2015-04-26 08:00:28 CDT; 20min ago
  Process: 5373 ExecStart=/usr/lib/systemd/systemd-ovirt-ha-agent start (code=exited, status=1/FAILURE)

Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd-ovirt-ha-agent[5373]: hdlr = FileHandler(filename, mode)
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd-ovirt-ha-agent[5373]: File "/usr/lib64/python2.7/logging/__init__.py", line 902, in __init__
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd-ovirt-ha-agent[5373]: StreamHandler.__init__(self, self._open())
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd-ovirt-ha-agent[5373]: File "/usr/lib64/python2.7/logging/__init__.py", line 925, in _open
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd-ovirt-ha-agent[5373]: stream = open(self.baseFilename, self.mode)
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd-ovirt-ha-agent[5373]: IOError: [Errno 6] No such device or address: '/dev/stdout'
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd-ovirt-ha-agent[5373]: [FAILED]
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd[1]: ovirt-ha-agent.service: control process exited, code=exited status=1
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd[1]: Failed to start oVirt Hosted Engine High Availability Monitoring Agent.
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd[1]: Unit ovirt-ha-agent.service entered failed state.
-------------------------------------
And
-------------------------------------
[root at ovirt-node2 ~]# systemctl status ovirt-ha-broker
ovirt-ha-broker.service - oVirt Hosted Engine High Availability Communications Broker
   Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-broker.service; enabled)
   Active: failed (Result: exit-code) since Sun 2015-04-26 08:00:28 CDT; 21min ago
  Process: 5359 ExecStart=/usr/lib/systemd/systemd-ovirt-ha-broker start (code=exited, status=1/FAILURE)

Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd-ovirt-ha-broker[5359]: hdlr = FileHandler(filename, mode)
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd-ovirt-ha-broker[5359]: File "/usr/lib64/python2.7/logging/__init__.py", line ...it__
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd-ovirt-ha-broker[5359]: StreamHandler.__init__(self, self._open())
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd-ovirt-ha-broker[5359]: File "/usr/lib64/python2.7/logging/__init__.py", line ...open
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd-ovirt-ha-broker[5359]: stream = open(self.baseFilename, self.mode)
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd-ovirt-ha-broker[5359]: IOError: [Errno 6] No such device or address: '/dev/stdout'

Didi any clue?
the log says it runs as root so I canrule that out

Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd-ovirt-ha-broker[5359]: [FAILED]
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd[1]: ovirt-ha-broker.service: control process exited, code=exited status=1
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd[1]: Failed to start oVirt Hosted Engine High Availability Communications Broker.
Apr 26 08:00:28 ovirt-node2.mgmt.asl.local systemd[1]: Unit ovirt-ha-broker.service entered failed state.
----------------------------------------

The system is a CentOS 7 Setup with SeLinux switched off, no firewall or iptables.  How can I find out which version of ovirt I'm running exactly ? I've had a lock at the logs and read through old bug reports.


the rpm version of ovirt* will be enough I guess


Thank you,

Sven




_______________________________________________

Users mailing list

Users at ovirt.org<mailto:Users at ovirt.org>

http://lists.ovirt.org/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20150426/93829a54/attachment-0001.html>


More information about the Users mailing list