Hi,

Thanks you for all your input
We have pinpoint the cause of our "liveliness check: failure. In our engine
we have a external provider that connect to our domain controller with LDAP
request. When we removed this provider the hosted-engine host  was able to
check for liveliness on the engine.

Not sure why the provider is preventing the engine to go live. Any thoughts?

Thanks & Regards
Carl

On Wed, Jul 24, 2019 at 11:00 PM Strahil <hunter86...@yahoo.com> wrote:

> The CA can be downloaded  via the web , or you can tell curl to just
> ignore the engine's cert via the '-k' flag.
> It will show you if the health page is working.
>
> Best Regards,
> Strahil Nikolov
> On Jul 24, 2019 19:39, carl langlois <crl.langl...@gmail.com> wrote:
>
> Strahil, not sure what to put for the --cacert.
>
> Yes Derek your are right at one point the port 8702 stop listening.
>
> tcp6       0      0 127.0.0.1:8702          :::*
>  LISTEN      1607/ovirt-engine
>
> After some time the line above disappear. I am trying to figure why this
> port is being close after some time when  the engine is running on the host
> on the 248.x network. On the 236.x network this port is kept alive all the
> time.
> If you have any hint on why this port is closing do not hesitate because i
> am starting to be out of ideas. :-)
>
>
> Thanks & Regards
>
> Carl
>
>
>
>
>
>
> On Wed, Jul 24, 2019 at 11:11 AM Strahil Nikolov <hunter86...@yahoo.com>
> wrote:
>
> A healthy engine should report:
> [root@ovirt1 ~]# curl --cacert CA
> https://engine.localdomain/ovirt-engine/services/health;echo
> DB Up!Welcome to Health Status!
>
> Of course you can use the '-k' switch to verify the situation.
>
> Best Regards,
> Strahil Nikolov
>
> В сряда, 24 юли 2019 г., 17:43:59 ч. Гринуич+3, Derek Atkins <
> de...@ihtfp.com> написа:
>
>
> Hi,
>
> carl langlois <crl.langl...@gmail.com> writes:
>
> > If i try to access http://ovengine/ovirt-engine/services/health
> > i always get "Service Unavailable" in the browser and each time i it
> reload in
> > the browser i get in the error_log
> >
> >  [proxy_ajp:error] [pid 1868] [client 10.8.1.76:63512] AH00896: failed
> to make
> > connection to backend: 127.0.0.1
> > [Tue Jul 23 14:04:10.074023 2019] [proxy:error] [pid 1416]
> (111)Connection
> > refused: AH00957: AJP: attempt to connect to 127.0.0.1:8702 (127.0.0.1)
> failed
>
> Sounds like a service isn't running on port 8702.
>
> > Thanks & Regards
> >
> > Carl
>
> -derek
>
> --
>       Derek Atkins                617-623-3745
>
>       de...@ihtfp.com
>             www.ihtfp.com
>       Computer and Internet Security Consultant
>
>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/4Z2RKPLZKS5YXNPIUEGP5ASTCKVDJNS6/

Reply via email to