Forum Discussion

Brian_Dantzig's avatar
Brian_Dantzig
Icon for Nimbostratus rankNimbostratus
Jan 04, 2019

Interpretation of 6581 monitor status log messages

When my https monitor marks a pool member down, it logs the following detail in the monitor status down message.

 

Unable to connect; Response Code: 200 (OK); No successful responses received before deadline.; Response Code: 502 (Bad Gateway)

 

How is this information interpreted?

 

It appears to be the responses from the last 3 monitor requests.

 

Is this telling me that the first test had a response of 200 and didn't match my return string then the second never received a response but the 3rd test came back as a 502 from the content server?

 

Also, if that's the case, wouldn't it be the oldest request that timed out and not the middle of the three?

 

I would appreciate any help in understanding exactly how to interpret this so I can convey this to the application and hosting provider.