ARN [main-SendThread(db99:2222)] zookeeper.ClientCnxn: Session 0x0 for server null, unexpected erro

本文记录了ZooKeeper客户端连接异常的问题及解决方案,详细解释了错误信息含义,并提供了检查和修正ZooKeeper配置的方法。

本文转自:http://blog.youkuaiyun.com/wulantian/article/details/38112305,略修改。


1. 2014-07-21 17:24:36,310 WARN  [main-SendThread(db99:2222)] zookeeper.ClientCnxn: Session 0x0 for server null, unexpected erro
r, closing socket connection and attempting reconnect
java.net.ConnectException: 拒绝连接                                                                                          
        at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
        at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
        at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:350)
        at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1068)
2014-07-21 17:24:36,417 INFO  [main-SendThread(db98:2222)] zookeeper.ClientCnxn: Opening socket connection to server db98/192
.168.8.98:2222. Will not attempt to authenticate using SASL (unknown error)
2014-07-21 17:24:36,418 WARN  [main-SendThread(db98:2222)] zookeeper.ClientCnxn: Session 0x0 for server null, unexpected erro
r, closing socket connection and attempting reconnect
java.net.ConnectException: 拒绝连接
解决办法:报错的原因是客户端通过2222端口连接不上。
这里要求zookeeper中zoo.cfg 中配置的端口号,与hbase中hbase-site.xml客户端配置一致。都为2181端口。


注:确认zookeeper是否已正确安装、启动。我的问题是因为zookeeper未安装,hadoop+hbase发布后,还需要发布zookeeper。


443和446是同样的证书,修改成这样可行吗: apiVersion: v1 kind: Service metadata: name: vms-core-server-cloud-access-pa-fw-v1 namespace: dev3-vms annotations: service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags: “Category=dev,Product=vms,ServiceType=biz” service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:ap-southeast-1:242777933053:certificate/74ff9ed2-8bcc-492d-b845-15308bace4e8 service.beta.kubernetes.io/aws-load-balancer-ssl-negotiation-policy: “ELBSecurityPolicy-TLS13-1-2-Res-2021-06” service.beta.kubernetes.io/aws-load-balancer-ssl-ports: “443” service.beta.kubernetes.io/aws-load-balancer-type: “external” service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: “ip” service.beta.kubernetes.io/aws-load-balancer-scheme: “internet-facing” labels: app.kubernetes.io/name: vms-core-server region: ap-southeast-1 spec: loadBalancerClass: service.k8s.aws/nlb selector: app.kubernetes.io/name: vms-core-server region: ap-southeast-1 ports: - port: 443 protocol: TCP name: cloud-access-443 targetPort: cloud-access - port: 446 protocol: TCP name: cloud-access-446 targetPort: cloud-access-short type: LoadBalancer externalTrafficPolicy: Cluster apiVersion: v1 kind: Service metadata: name: vms-core-server-cloud-access-pa-fw-v2 namespace: dev3-vms annotations: service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags: “Category=dev,Product=vms,ServiceType=biz” service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:ap-southeast-1:242777933053:certificate/e667c161-e7b0-4faa-a21e-23df5cb5f2d4 service.beta.kubernetes.io/aws-load-balancer-ssl-negotiation-policy: “ELBSecurityPolicy-TLS13-1-2-Res-2021-06” service.beta.kubernetes.io/aws-load-balancer-ssl-ports: “443” service.beta.kubernetes.io/aws-load-balancer-type: “external” service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: “ip” service.beta.kubernetes.io/aws-load-balancer-scheme: “internet-facing” labels: app.kubernetes.io/name: vms-core-server region: ap-southeast-1 spec: loadBalancerClass: service.k8s.aws/nlb selector: app.kubernetes.io/name: vms-core-server region: ap-southeast-1 ports: - port: 443 protocol: TCP name: cloud-access-443 targetPort: cloud-access - port: 446 protocol: TCP name: cloud-access-446 targetPort: cloud-access-short type: LoadBalancer externalTrafficPolicy: Cluster
最新发布
10-18
原先集群配置如下所示,请求通过443端口访问到8083,我现在需要新增一个请求,从446端口路由到8084端口,但不能更改原先的配置,不影响8083端口,即配置只能新增端口不能修改原有规则,该如何修改配置文件: istio.yaml: apiVersion: networking.istio.io/v1alpha3 kind: Gateway # 允许域名和端口的流量进入服务网格 metadata: name: vms-core-server-gw namespace: dev3-vms spec: selector: istio: ingressgateway # use istio default controller servers: - hosts: - "aps1-vms-api-alpha3.tplinkcloud.com" - "aps1-vms-alpha3.i.tplinknbu.com" - "aps1-vms-alpha3.i.tplinkcloud.com" port: number: 11443 # aps1 https, public network access name: https-aps1 protocol: HTTP - hosts: - "aps1-vms-api-alpha3.tplinkcloud.com" - "aps1-vms-alpha3.i.tplinknbu.com" - "aps1-vms-alpha3.i.tplinkcloud.com" port: number: 11082 # aps1 http, public network access name: http-aps1 protocol: HTTP - hosts: - "vms-api-internal.alpha3.tplinknbu.com" #给内部服务访问的 - "aps1-vms-api-internal.alpha3.tplinknbu.com" - "aps1-vms-api-internal-alpha3.tplinkcloud.com" port: name: http-internal-aps1 number: 21080 protocol: HTTP --- apiVersion: networking.istio.io/v1alpha3 kind: VirtualService metadata: name: vms-core-server-vs namespace: dev3-vms spec: gateways: - vms-core-server-gw hosts: - "aps1-vms-api-alpha3.tplinkcloud.com" http: - match: - uri: prefix: /api port: 11443 - uri: prefix: /v1 port: 11443 route: - destination: host: vms-core-server-aps1 port: number: 8080 --- apiVersion: networking.istio.io/v1alpha3 kind: VirtualService metadata: name: vms-core-server-internal-vs namespace: dev3-vms spec: gateways: - vms-core-server-gw hosts: - "aps1-vms-api-internal-alpha3.tplinkcloud.com" http: - match: - uri: prefix: /api/v1/internal port: 21080 # aps1 - uri: prefix: /openapi port: 21080 # aps1 route: - destination: host: vms-core-server-aps1 port: number: 80 retries: attempts: 3 retryOn: reset,connect-failure,refused-stream,unavailable,cancelled,retriable-status-codes --- apiVersion: networking.istio.io/v1alpha3 kind: VirtualService metadata: name: vms-core-server-self-aps1-vs namespace: dev3-vms spec: hosts: - vms-core-server-aps1 http: - match: - uri: prefix: / # access path port: 8850 route: - destination: host: vms-core-server-aps1 port: number: 8850 --- kind: DestinationRule apiVersion: networking.istio.io/v1alpha3 metadata: name: vms-core-server-dr namespace: dev3-vms spec: host: vms-aps1.dev3-vms.svc.cluster.local trafficPolicy: tls: mode: DISABLE service.yaml: apiVersion: v1 kind: Service metadata: name: vms-core-server-cloud-access-pa-fw-v1 namespace: dev3-vms annotations: service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags: "Category=dev,Product=vms,ServiceType=biz" service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:ap-southeast-1:242777933053:certificate/74ff9ed2-8bcc-492d-b845-15308bace4e8 service.beta.kubernetes.io/aws-load-balancer-ssl-negotiation-policy: "ELBSecurityPolicy-TLS13-1-2-Res-2021-06" service.beta.kubernetes.io/aws-load-balancer-ssl-ports: "443" service.beta.kubernetes.io/aws-load-balancer-type: "external" service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: "ip" service.beta.kubernetes.io/aws-load-balancer-scheme: "internet-facing" labels: app.kubernetes.io/name: vms-core-server region: ap-southeast-1 spec: loadBalancerClass: service.k8s.aws/nlb selector: app.kubernetes.io/name: vms-core-server region: ap-southeast-1 ports: - port: 443 protocol: TCP name: cloud-access-443 targetPort: cloud-access type: LoadBalancer externalTrafficPolicy: Cluster --- apiVersion: v1 kind: Service metadata: name: vms-core-server-cloud-access-pa-fw-v2 namespace: dev3-vms annotations: service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags: "Category=dev,Product=vms,ServiceType=biz" service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:ap-southeast-1:242777933053:certificate/e667c161-e7b0-4faa-a21e-23df5cb5f2d4 service.beta.kubernetes.io/aws-load-balancer-ssl-negotiation-policy: "ELBSecurityPolicy-TLS13-1-2-Res-2021-06" service.beta.kubernetes.io/aws-load-balancer-ssl-ports: "443" service.beta.kubernetes.io/aws-load-balancer-type: "external" service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: "ip" service.beta.kubernetes.io/aws-load-balancer-scheme: "internet-facing" labels: app.kubernetes.io/name: vms-core-server region: ap-southeast-1 spec: loadBalancerClass: service.k8s.aws/nlb selector: app.kubernetes.io/name: vms-core-server region: ap-southeast-1 ports: - port: 443 protocol: TCP name: cloud-access-443 targetPort: cloud-access type: LoadBalancer externalTrafficPolicy: Cluster service-monitor.yaml: apiVersion: v1 kind: Service metadata: labels: app.kubernetes.io/name: vms-core-server monitoring: service name: vms-core-server-aps1 namespace: dev3-vms spec: ports: - name: http-actuator port: 9091 protocol: TCP targetPort: http-actuator - name: grpc port: 8850 protocol: TCP targetPort: grpc - port: 8080 targetPort: http protocol: TCP name: http - port: 8082 targetPort: event protocol: TCP name: event - name: ops port: 10080 protocol: TCP targetPort: ops - name: internal port: 80 protocol: TCP targetPort: internal - name: websocket port: 8090 protocol: TCP targetPort: websocket - name: cloud-access port: 8083 protocol: TCP targetPort: cloud-access - name: cloud-access-short port: 8084 protocol: TCP targetPort: cloud-access-short - name: ai port: 8092 protocol: TCP targetPort: ai selector: app.kubernetes.io/name: vms-core-server region: ap-southeast-1 type: ClusterIP
10-18
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值