로그에 "config file(s) : (none)"이 표시되므로 RabbitMQ 구성 파일은 어디에 있습니까?

로그에 "config file(s) : (none)"이 표시되므로 RabbitMQ 구성 파일은 어디에 있습니까?

저는 RabbitMQ를 처음 사용하고 테스트 가상 머신에 RabbitMQ 3.7.17을 새로 설치했습니다. 정상적으로 실행되며 해당 웹 인터페이스에 로그인할 수 있습니다.

이전 엔지니어가 남긴 불분명한 메모를 보고 있으며, 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

관련 정보