Bootstrap

RabbitMQ - Log Files

by Jeremy Canfield | Updated: April 28 2021 | RabbitMQ articles

By default, on a Linux system, the RabbitMQ log files are located in the /var/log/rabbitmq directory, like this:

ls -l /var/log/rabbitmq/
. . .
-rw-r--r--. 1 rabbitmq root  153717 Jun  8 21:20 rabbit@server001.log
-rw-r--r--. 1 rabbitmq root   60686 Jun  8 21:20 rabbit@server001-sasl.log

Or an alternate directory and log file can be be defined in the main RabbitMQ configuration file, like this (in INI format).

log.dir = /usr/local/logs/rabbitmq
log.file = rabbit.log

Here is an example of what you might find in rabbit@server001.log.

2020-09-29 15:47:24.585 [info] <0.2478.160> accepting AMQP connection <0.2478.160> (10.20.15.115:55750 -> 10.17.114.12:5671)

2020-09-29 15:47:24.630 [info] <0.2478.160> Connection <0.2478.160> (10.20.15.115:55750 -> 10.17.114.12:5671) has a client-provided name: rabbitConnectionFactory#0

2020-09-29 15:47:24.637 [info] <0.2478.160> connection <0.2478.160> (10.20.15.115:55750 -> 10.17.114.12:5671 - rabbitConnectionFactory#0): user 'john.doe' authenticated and granted access to vhost 'vhost001'

2020-09-29 15:47:45.313 [info] <0.2478.160> closing AMQP connection <0.2478.160> (10.20.15.115:55750 -> 10.17.114.12:5671 - rabbitConnectionFactory#0, vhost: 'vhost001', user: 'john.doe')

Did you find this article helpful?

If so, consider buying me a coffee over at

Comments

September 20 2025 by prasanth reddy

Hi jeremy, I have 3 node rabbitmq cluster. one of node disk /u1 is fill with 100%. we removed the mnesia directory. after that we tried to join the cluster. but unable to join the cluster. we are seeing below exception when we try to join rabbitmqctl join_cluster rabbit@rabbitmq-cluster-01.example.com Clustering node rabbit@rabbitmq-cluster-02.example.com with rabbit@rabbitmq-cluster-01.example.com Error: unable to perform an operation on node 'rabbit@rabbitmq-cluster-01.example.com'. Please see diagnostics information and suggestions below. Most common reasons for this are: * Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues) * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server) * Target node is not running In addition to the diagnostics info below: * See the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more * Consult server logs on node rabbit@rabbitmq-cluster-01.example.com * If target node is configured to use long node names, don't forget to use --longnames with CLI tools DIAGNOSTICS =========== attempted to contact: ['rabbit@rabbitmq-cluster-01.example.com'] rabbit@rabbitmq-cluster-01.example.com: * connected to epmd (port 4369) on rabbitmq-cluster-01.example.com * node rabbit@rabbitmq-cluster-01.example.com up, 'rabbit' application running Current node details: * node name: 'rabbitmqcli-16796-rabbit@rabbitmq-cluster-02.example.com' * effective user's home directory: /u1/uc_rabbitmq_stage * Erlang cookie hash: zQ9nqcnsr2w+afMYJetB1g== config file is in /etc/rabbitmq/rabbitmq.conf cluster_name = RABBIT-STAGE cluster_formation.peer_discovery_backend = classic_config cluster_formation.classic_config.nodes.1 = rabbit@rabbitmq-cluster-01.example.com cluster_formation.classic_config.nodes.2 = rabbit@rabbitmq-cluster-02.example.com cluster_formation.classic_config.nodes.3 = rabbit@rabbitmq-cluster-03.example.com cluster_partition_handling = autoheal log.file = rabbitmq.log log.dir = /var/log/rabbitmq log.file.level = info log.connection.level = info log.connection.file = rabbitma_connecction.log log.channel.level = info log.channel.file = rabbitmq_channel.log log.queue.level = info log.queue.file = rabbitmq_queue.log /etc/rabbitmq/rabbitmq-env.conf HOME=/u1/uc_rabbitmq_stage RABBITMQ_USE_LONGNAME=True NODENAME=rabbit@rabbitmq-cluster-02.example.com -rw-r--r-- 1 rabbitmq rabbitmq 679 Jun 17 2024 /etc/rabbitmq/rabbitmq.conf -rw-r--r-- 1 rabbitmq rabbitmq 112 Sep 20 11:31 /etc/rabbitmq/rabbitmq-env.conf .erlang.cookie is in /u1/uc_rabbitmq_stage, /home/rabbitmq, /var/lib/rabbitmq which is sym link to /u1/uc_rabbitmq_stage and /root. file owner and group is rabbitmq permission is 400 Could you please let me know why rabbitmqctl command generating the new cookie and how to overcome this issue?

Did you find this article helpful?

Comments

Add a Comment