After 'set-origin-server reports: server x.x.x.x offline' Oracle Traffic Director Health Checker Does Not Mark Server As Online
Last updated on APRIL 06, 2017
Applies to:Oracle Traffic Director - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11gR1]
Information in this document applies to any platform.
When an origin server does not respond to a request due to a timeout or any other 500 error the health checker marks the server as offline.
At this point, the OTD’s offline health check should kick in and starts sending health check requests detect if the server came back online. This never happens and when the server comes back online it is still marked as offline.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms