[ovirt-users] ovirt-ha-broker issue after upgrade CentOS 7.1 => 7.2 and oVirt 3.6.0 => 3.6.1

Simone Tiraboschi stirabos at redhat.com
Fri Dec 18 00:50:42 UTC 2015


On Fri, Dec 18, 2015 at 12:32 AM, Matthew Trent <
Matthew.Trent at lewiscountywa.gov> wrote:

> (Sorry if this reply doesn't thread properly. Just subscribed to reply to
> this topic.)
>
> I'm also experiencing this issue. Just upgraded to the latest packages and
> both ovirt-ha-agent and ovirt-ha-broker pause for a long time when being
> started, then timeout with errors.
>

Please try manually reverting this patch https://gerrit.ovirt.org/#/c/50662/
by removing the lines that start with PIDFile= from
/usr/lib/systemd/system/ovirt-ha-broker.service and
/usr/lib/systemd/system/ovirt-ha-agent.service
Then systemctl daemon-reload and restart the services



>
> [root at ovirt2 ~]# systemctl start ovirt-ha-broker
> Job for ovirt-ha-broker.service failed because a timeout was exceeded. See
> "systemctl status ovirt-ha-broker.service" and "journalctl -xe" for details.
> [root at ovirt2 ~]# systemctl start ovirt-ha-agent
> Job for ovirt-ha-agent.service failed because a timeout was exceeded. See
> "systemctl status ovirt-ha-agent.service" and "journalctl -xe" for details.
>
>
> Dec 17 15:27:53 ovirt2 systemd: Failed to start oVirt Hosted Engine High
> Availability Communications Broker.
> Dec 17 15:27:53 ovirt2 systemd: Unit ovirt-ha-broker.service entered
> failed state.
> Dec 17 15:27:53 ovirt2 systemd: ovirt-ha-broker.service failed.
> Dec 17 15:27:53 ovirt2 systemd: ovirt-ha-broker.service holdoff time over,
> scheduling restart.
> Dec 17 15:27:53 ovirt2 systemd: Starting oVirt Hosted Engine High
> Availability Communications Broker...
> Dec 17 15:27:53 ovirt2 systemd-ovirt-ha-broker: Starting ovirt-ha-broker:
> [  OK  ]
> Dec 17 15:27:53 ovirt2 systemd: PID 21125 read from file
> /run/ovirt-hosted-engine-ha/broker.pid does not exist or is a zombie.
> Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service stop-final-sigterm
> timed out. Killing.
> Dec 17 15:29:22 ovirt2 systemd: Failed to start oVirt Hosted Engine High
> Availability Monitoring Agent.
> Dec 17 15:29:22 ovirt2 systemd: Unit ovirt-ha-agent.service entered failed
> state.
> Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service failed.
> Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service holdoff time over,
> scheduling restart.
> Dec 17 15:29:23 ovirt2 systemd: ovirt-ha-broker.service start operation
> timed out. Terminating.
> Dec 17 15:29:24 ovirt2 systemd: Failed to start oVirt Hosted Engine High
> Availability Communications Broker.
> Dec 17 15:29:24 ovirt2 systemd: Unit ovirt-ha-broker.service entered
> failed state.
> Dec 17 15:29:24 ovirt2 systemd: ovirt-ha-broker.service failed.
> Dec 17 15:29:24 ovirt2 systemd: Starting oVirt Hosted Engine High
> Availability Monitoring Agent...
> Dec 17 15:29:24 ovirt2 systemd-ovirt-ha-agent: Starting ovirt-ha-agent: [
> OK  ]
> Dec 17 15:29:24 ovirt2 systemd: PID 21288 read from file
> /run/ovirt-hosted-engine-ha/agent.pid does not exist or is a zombie.
> Dec 17 15:29:24 ovirt2 systemd: ovirt-ha-broker.service holdoff time over,
> scheduling restart.
> Dec 17 15:29:24 ovirt2 systemd: Starting oVirt Hosted Engine High
> Availability Communications Broker...
> Dec 17 15:29:25 ovirt2 systemd-ovirt-ha-broker: Starting ovirt-ha-broker:
> [  OK  ]
> Dec 17 15:29:25 ovirt2 systemd: PID 21304 read from file
> /run/ovirt-hosted-engine-ha/broker.pid does not exist or is a zombie.
>
>
> --
> Matthew Trent
> Network Engineer
> Lewis County IT Services
> 360.740.1247 - Helpdesk
> 360.740.3343 - Direct line
> _______________________________________________
> Users mailing list
> 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/20151218/0ed88e43/attachment-0001.html>


More information about the Users mailing list