AFAIK this Apache message is normal. Your containers get a dynamic
address and won't be resolvable though DNS. This is ok as users
never reach containers directly, but use either services (only for
other containers) or routes (external users).
This 503 error usually happens when your browser requested a
hostname that do not matches any route. Could you provide the URL
you used to acces your application, and the route configuartion
(oc describe route)?
s, Fernando Lozano
I'm building and deploying an s2i-application.
I'm creating a route to the service but I'm not able to access
503 Service Unavailable
No server available to handle the request.
The container logs show:
Could not reliably determine the server's fully qualified
domain name, using 10.1.0.22. Set the 'ServerName' directive
globally to suppress this message
What is this issue? I also have that issue when I'm trying to
deploy the wordpress-example of origin.
I'm using OpenShift Origin:
users mailing list
users lists openshift redhat com