-
Choerodon平台版本: 0.11
-
遇到问题的执行步骤:
登录验证后页面有时候出现404,有时候直接版面错 -
报错日志:
404
页面错乱
一直刷新 有时候可以正常展示 这是哪个服务有问题?
你好呀,已经获取到token了,像是认证成功后的重定向地址的问题。能给出浏览器的报错信息吗,network的。
你好 请问下这个问题能帮忙看下吗?谢谢了
你好呀,请确认一下以下两个问题:
是的,一般都是404,多刷几次有时候可以进去,但是再刷新又404了。
是不是什么服务不稳定? 这个要怎么排查?一般是什么接口问题哈
你好,我看了下你的问题有两个。
一个是登陆后跳转到404页面,另一个是进入首页后样式丢失。
先说第二个,首页的域名与登录的域名不同,样式丢失一般是样式文件没有下载成功。可以清空下缓存,然后控制台查看下加载样式文件耗时,如果网络不好的话确实会加载不出来样式。
页面404,可以判断为接口不可调用。因为该接口是通过网关路由到oauth 上的。如果在登录跳转的时候,oauth 服务不可用,接口可能会返回404。可以在出错的时候查看oauth-server 的日志信息。
如果没有任何错误提示,也可以查看api-gateway 的日志信息。
oauth-serve api-gateway 都没有明显的报错。前台还是404
oauth日志:
vops-ofc:8010/
2018-12-05 20:46:31.380 INFO [oauth-server,,,] 1 --- [ XNIO-2 task-24] c.c.c.ConfigServicePropertySourceLocator : Located environment: name=manager-service, profiles=[default], label=null, version=null, state=null
2018-12-05 20:49:28.123 INFO [oauth-server,,,] 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver : Resolving eureka endpoints via configuration
2018-12-05 20:51:41.300 INFO [oauth-server,,,] 1 --- [ XNIO-2 task-22] c.c.c.ConfigServicePropertySourceLocator : Fetching config from server at: http://config-server.liantai-devops-ofc:8010/
2018-12-05 20:51:41.341 INFO [oauth-server,,,] 1 --- [ XNIO-2 task-22] c.c.c.ConfigServicePropertySourceLocator : Located environment: name=manager-service, profiles=[default], label=null, version=null, state=null
2018-12-05 20:54:28.124 INFO [oauth-server,,,] 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver : Resolving eureka endpoints via configuration
2018-12-05 20:56:41.346 INFO [oauth-server,,,] 1 --- [ XNIO-2 task-18] c.c.c.ConfigServicePropertySourceLocator : Fetching config from server at: http://config-server.liantai-devops-ofc:8010/
2018-12-05 20:56:41.434 INFO [oauth-server,,,] 1 --- [ XNIO-2 task-18] c.c.c.ConfigServicePropertySourceLocator : Located environment: name=manager-service, profiles=[default], label=null, version=null, state=null
2018-12-05 20:58:02.082 INFO [oauth-server,a9acf63786c36be1,1f096d001b6fcffe,true] 1 --- [ XNIO-3 task-24] o.s.s.o.p.t.AuthenticationKeyGenerator : sessionId : 46343c39-1cac-4fb5-8f78-c868043f378f
2018-12-05 20:58:02.089 INFO [oauth-server,a9acf63786c36be1,1f096d001b6fcffe,true] 1 --- [ XNIO-3 task-24] o.s.s.o.p.token.store.JdbcTokenStore : Failed to find access token for token 0386fd97-c860-447d-b4b1-985a99c2fbc0
2018-12-05 20:58:02.093 INFO [oauth-server,a9acf63786c36be1,1f096d001b6fcffe,true] 1 --- [ XNIO-3 task-24] o.s.s.o.p.t.AuthenticationKeyGenerator : sessionId : 46343c39-1cac-4fb5-8f78-c868043f378f
2018-12-05 20:59:28.125 INFO [oauth-server,,,] 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver : Resolving eureka endpoints via configuration
APIGATEWAY日志:
2018-12-05 20:58:43.000 INFO [api-gateway,,,] 1 --- [ XNIO-2 task-28] o.s.cloud.config.client.RouterOperator : refresh zuul routes
2018-12-05 20:58:44.237 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Disable delta property : true
2018-12-05 20:58:44.237 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Single vip registry refresh property : null
2018-12-05 20:58:44.237 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Force full registry fetch : false
2018-12-05 20:58:44.237 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Application is null : false
2018-12-05 20:58:44.237 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Registered Applications size is zero : false
2018-12-05 20:58:44.237 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Application version is -1: false
2018-12-05 20:58:44.237 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Getting all instance registry info from the eureka server
2018-12-05 20:58:44.244 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : The response status is 200
2018-12-05 20:58:54.245 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Disable delta property : true
2018-12-05 20:58:54.245 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Single vip registry refresh property : null
2018-12-05 20:58:54.245 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Force full registry fetch : false
2018-12-05 20:58:54.245 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Application is null : false
2018-12-05 20:58:54.245 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Registered Applications size is zero : false
2018-12-05 20:58:54.245 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Application version is -1: false
2018-12-05 20:58:54.245 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Getting all instance registry info from the eureka server
2018-12-05 20:58:54.251 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : The response status is 200
2018-12-05 20:59:02.555 INFO [api-gateway,d7bebd1bff767893,d7bebd1bff767893,true] 1 --- [ XNIO-3 task-54] i.c.gateway.filter.HeaderWrapperFilter : Request get empty jwt , request uri: /iam/v1/system/setting method: GET
2018-12-05 20:59:04.252 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Disable delta property : true
2018-12-05 20:59:04.252 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Single vip registry refresh property : null
2018-12-05 20:59:04.252 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Force full registry fetch : false
2018-12-05 20:59:04.252 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Application is null : false
2018-12-05 20:59:04.252 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Registered Applications size is zero : false
2018-12-05 20:59:04.253 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Application version is -1: false
2018-12-05 20:59:04.253 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Getting all instance registry info from the eureka server
2018-12-05 20:59:04.258 INFO [api-gateway,,,] 1 --- [freshExecutor-0] com.netflix.discovery.DiscoveryClient : The response status is 200
你可以进入到oauth-server 的pod 内,通过curl localhost:8021/mapping
查看oauth 所有的endpoint
, 确认下oaut-server 接口没问题。
然后查看下数据库中manager_service.mgmt_route
这张表中是否有oauth-server
的路由。确保请求可以路由到正确的服务。
查看集群中服务已经启动的实例个数,确保不会由于其他版本造成请求错乱。
最后在请求接口的同时,查看api-gateway, gateway-helper, oauth-server
的日志。
然后提供一下/oauth/oauth/authorize?response_type=token&state=&redirect_uri=
这个接口,禁止缓存,手动调用试试看会不会出问题。