问题1:
Dubbo启动时qos-server can not bind localhost:22222
解决:本质上是占用端口,杀掉占用22222端口的进程就可以
问题2:
Zookeeper is not connected yet!
纠结了半天
1,可能是防火墙没关(我不是)
2,可能是zookeeper没有启动
[root@localhost bin]# ./zkServer.sh start
ZooKeeper JMX enabled by default
Using config: /opt/zookeeper/zookeeper-3.4.11/bin/../conf/zoo.cfg
Starting zookeeper ... already running as process 1165.
[root@localhost bin]# ./zkServer.sh status
ZooKeeper JMX enabled by default
Using config: /opt/zookeeper/zookeeper-3.4.11/bin/../conf/zoo.cfg
Error contacting service. It is probably not running.
这里可以看到启动的时候报已经启动,但是查看状态却说not running
解决:将zoo.cfg配置文件中存放数据的data目录下的zookeeper_server.pid文件删除,重新启动
[root@localhost bin]# cd ..
[root@localhost zookeeper-3.4.11]# ls
bin data ivy.xml README.md zookeeper-3.4.11.jar
build.xml dist-maven lib README_packaging.txt zookeeper-3.4.11.jar.asc
conf docs LICENSE.txt recipes zookeeper-3.4.11.jar.md5
contrib ivysettings.xml NOTICE.txt src zookeeper-3.4.11.jar.sha1
[root@localhost zookeeper-3.4.11]# cd data
[root@localhost data]# ll
总用量 4
drwxr-xr-x. 2 root root 166 3月 5 23:26 version-2
-rw-r--r--. 1 root root 4 3月 5 23:26 zookeeper_server.pid
[root@localhost data]# rm zookeeper_server.pid
rm:是否删除普通文件 "zookeeper_server.pid"?y
[root@localhost data]# ll
总用量 0
drwxr-xr-x. 2 root root 166 3月 5 23:26 version-2
重新启动成功
[root@localhost bin]# ./zkServer.sh start
ZooKeeper JMX enabled by default
Using config: /opt/zookeeper/zookeeper-3.4.11/bin/../conf/zoo.cfg
Starting zookeeper ... STARTED
[root@localhost bin]# ./zkServer.sh status
ZooKeeper JMX enabled by default
Using config: /opt/zookeeper/zookeeper-3.4.11/bin/../conf/zoo.cfg
Mode: standalone