开发者社区> 问答> 正文

重启docker,访问不了面板,logs里报错:EXIT CODE: 0

docker ps -a,状态如下: f28694c5e6b8 canal/otter-all "/alidata/bin/main.s…" 5 weeks ago Exited (1) 3 minutes ago otter-all

查看logs,详细如下:

[root@localhost ~]# docker logs f28694c5e6b8 DOCKER_DEPLOY_TYPE=VM ==> INIT /alidata/init/02init-sshd.sh ==> EXIT CODE: 0 ==> INIT /alidata/init/fix-hosts.py ==> EXIT CODE: 0 ==> INIT DEFAULT Generating SSH1 RSA host key: [ OK ] Starting sshd: [ OK ] Starting crond: [ OK ] ==> INIT DONE ==> RUN /home/admin/app.sh ==> START ... start mysql ... Starting mysqld: [ OK ] mysql start successful start zookeeper ... zookeeper start successful start manager ... manager start successful start node ... node start successful you can visit manager link : http://192.168.40.73:8080/ , just have fun ! ==> START SUCCESSFUL ... ==> STOP stop node 192.168.40.73: stopping otter node 474 ... Oook! cost:2 stop node successful ... stop manager stop manager successful ... stop zookeeper stop zookeeper successful ... stop zookeeper stop zookeeper successful ... stop mysql ... DOCKER_DEPLOY_TYPE=VM ==> INIT /alidata/init/02init-sshd.sh ==> EXIT CODE: 0 ==> INIT /alidata/init/fix-hosts.py ==> EXIT CODE: 0 ==> INIT DEFAULT Starting sshd: [ OK ] Starting crond: [ OK ] ==> INIT DONE ==> RUN /home/admin/app.sh ==> START ... start mysql ... Starting mysqld: [ OK ] mysql start successful start zookeeper ... zookeeper start successful start manager ... manager start successful start node ... node start successful you can visit manager link : http://192.168.40.73:8080/ , just have fun ! ==> START SUCCESSFUL ... ==> STOP stop node 192.168.40.73: stopping otter node 417 ... Oook! cost:3 stop node successful ... stop manager stop manager successful ... stop zookeeper stop zookeeper successful ... stop zookeeper stop zookeeper successful ... stop mysql ... DOCKER_DEPLOY_TYPE=VM ==> INIT /alidata/init/02init-sshd.sh ==> EXIT CODE: 0 ==> INIT /alidata/init/fix-hosts.py ==> EXIT CODE: 0 ==> INIT DEFAULT Starting sshd: [ OK ] Starting crond: [ OK ] ==> INIT DONE ==> RUN /home/admin/app.sh ==> START ... start mysql ... Starting mysqld: [ OK ] mysql start successful start zookeeper ... zookeeper start successful start manager ... manager start successful start node ... node start successful you can visit manager link : http://192.168.40.73:8080/ , just have fun ! ==> START SUCCESSFUL ... DOCKER_DEPLOY_TYPE=VM ==> INIT /alidata/init/02init-sshd.sh ==> EXIT CODE: 0 ==> INIT /alidata/init/fix-hosts.py ==> EXIT CODE: 0 ==> INIT DEFAULT Starting sshd: [ OK ] Starting crond: [ OK ] ==> INIT DONE ==> RUN /home/admin/app.sh ==> START ... start mysql ... Starting mysqld: [ OK ] mysql start successful start zookeeper ... zookeeper start successful start manager ... DOCKER_DEPLOY_TYPE=VM ==> INIT /alidata/init/02init-sshd.sh ==> EXIT CODE: 0 ==> INIT /alidata/init/fix-hosts.py ==> EXIT CODE: 0 ==> INIT DEFAULT Starting sshd: [ OK ] Starting crond: [ OK ] ==> INIT DONE ==> RUN /home/admin/app.sh ==> START ... start mysql ... Starting mysqld: [ OK ] mysql start successful start zookeeper ... zookeeper start successful start manager ... DOCKER_DEPLOY_TYPE=VM ==> INIT /alidata/init/02init-sshd.sh ==> EXIT CODE: 0 ==> INIT /alidata/init/fix-hosts.py ==> EXIT CODE: 0 ==> INIT DEFAULT Starting sshd: [ OK ] Starting crond: [ OK ] ==> INIT DONE ==> RUN /home/admin/app.sh ==> START ... start mysql ... Starting mysqld: [ OK ] mysql start successful start zookeeper ... zookeeper start successful start manager ... DOCKER_DEPLOY_TYPE=VM ==> INIT /alidata/init/02init-sshd.sh ==> EXIT CODE: 0 ==> INIT /alidata/init/fix-hosts.py ==> EXIT CODE: 0 ==> INIT DEFAULT Starting sshd: [ OK ] Starting crond: [ OK ] ==> INIT DONE ==> RUN /home/admin/app.sh ==> START ... start mysql ... Starting mysqld: [ OK ] mysql start successful start zookeeper ... zookeeper start successful start manager ... DOCKER_DEPLOY_TYPE=VM ==> INIT /alidata/init/02init-sshd.sh ==> EXIT CODE: 0 ==> INIT /alidata/init/fix-hosts.py ==> EXIT CODE: 0 ==> INIT DEFAULT Starting sshd: [ OK ] Starting crond: [ OK ] ==> INIT DONE ==> RUN /home/admin/app.sh ==> START ... start mysql ... Starting mysqld: [ OK ] mysql start successful start zookeeper ... zookeeper start successful start manager ... DOCKER_DEPLOY_TYPE=VM ==> INIT /alidata/init/02init-sshd.sh ==> EXIT CODE: 0 ==> INIT /alidata/init/fix-hosts.py ==> EXIT CODE: 0 ==> INIT DEFAULT Starting sshd: [ OK ] Starting crond: [ OK ] ==> INIT DONE ==> RUN /home/admin/app.sh ==> START ... start mysql ... Starting mysqld: [ OK ] mysql start successful start zookeeper ... zookeeper start successful start manager ... DOCKER_DEPLOY_TYPE=VM ==> INIT /alidata/init/02init-sshd.sh ==> EXIT CODE: 0 ==> INIT /alidata/init/fix-hosts.py ==> EXIT CODE: 0 ==> INIT DEFAULT Starting sshd: [ OK ] Starting crond: [ OK ] ==> INIT DONE ==> RUN /home/admin/app.sh ==> START ... start mysql ... Starting mysqld: [ OK ] mysql start successful start zookeeper ... zookeeper start successful start manager ...

原提问者GitHub用户jimstory

展开
收起
古拉古拉 2023-06-14 21:52:56 97 0
3 条回答
写回答
取消 提交回答
  • 值得去的地方都没有捷径

    根据您提供的信息,容器启动后即退出了,这是因为容器内的进程已经停止。在您提供的日志中,可以看到容器启动了多次,但都在启动成功后退出了。因此,您需要检查容器启动时的配置和日志,以找出问题的根本原因。

    您可以通过以下步骤来解决此问题:

    检查容器内的进程是否正在运行。您可以使用以下命令进入容器并检查进程状态:

    docker exec -it f28694c5e6b8 /bin/bash ps -ef

    检查容器启动时使用的命令和参数是否正确。您可以使用以下命令查看容器的启动命令:

    docker inspect f28694c5e6b8

    检查容器的日志以查看错误消息。您可以使用以下命令查看容器的日志:

    docker logs f28694c5e6b8

    确保容器的配置文件正确。您可以使用以下命令检查容器中的配置文件:

    docker exec -it f28694c5e6b8 /bin/bash cat /path/to/config/file

    根据您提供的日志,容器启动后即退出了,而且没有任何错误消息。因此,您可能需要检查容器的配置文件和启动命令以找出问题的根本原因。如果您无法解决问题,请提供更多详细信息,以便我们更好地帮助您。

    2023-06-15 17:39:46
    赞同 展开评论 打赏
  • 从日志来看,其实 OTTER 可以正常启动,但是可能存在某些问题导致 OTTER 无法正常访问面板。

    首先,您可以通过以下命令启动 OTTER 容器时,打开端口映射,将宿主机的 8080 端口映射到容器内的 8080 端口,以确保可以通过宿主机访问 OTTER 的面板:

    docker run --name my-otter -p 8080:8080 canal/otter-all
    

    如果您已经使用了此命令启动了 OTTER 容器,请在宿主机中使用浏览器访问以下 URL:http://localhost:8080,检查是否能够访问 OTTER 的面板。

    另外,您也可以查看 OTTER 的日志中,是否有关于面板访问失败的相关信息。具体命令如下:

    docker logs my-otter
    

    日志输出可能会很长,请查找与访问 OTTER 面板有关的错误信息,并针对错误信息去检查配置、环境等方面的问题。

    2023-06-15 10:09:09
    赞同 展开评论 打赏
  • 我这样做了一下,发现了一个问题 重启服务器,容器启动不了,确实是manager没有启动成功 但是, 1,把原来的数据zkData文件夹备份 2,重新安装 3,替换备份文件夹 这才能启动,数据还在

    原回答者GitHub用户jimstory

    2023-06-14 22:30:16
    赞同 展开评论 打赏
问答排行榜
最热
最新

相关电子书

更多
应用 Docker 进行持续交付:用技术改变交付路程 立即下载
从Docker到容器服务 立即下载
Docker@Alibaba——超大规模Docker化的实战经验 立即下载