RabbitMQ 設定檔在哪裡,因為它的日誌顯示“設定檔:(無)”

RabbitMQ 設定檔在哪裡,因為它的日誌顯示“設定檔:(無)”

我是 RabbitMQ 新手,在測試虛擬機器上新安裝了 RabbitMQ 3.7.17,它運作正常,我可以登入其 Web 介面。

我正在查看前任工程師留下的一些不清楚的註釋,提到了management.listener.port = 9999和的一些必需的配置更改management.listener.ip = 0.0.0.0。初步認為這些項屬於RabbitMQ的設定鍵,所以希望找到該文件並確認。

我檢查了日誌文件,它包含在開頭。我還嘗試了命令,但輸出不包含任何有關./var/log/rabbitmq/[email protected]config file(s) : (none)rabbitmq-diagnostics status -n rabbit@payvconfig

我找到了另一個文件/usr/share/doc/rabbitmq-server-3.7.17/rabbitmq.config.example,但不確定這是否是用於創建配置文件的範例。

我的問題是:

  • 我需要確認management.listener.port確實management.listener.ip是配置鍵。
  • 設定檔位於哪裡,如果遺失如何建立它?

任何指示都將受到高度讚賞,如果您需要更多信息,請告訴我。

更多日誌檔:

2021-08-11 16:41:40.648 [info] <0.8.0> Log file opened with Lager
2021-08-11 16:41:41.380 [info] <0.8.0> Feature flags: list of feature flags found:
2021-08-11 16:41:41.380 [info] <0.8.0> Feature flags: feature flag states written to disk: yes
2021-08-11 16:41:41.404 [info] <0.220.0>
 Starting RabbitMQ 3.7.17 on Erlang 21.3.8.6
 Copyright (C) 2007-2019 Pivotal Software, Inc.
 Licensed under the MPL.  See https://www.rabbitmq.com/
2021-08-11 16:41:41.404 [info] <0.220.0>
 node           : rabbit@payv
 home dir       : /var/lib/rabbitmq
 config file(s) : (none)
 cookie hash    : bpwgtZuS4DLf4bvseoUPpQ==
 log(s)         : /var/log/rabbitmq/[email protected]
                : /var/log/rabbitmq/rabbit@payv_upgrade.log
 database dir   : /var/lib/rabbitmq/mnesia/rabbit@payv
2021-08-11 16:41:41.410 [info] <0.220.0> Running boot step pre_boot defined by app rabbit
2021-08-11 16:41:41.410 [info] <0.220.0> Running boot step rabbit_core_metrics defined by app rabbit
2021-08-11 16:41:41.410 [info] <0.220.0> Running boot step rabbit_alarm defined by app rabbit
2021-08-11 16:41:41.415 [info] <0.226.0> Memory high watermark set to 1515 MiB (1589220147 bytes) of 3788 MiB (3973050368 bytes) total
2021-08-11 16:41:41.418 [info] <0.228.0> Enabling free disk space monitoring
2021-08-11 16:41:41.418 [info] <0.228.0> Disk free limit set to 50MB
2021-08-11 16:41:41.421 [info] <0.220.0> Running boot step code_server_cache defined by app rabbit
2021-08-11 16:41:41.421 [info] <0.220.0> Running boot step file_handle_cache defined by app rabbit
2021-08-11 16:41:41.421 [info] <0.231.0> Limiting to approx 32668 file handles (29399 sockets)
2021-08-11 16:41:41.421 [info] <0.232.0> FHC read buffering:  OFF
2021-08-11 16:41:41.421 [info] <0.232.0> FHC write buffering: ON
2021-08-11 16:41:41.421 [info] <0.220.0> Running boot step worker_pool defined by app rabbit
2021-08-11 16:41:41.421 [info] <0.221.0> Will use 4 processes for default worker pool
2021-08-11 16:41:41.422 [info] <0.221.0> Starting worker pool 'worker_pool' with 4 processes in it
2021-08-11 16:41:41.422 [info] <0.220.0> Running boot step database defined by app rabbit
2021-08-11 16:41:41.422 [info] <0.220.0> Node database directory at /var/lib/rabbitmq/mnesia/rabbit@payv is empty. Assuming we need to join an existing cluster or initialise from scratch...
2021-08-11 16:41:41.422 [info] <0.220.0> Configured peer discovery backend: rabbit_peer_discovery_classic_config
2021-08-11 16:41:41.422 [info] <0.220.0> Will try to lock with peer discovery backend rabbit_peer_discovery_classic_config
2021-08-11 16:41:41.422 [info] <0.220.0> Peer discovery backend does not support locking, falling back to randomized delay
2021-08-11 16:41:41.422 [info] <0.220.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping randomized startup delay.
2021-08-11 16:41:41.422 [info] <0.220.0> All discovered existing cluster peers:
2021-08-11 16:41:41.422 [info] <0.220.0> Discovered no peer nodes to cluster with
2021-08-11 16:41:41.423 [info] <0.43.0> Application mnesia exited with reason: stopped
2021-08-11 16:41:41.493 [info] <0.220.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2021-08-11 16:41:41.506 [info] <0.220.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2021-08-11 16:41:41.535 [info] <0.220.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2021-08-11 16:41:41.535 [info] <0.220.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping registration.
2021-08-11 16:41:41.535 [info] <0.220.0> Running boot step database_sync defined by app rabbit
2021-08-11 16:41:41.535 [info] <0.220.0> Running boot step feature_flags defined by app rabbit
2021-08-11 16:41:41.535 [info] <0.220.0> Running boot step codec_correctness_check defined by app rabbit
2021-08-11 16:41:41.535 [info] <0.220.0> Running boot step external_infrastructure defined by app rabbit
2021-08-11 16:41:41.535 [info] <0.220.0> Running boot step rabbit_registry defined by app rabbit
2021-08-11 16:41:41.535 [info] <0.220.0> Running boot step rabbit_auth_mechanism_cr_demo defined by app rabbit
2021-08-11 16:41:41.536 [info] <0.220.0> Running boot step rabbit_queue_location_random defined by app rabbit
2021-08-11 16:41:41.536 [info] <0.220.0> Running boot step rabbit_event defined by app rabbit
2021-08-11 16:41:41.536 [info] <0.220.0> Running boot step rabbit_auth_mechanism_amqplain defined by app rabbit
2021-08-11 16:41:41.536 [info] <0.220.0> Running boot step rabbit_auth_mechanism_plain defined by app rabbit
2021-08-11 16:41:41.536 [info] <0.220.0> Running boot step rabbit_exchange_type_direct defined by app rabbit
2021-08-11 16:41:41.536 [info] <0.220.0> Running boot step rabbit_exchange_type_fanout defined by app rabbit
2021-08-11 16:41:41.536 [info] <0.220.0> Running boot step rabbit_exchange_type_headers defined by app rabbit
2021-08-11 16:41:41.536 [info] <0.220.0> Running boot step rabbit_exchange_type_topic defined by app rabbit
2021-08-11 16:41:41.536 [info] <0.220.0> Running boot step rabbit_mirror_queue_mode_all defined by app rabbit
2021-08-11 16:41:41.536 [info] <0.220.0> Running boot step rabbit_mirror_queue_mode_exactly defined by app rabbit
2021-08-11 16:41:41.536 [info] <0.220.0> Running boot step rabbit_mirror_queue_mode_nodes defined by app rabbit

答案1

查看 /etc/rabbitmq/ 中類似rabbitmq.conf 的檔案。也可以在 /data/configuration/rabbitmq/rabbitmq.conf 中

更多資訊可以在文件中找到https://www.rabbitmq.com/configure.html#config-file

相關內容