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

2015-12-18 Thread Bello Florent
 

Yes it's solved for me too. Thanks for your help 


Cordialement,

Florent BELLO
Service
Informatique
informati...@ville-kourou.fr
0594 22 31 22
Mairie de Kourou


Le 17/12/2015 22:08, Matthew Trent a écrit : 

> Yes! That did it.
All the errors are gone, and HA seems to be functioning normally. Thanks
much! 
> 
> --
> Matthew Trent 
> Network Engineer
> Lewis County IT
Services ​ 
> 
> -
> 
> FROM: Simone
Tiraboschi <stira...@redhat.com>
> SENT: Thursday, December 17, 2015
4:50 PM
> TO: Matthew Trent
> CC: users@ovirt.org
> SUBJECT: Re:
[ovirt-users] ovirt-ha-broker issue after upgrade CentOS 7.1 => 7.2 and
oVirt 3.6.0 => 3.6.1 
> 
> On Fri, Dec 18, 2015 at 12:32 AM, Matthew
Trent <matthew.tr...@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/ [2] 
>
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@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@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@ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users [1]
> 
>
___
> Users mailing list
>
Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users [1]



Links:
--
[1] http://lists.ovirt.org/mailman/listinfo/users
[2]
https://gerrit.ovirt.org/#/c/50662/
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-17 Thread Bello Florent
 

Hi, 

I upgrade my 3 servers to CentOS 7.2 and oVirt 3.6.1, the
oVirt engine works fine and my first host upgraded too. However, my
second and third host have a ovirt-ha-broker issue and is doesn't
start.
When i try to start the broker service, it failed with timeout.


Here my logs of my second upgraded server : 

[root@ovirt01 ~]#
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; vendor
preset: disabled)
 Active: activating (start) since jeu. 2015-12-17
17:41:46 GFT; 1min 3s ago
 Process: 15245
ExecStart=/usr/lib/systemd/systemd-ovirt-ha-broker start (code=exited,
status=0/SUCCESS)
 CGroup: /system.slice/ovirt-ha-broker.service

└─15259 /usr/bin/python
/usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker

déc. 17 17:41:46
ovirt01 systemd[1]: Starting oVirt Hosted Engine High Availability
Communications Broker...
déc. 17 17:41:46 ovirt01 systemd[1]: PID 15252
read from file /run/ovirt-hosted-engine-ha/broker.pid does not exist or
is a zombie. 

[root@ovirt01 ~]# 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@ovirt01 ~]# tail -f
/var/log/ovirt-hosted-engine-ha/broker.log
MainThread::INFO::2015-12-17
17:44:28,562::broker::57::ovirt_hosted_engine_ha.broker.broker.Broker::(run)
ovirt-hosted-engine-ha broker 1.3.3.4
started
MainThread::INFO::2015-12-17
17:44:28,588::monitor::40::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Searching for submonitors in
/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/submonitors
MainThread::INFO::2015-12-17
17:44:28,588::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor cpu-load
MainThread::INFO::2015-12-17
17:44:28,590::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor cpu-load-no-engine
MainThread::INFO::2015-12-17
17:44:28,591::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor engine-health
MainThread::INFO::2015-12-17
17:44:28,591::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor mem-free
MainThread::INFO::2015-12-17
17:44:28,591::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor mem-load
MainThread::INFO::2015-12-17
17:44:28,591::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor mgmt-bridge
MainThread::INFO::2015-12-17
17:44:28,592::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor ping
MainThread::INFO::2015-12-17
17:44:28,592::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor cpu-load
MainThread::INFO::2015-12-17
17:44:28,593::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor cpu-load-no-engine
MainThread::INFO::2015-12-17
17:44:28,593::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor engine-health
MainThread::INFO::2015-12-17
17:44:28,593::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor mem-free
MainThread::INFO::2015-12-17
17:44:28,594::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor mem-load
MainThread::INFO::2015-12-17
17:44:28,594::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor mgmt-bridge
MainThread::INFO::2015-12-17
17:44:28,594::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor ping
MainThread::INFO::2015-12-17
17:44:28,594::monitor::50::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Finished loading submonitors
MainThread::INFO::2015-12-17
17:44:28,595::listener::41::ovirt_hosted_engine_ha.broker.listener.Listener::(__init__)
Initializing SocketServer
MainThread::INFO::2015-12-17
17:44:28,595::listener::56::ovirt_hosted_engine_ha.broker.listener.Listener::(__init__)
SocketServer ready
MainThread::INFO::2015-12-17
17:45:59,215::broker::114::ovirt_hosted_engine_ha.broker.broker.Broker::(run)
Server shutting down 

[root@ovirt01 ~]# tail -f
/var/log/vdsm/vdsm.log
Reactor thread::INFO::2015-12-17
17:48:19,800::protocoldetector::72::ProtocolDetector.AcceptorImpl::(handle_accept)
Accepting connection from 127.0.0.1:44498
Reactor
thread::DEBUG::2015-12-17
17:48:19,808::protocoldetector::82::ProtocolDetector.Detector::(__init__)
Using required_size=11
Reactor thread::INFO::2015-12-17
17:48:19,808::protocoldetector::118::ProtocolDetector.Detector::(handle_read)
Detected protocol xml from 

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

2015-12-17 Thread Simone Tiraboschi
On Thu, Dec 17, 2015 at 9:49 PM, Bello Florent <
florent.be...@ville-kourou.fr> wrote:

> Hi,
>
> I upgrade my 3 servers to CentOS 7.2 and oVirt 3.6.1, the oVirt engine
> works fine and my first host upgraded too. However, my second and third
> host have a ovirt-ha-broker issue and is doesn't start.
> When i try to start the broker service, it failed with timeout.
>
> Here my logs of my second upgraded server :
>
> [root@ovirt01 ~]# 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; vendor preset: disabled)
>Active: activating (start) since jeu. 2015-12-17 17:41:46 GFT; 1min 3s
> ago
>   Process: 15245 ExecStart=/usr/lib/systemd/systemd-ovirt-ha-broker start
> (code=exited, status=0/SUCCESS)
>CGroup: /system.slice/ovirt-ha-broker.service
>└─15259 /usr/bin/python
> /usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker
>
> déc. 17 17:41:46 ovirt01 systemd[1]: Starting oVirt Hosted Engine High
> Availability Communications Broker...
> déc. 17 17:41:46 ovirt01 systemd[1]: PID 15252 read from file
> /run/ovirt-hosted-engine-ha/broker.pid does not exist or is a zombie.
>
>
>
> [root@ovirt01 ~]# 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.
>
>
>

Thanks for the report Florent,
just today I experimented it too: we are checking if it's related to this
last minute patch from this morning:
https://gerrit.ovirt.org/#/c/50662/

Adding Fabian and Martin.


> [root@ovirt01 ~]# tail -f /var/log/ovirt-hosted-engine-ha/broker.log
> MainThread::INFO::2015-12-17
> 17:44:28,562::broker::57::ovirt_hosted_engine_ha.broker.broker.Broker::(run)
> ovirt-hosted-engine-ha broker 1.3.3.4 started
> MainThread::INFO::2015-12-17
> 17:44:28,588::monitor::40::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Searching for submonitors in
> /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/submonitors
> MainThread::INFO::2015-12-17
> 17:44:28,588::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor cpu-load
> MainThread::INFO::2015-12-17
> 17:44:28,590::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor cpu-load-no-engine
> MainThread::INFO::2015-12-17
> 17:44:28,591::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor engine-health
> MainThread::INFO::2015-12-17
> 17:44:28,591::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor mem-free
> MainThread::INFO::2015-12-17
> 17:44:28,591::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor mem-load
> MainThread::INFO::2015-12-17
> 17:44:28,591::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor mgmt-bridge
> MainThread::INFO::2015-12-17
> 17:44:28,592::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor ping
> MainThread::INFO::2015-12-17
> 17:44:28,592::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor cpu-load
> MainThread::INFO::2015-12-17
> 17:44:28,593::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor cpu-load-no-engine
> MainThread::INFO::2015-12-17
> 17:44:28,593::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor engine-health
> MainThread::INFO::2015-12-17
> 17:44:28,593::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor mem-free
> MainThread::INFO::2015-12-17
> 17:44:28,594::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor mem-load
> MainThread::INFO::2015-12-17
> 17:44:28,594::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor mgmt-bridge
> MainThread::INFO::2015-12-17
> 17:44:28,594::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor ping
> MainThread::INFO::2015-12-17
> 17:44:28,594::monitor::50::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Finished loading submonitors
> MainThread::INFO::2015-12-17
> 17:44:28,595::listener::41::ovirt_hosted_engine_ha.broker.listener.Listener::(__init__)
> Initializing SocketServer
> MainThread::INFO::2015-12-17
> 17:44:28,595::listener::56::ovirt_hosted_engine_ha.broker.listener.Listener::(__init__)
> SocketServer ready
> MainThread::INFO::2015-12-17
> 17:45:59,215::broker::114::ovirt_hosted_engine_ha.broker.broker.Broker::(run)
> Server shutting 

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

2015-12-17 Thread Matthew Trent
(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.

[root@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@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@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-17 Thread Matthew Trent
Yes! That did it. All the errors are gone, and HA seems to be functioning 
normally. Thanks much!


--
Matthew Trent
Network Engineer
Lewis County IT Services
?

From: Simone Tiraboschi <stira...@redhat.com>
Sent: Thursday, December 17, 2015 4:50 PM
To: Matthew Trent
Cc: users@ovirt.org
Subject: Re: [ovirt-users] ovirt-ha-broker issue after upgrade CentOS 7.1 => 
7.2 and oVirt 3.6.0 => 3.6.1



On Fri, Dec 18, 2015 at 12:32 AM, Matthew Trent 
<matthew.tr...@lewiscountywa.gov<mailto:matthew.tr...@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@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@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@ovirt.org<mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2015-12-17 Thread Simone Tiraboschi
On Fri, Dec 18, 2015 at 12:32 AM, Matthew Trent <
matthew.tr...@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@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@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@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users