-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
其他组件启动都没有问题,就是client启动报错了 #19
Comments
大佬,有空帮忙看一下 |
本地的这个服务连不上: |
telnet 试一下本地端口是否可以连上 |
我也是一样的问题,部署到阿里云的时候 客户端连接超时。 |
@rainbowyao 可以看看注册到 ZK 里的服务地址是多少,多网卡加上内网环境可能会出现注册了内网地址的问题。 |
本地环境启动 cim-client 工程报错环境信息如下: 宿主机 虚拟机 以下是 cim-client 启动错误的堆栈信息
错误信息推断cim-client 工程在内网环境获取到的 IP 为169.254.136.188 不正确,cim-client 无法访问
原因可能为: cim-server 和 zookeeper 运行在不同的子网,导致从 cim-forward-route 获取的 IP cim-client 无法访问 PS: 验证作者的提示
查看zookeeper注册信息
结果:注册到 ZK 里的服务地址在运行 cim-client 的网络下无法访问 解决过程
|
启动客户端只显示了一行错误就退出了 [2020-03-29 10:03:13] zhangsan$ 登录信息不匹配! Process finished with exit code 255 image 请问这是怎么回事啊,谢谢大佬解答 |
@jdkYang 我 demo 里配置的 |
我遇到同样的问题,使用java -jar cim-client-1.0.0-SNAPSHOT.jar --server.port=8084 --cim.user.id=1602300121383 --cim.user.userName=libuwei --cim.route.url=http://154.8.222.62:8083/去登录时报错:The User information you have used is incorrect! ,主要是因为redis中没有相关数据,可以先执行作者的curl命令,(curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' -d '{ "reqNo": "123456789", "timeStamp": 0, "userName": "libuwei"}' 'http://154.8.222.62:8083/registerAccount'),当生成一个用户时再去启动cim-client服务。另外也可以去redis按照:cim-account:1602300121383(这个时userId)添加进去。 |
开启了其他的使用
也注册不了 |
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'CIMClient': Invocation of init method failed; nested exception is io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out: no further information: /172.17.48.1:11211
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:137) ~[spring-beans-4.3.10.RELEASE.jar:4.3.10.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:409) ~[spring-beans-4.3.10.RELEASE.jar:4.3.10.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1620) ~[spring-beans-4.3.10.RELEASE.jar:4.3.10.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555) ~[spring-beans-4.3.10.RELEASE.jar:4.3.10.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483) ~[spring-beans-4.3.10.RELEASE.jar:4.3.10.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306) ~[spring-beans-4.3.10.RELEASE.jar:4.3.10.RELEASE]
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) ~[spring-beans-4.3.10.RELEASE.jar:4.3.10.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302) ~[spring-beans-4.3.10.RELEASE.jar:4.3.10.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) ~[spring-beans-4.3.10.RELEASE.jar:4.3.10.RELEASE]
The text was updated successfully, but these errors were encountered: