Forum Discussion
CirrusHealth Monitor
Hi comminity,
I have a puzzling health monitor that I can't get working.
I can curl to the server from CLI
# curl server-name.domain:1936/healthz -k
ok
But when I try to produce a health monitor via the GUI to do the same/similar I get no valid response and the pool is marked down.
This is an OpenShift server that doesn't respond to a request on 1936 so I need to craft some form of https command to mimic the above.
If I point directly at https I get the folloiwng error:
# curl https://server-name.domain/healthz -k
returns curl: (35) Unknown SSL protocol error in connection to server-name.domain:443
Has anyone seen similar issues when monitoring OpenShift pools and got a working solution / suggestion?
I need something better than TCP-half-open monitoring.
3 Replies
CA_ValliMVP
You should be looking at SSL configuration in your backend, something like this might return some more info
(echo -e "GET /healthz HTTP/1.1\r\nHost: \r\nConnection: Close\r\n\r\n";sleep 1) | openssl s_client -connect server-name.domain- mlwebster
works well from CLI, I need to play with the monitor in the GUI to see if this works as expected now - fingers crossed 🤞
- Siona_Somboba
Nimbostratus
from GUI - https monitor send string should only have
GET /healthz HTTP/1.1\r\nHost: f5bigip.domain\r\nConnection: Close\r\n\r\n
