[ovirt-users] [hosted-engine-ha] restart-loop

[Doron Fediuck]

----- Original Message -----
> From: "Daniel Helgenberger" <daniel.helgenberger at m-box.de>
> To: "Ludek Finstrle" <lfinstrle at netsuite.com>
> Cc: users at ovirt.org
> Sent: Monday, September 29, 2014 7:27:35 PM
> Subject: Re: [ovirt-users] [hosted-engine-ha] restart-loop
> 
> Hello Luf,
> 
> thanks for the input.
> 
> Indeed, the network is fine; i can ping the engine fine from both hosts;
> also name resolution works from engine -> hosts as vice versa.
> 
> On 29.09.2014 16:12, Finstrle, Ludek wrote:
> > Hi Daniel,
> >
> > I had similar problem when my routing table was corrupted
> > so the host wasn't able to reach the hosted-engine IP address.
> >
> > Are you sure that ovirt host can reach hosted-engine?
> > (routing, fw, ...)
> >
> > Cheers,
> >
> > Luf
> >
> > Daniel Helgenberger píše v So 27. 09. 2014 v 10:40 +0000:
> >  > Hello,
> >  >
> >  > before filing a BZ against 3.4 branch I wanted to get some input on the
> >  > following issue:
> >  >
> >  > Steps, root shell on one engine-ha hosts, using hosted-engine cmd:
> >  > 1. set global maintenance
> >  > 2. shutdown hosted-engine vm
> >  > (do some work)
> >  > 3. disable global maintenance
> >  >
> >  > Result: My engine was started and immediately powered down again, in a
> >  > loop.
> >  > I could only manually brake this with:
> >  > 1. enable global mt. gain
> >  > 2. start engine
> >  > 3. disable global mt.
> >  >
> >  > I attached the hosts' engine-ha broker logs as well as agent logs, from
> >  > today 12:00 to 12:27, right after I 'fixed' this.
> >  > Note, the engine was started on nodehv02 automatically after i disabled
> >  > global mt. @ about 12:05
> >  >
> >  > Thanks
> >  >
> >  > _______________________________________________
> >  > Users mailing list
> >  > Users at ovirt.org <mailto:Users at ovirt.org>
> >  > http://lists.ovirt.org/mailman/listinfo/users
> >  >
> >  >
> >
> >
> > NOTICE: This email and any attachments may contain confidential and
> > proprietary
> > information of NetSuite Inc. and is for the sole use of the intended
> > recipient
> > for the stated purpose. Any improper use or distribution is prohibited. If
> > you
> > are not the intended recipient, please notify the sender; do not review,
> > copy or
> > distribute; and promptly delete or destroy all transmitted information.
> > Please
> > note that all communications and information transmitted through this email
> > system may be monitored and retained by NetSuite or its agents and that all
> > incoming email is automatically scanned by a third party spam and filtering
> > service which may result in deletion of a legitimate e-mail before it is
> > read by
> > the intended recipient.
> 
> --
> Daniel Helgenberger
> m box bewegtbild GmbH
> 
> P: +49/30/2408781-22
> F: +49/30/2408781-10
> 
> ACKERSTR. 19
> D-10115 BERLIN
> 
> 
> www.m-box.de  www.monkeymen.tv
> 
> Geschäftsführer: Martin Retschitzegger / Michaela Göllner
> Handeslregister: Amtsgericht Charlottenburg / HRB 112767
> 


Hi daniel,
Looking into the logs I can see:

(score) Score is 0 due to bad engine health at Sat Sep 27 12:10:56 2014
(start_monitoring) Current state EngineUpBadHealth (score: 0)
(start_monitoring) Best remote host 192.168.50.201 (id: 1, score: 2400)

So it seems that the engine inside the VM is not responding to the health test
hosted engine performs. Can you put the system in global maintenance and
check the engine in the vm? Can you access it from outside the VM?