Getting 503 Service Unavailable Error When Accessing Application Via Oracle Traffic Director
(Doc ID 2290306.1)
Last updated on OCTOBER 03, 2017
Applies to:Oracle Traffic Director - Version 18.104.22.168 and later
Information in this document applies to any platform.
Accessing application through Oracle Traffic Director (OTD) fails with error saying "Service Unavailable".
The OTD log shows the OTD marks all the servers in the origin server pool offline after receiving response code 500 for the health check request (OPTIONS method by default)
[2017-07-25T15:27:06-04:00] [net-pr-abms-ha] [TRACE:1]   [pid: 5970] trying to OPTIONS /, check-http-server reports: received server error response code 500 from server backendserver02.example.com:51211
[2017-07-25T15:28:44-04:00] [net-pr-abms-ha] [WARNING:1] [OTD-11016]  [pid: 5970] health-check reports: all servers in origin server pool origin-server-pool-1 are offline.
[2017-07-25T15:27:59-04:00] [net-pr-abms-ha] [TRACE:32]   [ecid: t4okA0R0000000000] [rid: 0] [pid: 5970] for host xx.xx.xx.xx trying to GET /, func_exec reports: fn="set-origin-server" origin-server-pool="origin-server-pool-1" rewrite-location="false" rewrite-content-location="false" Directive="Route" magnus-internal="" magnus-internal="" returned -1 (REQ_ABORTED)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!