ubuntu RabbitMQ无法从停靠组合 Boot

uinbv5nw  于 2022-11-02  发布在  RabbitMQ
关注(0)|答案(1)|浏览(479)

我正在尝试从docker-compose命令设置rabbitmq示例。
我的 Docker 组成yaml

version: '3.8'

services:
  rabbitmq:
    image: rabbitmq:3-management
    hostname: rabbit
    container_name: 'rabbitmq'
    volumes:
      - ./etc/rabbitmq.conf:/etc/rabbitmq/rabbitmq.conf
      - ./data:/var/lib/rabbitmq/mnesia/rabbit@rabbit
      - ./logs:/var/log/rabbitmq/log
      - ./etc/ssl/CERT_LAB_CA.pem:/etc/rabbitmq/ssl/cacert.pem
      - ./etc/ssl/CERT_LAB_RABBITMQ.pem:/etc/rabbitmq/ssl/cert.pem
      - ./etc/ssl/KEY_LAB_RABBITMQ.pem:/etc/rabbitmq/ssl/key.pem
    ports:
      - 5672:5672
      - 15672:15672
      - 15671:15671
      - 5671:5671
    environment:
      - RABBITMQ_DEFAULT_USER=secret
      - RABBITMQ_DEFAULT_PASS=secret

当我第一次运行docker compose up时,一切都运行正常。但是当我添加队列和交换(从definitions.json加载),关闭并删除容器,然后再次尝试运行docker compose up时,我得到了这个错误

2022-09-29 13:32:09.522956+00:00 [notice] <0.44.0> Application mnesia exited with reason: stopped
2022-09-29 13:32:09.523096+00:00 [error] <0.229.0>
2022-09-29 13:32:09.523096+00:00 [error] <0.229.0> BOOT FAILED
2022-09-29 13:32:09.523096+00:00 [error] <0.229.0> ===========
2022-09-29 13:32:09.523096+00:00 [error] <0.229.0> Error during startup: {error,
2022-09-29 13:32:09.523096+00:00 [error] <0.229.0>                           {schema_integrity_check_failed,
2022-09-29 13:32:09.523096+00:00 [error] <0.229.0>                               [{table_missing,rabbit_listener}]}}
2022-09-29 13:32:09.523096+00:00 [error] <0.229.0>

BOOT FAILED
===========
Error during startup: {error,
                          {schema_integrity_check_failed,
                              [{table_missing,rabbit_listener}]}}

2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>   crasher:
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>     initial call: application_master:init/4
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>     pid: <0.228.0>
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>     registered_name: []
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>     exception exit: {{schema_integrity_check_failed,
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>                          [{table_missing,rabbit_listener}]},
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>                      {rabbit,start,[normal,[]]}}
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>       in function  application_master:init/4 (application_master.erl, line 142)
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>     ancestors: [<0.227.0>]
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>     message_queue_len: 1
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>     messages: [{'EXIT',<0.229.0>,normal}]
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>     links: [<0.227.0>,<0.44.0>]
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>     dictionary: []
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>     trap_exit: true
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>     status: running
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>     heap_size: 2586
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>     stack_size: 28
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>     reductions: 180
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>   neighbours:
2022-09-29 13:32:10.524073+00:00 [error] <0.228.0>

这是我的rabbitmq.conf文件

listeners.tcp.default = 5672
listeners.ssl.default = 5671
ssl_options.cacertfile = /etc/rabbitmq/ssl/cacert.pem
ssl_options.certfile = /etc/rabbitmq/ssl/cert.pem
ssl_options.keyfile = /etc/rabbitmq/ssl/key.pem

# Generate client cert and uncomment this if client has to provide cert.

# ssl_options.verify = verify_peer

# ssl_options.fail_if_no_peer_cert = true

collect_statistics_interval = 10000

# load_definitions = /path/to/exported/definitions.json

# definitions.skip_if_unchanged = true

management.tcp.port = 15672

management.ssl.port       = 15671
management.ssl.cacertfile = /etc/rabbitmq/ssl/cacert.pem
management.ssl.certfile   = /etc/rabbitmq/ssl/cert.pem
management.ssl.keyfile    = /etc/rabbitmq/ssl/key.pem

management.http_log_dir = /var/log/rabbitmq/http

我错过了什么?

lzfw57am

lzfw57am1#

我遇到了同样的错误,并花了相当长的时间试图找出问题。我的配置与你的略有不同,看起来像这样:

rabbitmq:
  image: rabbitmq:3.11.2-management-alpine
  hostname: rabbitmq
  environment:
    RABBITMQ_DEFAULT_USER: tester
    RABBITMQ_DEFAULT_PASS: qwerty
    RABBITMQ_MNESIA_DIR: /my-custom-data-folder-path-inside-container
    RABBITMQ_NODENAME: rabbitmq
  volumes:
    - type: bind
      source: /my-custom-data-folder-path-on-host
      target: /my-custom-data-folder-path-inside-container

我不是RabbitMQ的Maven,我的想法是让RabbitMQ将其数据库保存在主机上的/my-custom-data-folder-path-on-host文件夹中。就像您的情况一样,在第一次运行时,它能够成功启动,但在重新启动容器后,我得到了以下错误:
Boot FAILED启动过程中出现错误:{error,{schema_integrity_check_failed,[{table_missing,rabbit_listener}]}}我从文档中了解到,rabbit_listener是由RabbitMQ使用的Mnesia数据库中的一个表,而“listener”是在RabbitMQ中配置的TCP侦听器,用于接受客户端连接。要使RabbitMQ接受客户端连接,它需要绑定到一个或多个接口并侦听(特定于协议的)端口。在RabbitMQ的说法中,一个这样的接口/端口对称为侦听器。侦听器使用listeners.tcp.* 配置选项进行配置。
我想深入研究Mnesia数据库来排除故障,但没有Erlang知识就无法做到这一点。似乎由于某种原因,在第一次运行RabbitMQ时没有创建“rabbit_listener”表,但在后续运行时需要它。
最后,我设法通过更改初始配置来解决这个问题,如下所示:

service-bus:
  image: rabbitmq:3.11.2-management-alpine
  hostname: rabbitmq
  environment:
    RABBITMQ_DEFAULT_USER: tester
    RABBITMQ_DEFAULT_PASS: qwerty     
    RABBITMQ_NODENAME: rabbitmq
  volumes:
    - type: bind
      source: /my-custom-data-folder-path-on-host
      target: /var/lib/rabbitmq

我没有只覆盖RABBITMQ_MNESIA_DIR文件夹,而是覆盖了整个/var/lib/rabbitmq文件夹。这样就成功了,现在我的RabbitMQ成功地承受了重新启动。
根据您的配置,我认为如果您将./data:/var/lib/rabbitmq/mnesia/rabbit@rabbit替换为./data:/var/lib/rabbitmq,将解决此问题。

相关问题