Forum Discussion

am_gli_287451's avatar
Icon for Nimbostratus rankNimbostratus
Sep 19, 2017

Sharepoint HealthCheck not working



recently we updated our SP2010-Farm to SP2013 and our monitors stopped working.


The monitors were http-monitors with the send string:


GET /pages/default.aspx HTTP/1.1\r\nHost: \r\nConnection: Close\r\n\r\n


The expected receive string was set to "X-SharePointHealthScore:", since this is something that only a running SP service would return.


Now, since the upgrade we had to degrade all our monitors to normal tcp on port 443, but we would like to have these old monitors back in place.


From the F5, it is possible to telnet to the node via 443, but the GET-request from the monitor doesn't return anything and times out. But when I try curl, it seems to work:


" curl -v -k -H "Host: ; " It returns the SSL-information etc. and also the SP-Parameters, which also contain the "X-SharepointHealthScore", which we are looking for.


One thing that is to be mentioned is, that the server is using a self-signed certificate. Curl says "* SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed"


But I'm not sure if this is just an issue of curl, or could this cause also the problems with the monitor? Also - normal traffic is working properly, with the F5 talking to the servers in the back end via HTTPS.


Any idea is welcome :)


1 Reply

  • Hi,

    Could you post the output of the tmsh command :

    list ltm monitor https old_monitor_name

    If thought that it is SNI related, but if CURL working fine, basic HTTPs monitor should work also.

    You said "The monitors were http-monitors with the send string:"

    Pool members of SP2010 farm were listnening on HTTP port or HTTPs ?

    For the SP2013 are you sure you applied HTTPS monitor... because based on what you said "http-monitors"...

    Please clarify