11 p.m.
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 NikolovOn Jul 24, 2019 19:39, carl langlois <crl.langlois(a)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_bg(a)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 <derek(a)ihtfp.com>
написа:
>
>
> Hi,
>
> carl langlois <crl.langlois(a)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
>
> derek(a)ihtfp.com
> www.ihtfp.com
> Computer and Internet Security Consultant
10:31 a.m.
New subject: major network changes
Thanks Strahil,
When i run the command it get stuck waiting for the response.
About to connect() to ovengine port 443 (#0)
* Trying 10.16.248.74...
* Connected to ovengine (10.16.248.74) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* skipping SSL peer certificate verification
* SSL connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
GET /ovirt-engine/services/health HTTP/1.1
User-Agent: curl/7.29.0
Host: ovengine
Accept: */*
in the error_log i have always
[proxy_ajp:debug] [pid 2164] mod_proxy_ajp.c(276): [client
10.16.248.65:58768] AH00872: APR_BUCKET_IS_EOS
[Thu Jul 25 10:26:48.452910 2019] [proxy_ajp:debug] [pid 2164]
mod_proxy_ajp.c(282): [client 10.16.248.65:58768] AH00873: data to read
(max 8186 at 4)
[Thu Jul 25 10:26:48.452916 2019] [proxy_ajp:debug] [pid 2164]
mod_proxy_ajp.c(296): [client 10.16.248.65:58768] AH00875: got 0 bytes of
data
[Thu Jul 25 10:26:49.444631 2019] [proxy:debug] [pid 2771]
proxy_util.c(1843): AH00925: initializing worker ajp://127.0.0.1:8702 shared
[Thu Jul 25 10:26:49.444686 2019] [proxy:debug] [pid 2771]
proxy_util.c(1885): AH00927: initializing worker ajp://127.0.0.1:8702 local
[Thu Jul 25 10:26:49.444716 2019] [proxy:debug] [pid 2771]
proxy_util.c(1936): AH00931: initialized single connection worker in child
2771 for (127.0.0.1)
[Thu Jul 25 10:26:49.444745 2019] [proxy:debug] [pid 2771]
proxy_util.c(1843): AH00925: initializing worker proxy:reverse shared
[Thu Jul 25 10:26:49.444878 2019] [proxy:debug] [pid 2771]
proxy_util.c(1885): AH00927: initializing worker proxy:reverse local
[Thu Jul 25 10:26:49.444938 2019] [proxy:debug] [pid 2771]
proxy_util.c(1936): AH00931: initialized single connection worker in child
2771 for (*)
it keep initializing after the connection after an attempt to connect.
Any ideas?
Thanks & Regards
Carl
On Wed, Jul 24, 2019 at 11:00 PM Strahil <hunter86_bg(a)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.langlois(a)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_bg(a)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 <
derek(a)ihtfp.com> написа:
Hi,
carl langlois <crl.langlois(a)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
derek(a)ihtfp.com
www.ihtfp.com
Computer and Internet Security Consultant
4:30 p.m.
New subject: major network changes
That's strange...Do you have any kind of proxy there?
Best Regards,Strahil Nikolov
В четвъртък, 25 юли 2019 г., 17:31:26 ч. Гринуич+3, carl langlois
<crl.langlois(a)gmail.com> написа:
Thanks Strahil,
When i run the command it get stuck waiting for the response.
About to connect() to ovengine port 443 (#0)
* Trying 10.16.248.74...
* Connected to ovengine (10.16.248.74) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* skipping SSL peer certificate verification
* SSL connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
GET /ovirt-engine/services/health HTTP/1.1
User-Agent: curl/7.29.0
Host: ovengine
Accept: */*
in the error_log i have always
[proxy_ajp:debug] [pid 2164] mod_proxy_ajp.c(276): [client 10.16.248.65:58768] AH00872:
APR_BUCKET_IS_EOS
[Thu Jul 25 10:26:48.452910 2019] [proxy_ajp:debug] [pid 2164] mod_proxy_ajp.c(282):
[client 10.16.248.65:58768] AH00873: data to read (max 8186 at 4)
[Thu Jul 25 10:26:48.452916 2019] [proxy_ajp:debug] [pid 2164] mod_proxy_ajp.c(296):
[client 10.16.248.65:58768] AH00875: got 0 bytes of data
[Thu Jul 25 10:26:49.444631 2019] [proxy:debug] [pid 2771] proxy_util.c(1843): AH00925:
initializing worker ajp://127.0.0.1:8702 shared
[Thu Jul 25 10:26:49.444686 2019] [proxy:debug] [pid 2771] proxy_util.c(1885): AH00927:
initializing worker ajp://127.0.0.1:8702 local
[Thu Jul 25 10:26:49.444716 2019] [proxy:debug] [pid 2771] proxy_util.c(1936): AH00931:
initialized single connection worker in child 2771 for (127.0.0.1)
[Thu Jul 25 10:26:49.444745 2019] [proxy:debug] [pid 2771] proxy_util.c(1843): AH00925:
initializing worker proxy:reverse shared
[Thu Jul 25 10:26:49.444878 2019] [proxy:debug] [pid 2771] proxy_util.c(1885): AH00927:
initializing worker proxy:reverse local
[Thu Jul 25 10:26:49.444938 2019] [proxy:debug] [pid 2771] proxy_util.c(1936): AH00931:
initialized single connection worker in child 2771 for (*)
it keep initializing after the connection after an attempt to connect.
Any ideas?Thanks & Regards
Carl
On Wed, Jul 24, 2019 at 11:00 PM Strahil <hunter86_bg(a)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.langlois(a)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_bg(a)yahoo.com> wrote:
A healthy engine should report:[root@ovirt1 ~]# curl --cacert CA
https://engine.localdomain/ovirt-engine/services/health;echoDB 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 <derek(a)ihtfp.com>
написа:
Hi,
carl langlois <crl.langlois(a)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
derek(a)ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
3:35 p.m.
New subject: major network changes
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_bg(a)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.langlois(a)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_bg(a)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 <
derek(a)ihtfp.com> написа:
Hi,
carl langlois <crl.langlois(a)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
derek(a)ihtfp.com
www.ihtfp.com
Computer and Internet Security Consultant
1979
days inactive
1979
days old
3 comments
3 participants
participants (3)
-
carl langlois -
Strahil -
Strahil Nikolov