halo docker容器自动停止

[LDYang694]

是什么版本出现了此问题？

halo:2.0.2

使用的什么数据库？

H2

使用的哪种方式部署？

Docker Compose

在线站点地址

https://server.szhhh.top/

发生了什么？

使用docker compose部署后，可以正常访问。但如果将ssh断开连接后无法正常访问，从后台监控看出在ssh断开后内存占用下降，重新连接ssh后可以正常访问并且内存占用恢复正常。通过查看docker日志像是docker在ssh断开连接后自动关闭了？在重新连接后又自动重启了？我所有的配置都是按照官方文档的配置，并使用了nginx反向代理(从目前的情况来看好像和nginx没有关系？) 使用的是2核2G轻量级应用服务器，可能是什么方面的原因？

相关日志输出

2023-01-01T15:28:09.873+08:00  INFO 7 --- [tReconciler-t-9] org.wltea.analyzer.dic.Dictionary        : 加载扩展停止词典:org/wltea/analyzer/dic/stopword.dic
2023-01-01T15:28:10.038+08:00  INFO 7 --- [         task-1] run.halo.app.search.IndicesInitializer   : Initialized post indices. Usage: StopWatch 'PostIndicesWatch': running time = 2628994538 ns; [rebuild] took 2628994538 ns = 100%
2023-01-01T15:28:10.390+08:00  INFO 7 --- [tReconciler-t-9] r.h.a.e.controller.RequestSynchronizer   : Started request(class run.halo.app.core.extension.content.Post) synchronizer.
2023-01-01T15:28:10.813+08:00  WARN 7 --- [eReconciler-t-1] r.h.a.c.e.service.DefaultRoleService     : Detected a cycle in role dependencies: role-template-view-snaphosts,and skipped automatically
2023-01-01T15:28:10.818+08:00  WARN 7 --- [eReconciler-t-1] r.h.a.c.e.service.DefaultRoleService     : Detected a cycle in role dependencies: role-template-view-categories,and skipped automatically
2023-01-01T15:28:10.818+08:00  WARN 7 --- [eReconciler-t-1] r.h.a.c.e.service.DefaultRoleService     : Detected a cycle in role dependencies: role-template-view-tags,and skipped automatically
2023-01-01T15:28:10.942+08:00  WARN 7 --- [eReconciler-t-1] r.h.a.c.e.service.DefaultRoleService     : Detected a cycle in role dependencies: role-template-view-snaphosts,and skipped automatically

    __  __      __
   / / / /___ _/ /___
  / /_/ / __ `/ / __ \
 / __  / /_/ / / /_/ /
/_/ /_/\__,_/_/\____/

Version: 2.0.2
2023-01-01T15:29:37.954+08:00  INFO 8 --- [           main] run.halo.app.Application                 : Starting Application v2.0.2 using Java 17.0.5 with PID 8 (/application/BOOT-INF/classes started by root in /application)
2023-01-01T15:29:37.958+08:00  INFO 8 --- [           main] run.halo.app.Application                 : No active profile set, falling back to 1 default profile: "default"
2023-01-01T15:29:40.256+08:00  INFO 8 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode
2023-01-01T15:29:40.259+08:00  INFO 8 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data R2DBC repositories in DEFAULT mode.
2023-01-01T15:29:40.586+08:00  INFO 8 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 321 ms. Found 1 R2DBC repository interfaces.
2023-01-01T15:29:42.535+08:00  INFO 8 --- [           main] org.pf4j.DefaultPluginStatusProvider     : Enabled plugins: []
2023-01-01T15:29:42.537+08:00  INFO 8 --- [           main] org.pf4j.DefaultPluginStatusProvider     : Disabled plugins: []
2023-01-01T15:29:42.540+08:00  INFO 8 --- [           main] org.pf4j.DefaultPluginManager            : PF4J version 3.8.0 in 'deployment' mode
2023-01-01T15:29:44.972+08:00  INFO 8 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 1 endpoint(s) beneath base path '/actuator'
2023-01-01T15:29:45.722+08:00  WARN 8 --- [           main] ion$DefaultTemplateResolverConfiguration : Cannot find template location: classpath:/templates/ (please add some templates, check your Thymeleaf configuration, or set spring.thymeleaf.check-template-location=false)
2023-01-01T15:29:45.970+08:00  INFO 8 --- [           main] o.s.b.web.embedded.netty.NettyWebServer  : Netty started on port 8090
2023-01-01T15:29:45.972+08:00  INFO 8 --- [           main] r.h.a.e.controller.DefaultController     : Starting controller run.halo.app.search.post.PostEventReconciler
2023-01-01T15:29:46.029+08:00  INFO 8 --- [tReconciler-t-1] r.h.a.e.controller.DefaultController     : Controller worker run.halo.app.search.post.PostEventReconciler-worker-1 started
2023-01-01T15:29:46.094+08:00  INFO 8 --- [           main] run.halo.app.Application                 : Started Application in 8.737 seconds (process running for 9.583)
2023-01-01T15:29:47.229+08:00  INFO 8 --- [           main] r.h.a.e.controller.DefaultController     : Starting controller garbage-collector-controller
2023-01-01T15:29:47.233+08:00  INFO 8 --- [-controller-t-1] r.h.a.e.controller.DefaultController     : Controller worker garbage-collector-controller-worker-1 started
2023-01-01T15:29:47.238+08:00  INFO 8 --- [-controller-t-2] r.h.a.e.controller.DefaultController     : Controller worker garbage-collector-controller-worker-2 started
2023-01-01T15:29:47.248+08:00  INFO 8 --- [-controller-t-3] r.h.a.e.controller.DefaultController     : Controller worker garbage-collector-controller-worker-3 started
2023-01-01T15:29:47.248+08:00  INFO 8 --- [-controller-t-4] r.h.a.e.controller.DefaultController     : Controller worker garbage-collector-controller-worker-4 started
2023-01-01T15:29:47.253+08:00  INFO 8 --- [-controller-t-5] r.h.a.e.controller.DefaultController     : Controller worker garbage-collector-controller-worker-5 started
2023-01-01T15:29:47.259+08:00  INFO 8 --- [-controller-t-6] r.h.a.e.controller.DefaultController     : Controller worker garbage-collector-controller-worker-6 started
2023-01-01T15:29:47.265+08:00  INFO 8 --- [-controller-t-7] r.h.a.e.controller.DefaultController     : Controller worker garbage-collector-controller-worker-7 started
2023-01-01T15:29:47.265+08:00  INFO 8 --- [-controller-t-8] r.h.a.e.controller.DefaultController     : Controller worker garbage-collector-controller-worker-8 started
2023-01-01T15:29:47.270+08:00  INFO 8 --- [-controller-t-9] r.h.a.e.controller.DefaultController     : Controller worker garbage-collector-controller-worker-9 started
2023-01-01T15:29:47.280+08:00  INFO 8 --- [controller-t-10] r.h.a.e.controller.DefaultController     : Controller worker garbage-collector-controller-worker-10 started
2023-01-01T15:29:47.283+08:00  INFO 8 --- [           main] r.h.a.e.controller.DefaultController     : Starting controller run.halo.app.core.extension.reconciler.CategoryReconciler
2023-01-01T15:29:47.289+08:00  INFO 8 --- [           main] r.h.a.e.controller.DefaultController     : Starting controller run.halo.app.core.extension.reconciler.CommentReconciler
2023-01-01T15:29:47.289+08:00  INFO 8 --- [yReconciler-t-1] r.h.a.e.controller.DefaultController     : Controller worker run.halo.app.core.extension.reconciler.CategoryReconciler-worker-1 started
2023-01-01T15:29:47.290+08:00  INFO 8 --- [yReconciler-t-1] r.h.a.e.controller.RequestSynchronizer   : Starting request(class run.halo.app.core.extension.content.Category) synchronizer...
2023-01-01T15:29:47.292+08:00  INFO 8 --- [           main] r.h.a.e.controller.DefaultController     : Starting controller run.halo.app.core.extension.reconciler.MenuItemReconciler
2023-01-01T15:29:47.297+08:00  INFO 8 --- [tReconciler-t-1] r.h.a.e.controller.DefaultController     : Controller worker run.halo.app.core.extension.reconciler.CommentReconciler-worker-1 started

附加信息

[it985]

https://docs.halo.run/getting-started/install/docker-compose
docker-compose up -d docker-compose pull docker-compose logs -f 要进到docker-compose.yaml所在目录再执行命令

[LDYang694]

https://docs.halo.run/getting-started/install/docker-compose docker-compose up -d docker-compose pull docker-compose logs -f 要进到docker-compose.yaml所在目录再执行命令

我没有明白你的意思，我就是按照安装文档在docker-compose.yaml所在目录执行的命令，但我使用的是docker compose，中间是空格而不是-，这会有影响吗？

[ruibaby]

使用docker compose部署后，可以正常访问。但如果将ssh断开连接后无法正常访问

docker compose up -d，有加上 -d 吗？

[ruibaby]

/kind support

[guqing]

我没有明白你的意思，我就是按照安装文档在docker-compose.yaml所在目录执行的命令，但我使用的是docker compose，中间是空格而不是-，这会有影响吗？

参考： https://docs.docker.com/compose/gettingstarted/#step-8-experiment-with-some-other-commands

f you want to run your services in the background, you can pass the -d flag (for “detached” mode) to docker compose up and use docker compose ps to see what is currently running: $ docker compose up -d $ docker compose ps

[ruibaby]

/close

[f2c-ci-robot[bot]]

@ruibaby: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.