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 <> 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          :::*                    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


On Wed, Jul 24, 2019 at 11:11 AM Strahil Nikolov <> wrote:
A healthy engine should report:
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 <> написа:


carl langlois <> 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] AH00896: failed to make
> connection to backend:
> [Tue Jul 23 14:04:10.074023 2019] [proxy:error] [pid 1416] (111)Connection
> refused: AH00957: AJP: attempt to connect to ( failed

Sounds like a service isn't running on port 8702.

> Thanks & Regards
> Carl


      Derek Atkins                617-623-3745  
      Computer and Internet Security Consultant