[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: cannot expose docker service



Okay, so for the record, the node app I tried to deploy was explicitely listening on port 127.0.0.1... That's why... Oh my what a waste of time!

Thanks for the help!

On 08 Jun 2016, at 00:55, Ram Ranganathan <rrangana redhat com> wrote:

So would suggest, first checking if you can access the route from the host where your router is running ala:

That at the very least verifies that the haproxy config + route is ok. 

And then check for any external routing/firewall/etc issues by running that curl command on another node / outside the cluster switching 127.0.0.1 to the actual IP address of the host(s) where the router is running.

HTH

On Tue, Jun 7, 2016 at 12:40 PM, Candide Kemmler <candide intrinsic world> wrote:
See below. Then again, I have tons of other pods that work just fine on this openshift instance.

[admin paas development]$ oc logs dc/router -n default
I0607 15:40:03.083078       1 router.go:161] Router is including routes in all namespaces
I0607 15:40:07.389174       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 15:40:08.317159       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 15:40:15.846769       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 15:50:04.589960       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 15:50:08.215881       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 16:00:05.529664       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 16:00:12.695714       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 16:02:15.475518       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 16:10:06.262443       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 16:10:08.170507       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 16:20:07.257365       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 16:20:08.178744       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 16:24:37.658033       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 16:24:39.076408       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 16:30:08.574189       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 16:30:13.198829       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 16:40:09.513607       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 16:40:20.237690       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 16:50:10.528691       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 16:50:13.234178       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 17:00:11.306389       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 17:00:13.174592       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 17:10:12.258383       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 17:10:13.357327       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 17:20:13.640493       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 17:20:18.555030       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 17:30:15.410032       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 17:30:18.163619       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 17:40:15.350079       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 17:40:18.163290       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 17:50:16.402243       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 17:50:18.226275       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:00:17.319497       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:00:18.203229       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:10:18.605779       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:10:23.197311       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:20:19.568966       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:20:23.220022       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:25:48.536137       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:25:53.156059       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:25:58.235775       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:26:03.162379       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:26:40.901553       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:26:54.190289       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:26:58.927938       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:27:20.770432       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:27:27.753707       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:27:28.604589       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:28:43.688943       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:30:20.313532       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:30:23.208836       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:36:25.124173       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:40:21.298528       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:40:23.375553       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:50:22.275753       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 18:50:23.176191       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 19:00:23.568077       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 19:00:28.152691       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 19:10:24.577818       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 19:10:28.233401       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 19:20:25.536460       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 19:20:28.227925       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 19:30:26.592129       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).
I0607 19:30:28.165657       1 router.go:310] Router reloaded:
 - Checking HAProxy /healthz on port 1936 ...
 - HAProxy port 1936 health check ok : 0 retry attempt(s).

On 07 Jun 2016, at 21:36, Clayton Coleman <ccoleman redhat com> wrote:

Can you double check the router started successfully - what do you see when you run oc logs dc/router -n default?

On Tue, Jun 7, 2016 at 2:44 PM, Candide Kemmler <candide intrinsic world> wrote:
I am also able to port forward locally... Really strange: the only thing that doesn't work is really the public route.

Any idea what I might have done wrong based on my template?

I doubt this is a bug, but not seeing any solution, I may file it as that anyway...


On 07 Jun 2016, at 17:48, Clayton Coleman <ccoleman redhat com> wrote:

So you see IP 10.1.2.20 listed in the endpoints for service your dictionary points to?  oc get endpoints SERVICE_NAME?

On Tue, Jun 7, 2016 at 10:38 AM, Candide Kemmler <candide intrinsic world> wrote:
...and here's the pod's description:

Name: dictionary-10-b3go6
Namespace: ieml-dev
Node: apps.intrinsic.world/167.114.241.106
Start Time: Tue, 07 Jun 2016 16:14:28 +0200
Labels: app=dictionary,deployment=dictionary-10,deploymentconfig=dictionary
Status: Running
Reason:
Message:
IP: 10.1.0.20
Replication Controllers: dictionary-10 (1/1 replicas created)
Containers:
  dictionary:
    QoS Tier:
      cpu: BestEffort
      memory: BestEffort
    State: Running
      Started: Tue, 07 Jun 2016 16:14:31 +0200
    Ready: True
    Restart Count: 0
    Environment Variables:
Conditions:
  Type Status
  Ready True 
Volumes:
  default-token-cqsfz:
    Type: Secret (a secret that should populate this volume)
    SecretName: default-token-cqsfz
Events:
  FirstSeen LastSeen Count From SubobjectPath Reason Message
  ───────── ──────── ───── ──── ───────────── ────── ───────
  22m 22m 1 {default-scheduler } Scheduled Successfully assigned dictionary-10-b3go6 to apps.intrinsic.world
  22m 22m 1 {kubelet apps.intrinsic.world} spec.containers{dictionary} Pulling pulling image "172.30.171.126:5000/ieml-dev/dictionary sha256:b1566af562a870eb94d4c2f46f47a46fb391876ce809d2c715762c5b88aa9083"
  22m 22m 1 {kubelet apps.intrinsic.world} spec.containers{dictionary} Pulled Successfully pulled image "172.30.171.126:5000/ieml-dev/dictionary sha256:b1566af562a870eb94d4c2f46f47a46fb391876ce809d2c715762c5b88aa9083"
  22m 22m 1 {kubelet apps.intrinsic.world} spec.containers{dictionary} Created Created container with docker id 2d310c466110
  22m 22m 1 {kubelet apps.intrinsic.world} spec.containers{dictionary} Started Started container with docker id 2d310c466110



On 07 Jun 2016, at 16:21, Clayton Coleman <ccoleman redhat com> wrote:

Ok, so you created a route, and the route pointed to your service?  If you look at the endpoints for your service, are there any listed (i.e., did any pods start correctly)?

On Tue, Jun 7, 2016 at 10:17 AM, Candide Kemmler <candide intrinsic world> wrote:
I was expecting I could access the service through



On 07 Jun 2016, at 16:11, Clayton Coleman <ccoleman redhat com> wrote:

From the outside, what are you trying to curl?

On Tue, Jun 7, 2016 at 9:32 AM, Candide Kemmler <candide intrinsic world> wrote:
I have trouble exposing a service as a docker container.

My Dockerfile ends with EXPOSE 8080 and I have a route using that port:


I don't see where I'm doing things differently and yet I can `curl localhost:8080` from the pod itself but not access it from the outside world where I'm consistently seeing a 503 Service Unavailable.

_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users










_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users




--
Ram//
main(O,s){s=--O;10<putchar(3^O?97-(15&7183>>4*s)*(O++?-1:1):10)&&\
main(++O,s++);}



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]