ayasuda2OO3
commented
3 years ago duplicate tracker #137 @simran3695 @ramaraosrikakulapu @palokam
Open simran3695 opened 3 years ago
ayasuda2OO3
commented
3 years ago duplicate tracker #137 @simran3695 @ramaraosrikakulapu @palokam
We have currently seen an issue where EC Server running on On-prem are not able to connect to EC Gateway running on AWS (EKS Cluster). and etting below error:
[EC Server] 2020/10/15 13:36:37 [cleaned up logging file(s). connectivity.log plugin.log] [EC Server] 2020/10/15 13:36:37 [Rev: v1.hokkaido.212] [EC Server] 2020/10/15 13:36:37 [Agent websocket compression is being negotiated at level 0] [EC Server] 2020/10/15 13:36:37 [refresh duration is specified. Token auto-refresh is set.] [EC Server] 2020/10/15 13:36:37 [Fetching new token..] [EC Server] 2020/10/15 13:36:37 [Token refreshed. The token will be expired in 719 minutes. Approx. 20 minutes to the next auto-refresh.] [EC Server] 2020/10/15 13:36:37 [health api will be available on the local port#8545] [EC Server] 2020/10/15 13:36:38 [initialising super connection for gateway inst#0] [EC Server] 2020/10/15 13:36:38 [proxy serivce (10.114.19.200) is found.] [EC Server] 2020/10/15 13:36:38 [github.build.ge.com/212359746/wzcore.(*Server).admChannelReq.func1 runtime error: invalid memory address or nil pointer dereference] ^C
We got to know about the proxy feature availaibilty on v1.1beta version can we have same setting on 212 as going forward we are moving all our customer gateway's on EKS.