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

Re: debug routes not working with 1.1.6



Are they pointed to the right backends?  Or have any backends?  Are the ports right?

On Apr 18, 2016, at 4:01 PM, Candide Kemmler <candide intrinsic world> wrote:

I got how to retrieve the stats:


So yes it appears that the routes are there: be_http_dev_flx and be_http_dev_webtools


On 18 Apr 2016, at 20:11, Clayton Coleman <ccoleman redhat com> wrote:

Does the haproxy status port show you the routes?  It's on port 1936 and the password is defined as an env var

On Apr 18, 2016, at 1:58 PM, Candide Kemmler <candide intrinsic world> wrote:

mmh, logs or describe don't look interesting at all.

[admin server-3 development]$ oc describe route webtools
Name: webtools
Created: 4 minutes ago
Labels: micro_service_name=webtools,template=intrinsic-edge-development
Annotations: openshift.io/host.generated=true
Requested Host: webtools-dev.apps.intrinsic.world
  exposed on router router 4 minutes ago
Path: <none>
TLS Termination: <none>
Insecure Policy: <none>
Service: webtools
Endpoint Port: 8080-tcp
Endpoints: 10.1.0.8:8443, 10.1.0.8:8778, 10.1.0.8:8080

The first messages below are a bit more intringuing:

E0418 17:48:27.663159 1 reflector.go:271] pkg/router/controller/factory/factory.go:66: Failed to watch *api.Endpoints: Get https://paas.intrinsic.world:8443/api/v1/watch/endpoints?resourceVersion=6190: dial tcp 167.114.238.170:8443: getsockopt: connection refused
E0418 17:48:27.663159 1 reflector.go:271] pkg/router/controller/factory/factory.go:59: Failed to watch *api.Route: Get https://paas.intrinsic.world:8443/oapi/v1/watch/routes?resourceVersion=6185: dial tcp 167.114.238.170:8443: getsockopt: connection refused
I0418 17:48:31.949514 1 router.go:310] Router reloaded: 
- Checking HAProxy /healthz on port 1936 ... 
- HAProxy port 1936 health check ok : 0 retry attempt(s). 
I0418 17:48:34.371633 1 router.go:310] Router reloaded: 
- Checking HAProxy /healthz on port 1936 ... 
- HAProxy port 1936 health check ok : 0 retry attempt(s). 
I0418 17:50:05.624552 1 router.go:310] Router reloaded: 
- Checking HAProxy /healthz on port 1936 ... 


I have not updated but really re-installed everything. For an instant I thought that setting:

corsAllowedOrigins:
  - .*

in the master-config yaml and restarting master would fix it, but it didn't. I also deleted and re-created the routes to no effect.

Of course I checked that my services are available from the pods themselves.

Other ideas?


On 18 Apr 2016, at 19:27, Clayton Coleman <ccoleman redhat com> wrote:

Would recommend looking at router logs - there may be an error on
update.  Also, run oc describe route ROUTENAME

On Mon, Apr 18, 2016 at 1:05 PM, Candide Kemmler
<candide intrinsic world> wrote:
I just got my setup to work on 1.1.6. Alas, my routes seem to be broken as the two web-facing pods I have hang going to their web URL.

How do I debug this issue?



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



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