Log analysis and troubleshooting in RabbitMQ - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Identify the error from RabbitMQ log snippet

Given the following RabbitMQ log snippet, what is the main error reported?

2024-04-01 10:15:23.456 [error] <0.123.0> closing AMQP connection <0.123.0> (192.168.1.10:5672 -> 192.168.1.20:5672): connection_closed_abruptly

A The connection was closed abruptly by the client.

B The RabbitMQ server failed to start due to port conflict.

C The queue was declared with an invalid name.

D The user authentication failed during connection.

💡 Hint

Look for keywords related to connection status in the log.

The log shows 'connection_closed_abruptly' which means the client closed the connection unexpectedly.

❓ Troubleshoot

intermediate

Troubleshoot RabbitMQ node not joining cluster

You try to join a RabbitMQ node to a cluster but it fails. The log shows:

=ERROR REPORT==== 1-Apr-2024::11:00:00 ===
** Node rabbit@node2 not responding to pings.

What is the most likely cause?

A The queue on node2 is full and blocking the cluster join.

B The RabbitMQ version on node2 is incompatible with the cluster.

C The node rabbit@node2 is down or unreachable on the network.

D The user permissions are not set correctly on node2.

💡 Hint

Check network connectivity and node status.

The error means the node is not reachable or not running, so it cannot respond to cluster pings.

❓ Configuration

advanced

Correct RabbitMQ configuration for log rotation

Which configuration snippet correctly enables log rotation by size in RabbitMQ's configuration file?

A

log.rotation.size = 10485760
log.file.rotation.count = 5

B

log.rotation.size = 10485760
log.rotation.count = 5

C

log.file.rotation.size = 10485760
log.rotation.count = 5

D

log.file.rotation.size = 10485760
log.file.rotation.count = 5

💡 Hint

Check the correct prefix for log rotation settings in RabbitMQ config.

The correct keys for log rotation in RabbitMQ config use 'log.file.rotation.size' and 'log.file.rotation.count'.

✅ Best Practice

advanced

Best practice for analyzing RabbitMQ logs in production

What is the best practice when analyzing RabbitMQ logs to troubleshoot intermittent connection issues in a production environment?

A Restart RabbitMQ service to clear logs and then check for errors.

B Enable debug level logging temporarily and collect logs during the issue window.

C Disable all logging to improve performance and avoid log clutter.

D Only check logs after the server crashes to find the root cause.

💡 Hint

Think about how to get detailed info without affecting production negatively.

Temporarily enabling debug logs helps capture detailed info during issues without permanent overhead.

🧠 Conceptual

expert

Understanding RabbitMQ log message levels

Which RabbitMQ log message level indicates a serious problem that requires immediate attention but does not stop the server from running?

A error

B warning

C info

D debug

💡 Hint

Consider severity levels from least to most critical.

Error level logs indicate serious problems that need attention but usually do not crash the server.

Practice

1. What is the primary purpose of RabbitMQ logs?

easy

A. To show what RabbitMQ is doing and help find problems

B. To store user data permanently

C. To speed up message delivery

D. To configure RabbitMQ settings automatically

Solution

1. Step 1: Understand the role of logs in RabbitMQ

   Logs record events and actions RabbitMQ performs, which helps in monitoring and troubleshooting.

2. Step 2: Identify the main use of logs

   Logs are not for storing user data or speeding delivery but for tracking system behavior and errors.

3. Final Answer:

   To show what RabbitMQ is doing and help find problems -> Option A

4. Quick Check:

   Logs = system activity and troubleshooting [OK]

Hint: Logs track activity and errors, not data or speed [OK]

Common Mistakes:

• Thinking logs store user messages
• Assuming logs configure RabbitMQ automatically
• Believing logs improve message speed

2. Which command correctly shows the last 50 lines of the RabbitMQ log file located at /var/log/rabbitmq/rabbit.log?

easy

A. head -n 50 /var/log/rabbitmq/rabbit.log

B. tail -n 50 /var/log/rabbitmq/rabbit.log

C. cat -n 50 /var/log/rabbitmq/rabbit.log

D. grep -n 50 /var/log/rabbitmq/rabbit.log

Solution

1. Step 1: Identify command to view last lines of a file

   The tail command shows the end of a file; -n 50 limits output to last 50 lines.

2. Step 2: Check other commands

   head shows the start, cat outputs whole file, grep searches text, so they don't fit.

3. Final Answer:

   tail -n 50 /var/log/rabbitmq/rabbit.log -> Option B

4. Quick Check:

   tail = last lines [OK]

Hint: Use tail -n for last lines, head for first lines [OK]

Common Mistakes:

• Using head instead of tail for last lines
• Using grep without search pattern
• Using cat with invalid options

3. Given the command rabbitmqctl status, what kind of information will it display?

medium

A. Current server health and status details

B. List of all messages in queues

C. Configuration file contents

D. User permissions and roles

Solution

1. Step 1: Understand what rabbitmqctl status shows

   This command provides a summary of the RabbitMQ server's health, including running nodes and memory usage.

2. Step 2: Differentiate from other data

   It does not list messages, config files, or user roles directly.

3. Final Answer:

   Current server health and status details -> Option A

4. Quick Check:

   rabbitmqctl status = server health [OK]

Hint: rabbitmqctl status shows server health info [OK]

Common Mistakes:

• Expecting message lists from status command
• Confusing config files with status output
• Thinking it shows user permissions

4. You run tail -f /var/log/rabbitmq/rabbit.log but see no new log entries when RabbitMQ processes messages. What is the most likely cause?

medium

A. tail command does not work with RabbitMQ logs

B. The log file path is incorrect

C. RabbitMQ server is stopped

D. RabbitMQ logging level is set too low to show message processing

Solution

1. Step 1: Check why logs don't update with tail -f

   If RabbitMQ is running but logs don't show activity, logging level may be too low to capture message events.

2. Step 2: Eliminate other causes

   If path was wrong, tail would error; if server stopped, no processing happens; tail works with any file.

3. Final Answer:

   RabbitMQ logging level is set too low to show message processing -> Option D

4. Quick Check:

   Low logging level hides events [OK]

Hint: Check logging level if logs stay empty during activity [OK]

Common Mistakes:

• Assuming tail command is faulty
• Not verifying RabbitMQ server status
• Ignoring logging level settings

5. You notice RabbitMQ logs show frequent "connection refused" errors. Which combined steps help you troubleshoot this issue effectively?

hard

A. Restart RabbitMQ service and clear all logs immediately

B. Increase log verbosity and delete all user accounts

C. Check RabbitMQ server status with rabbitmqctl status and verify firewall rules

D. Change RabbitMQ port without checking current configuration

Solution

1. Step 1: Verify RabbitMQ server is running

   Use rabbitmqctl status to confirm the server is up and accepting connections.

2. Step 2: Check network and firewall settings

   Connection refused often means network blocks or firewall rules prevent access; verify these settings.

3. Final Answer:

   Check RabbitMQ server status with rabbitmqctl status and verify firewall rules -> Option C

4. Quick Check:

   Status + firewall check = fix connection refused [OK]

Hint: Check server status and firewall for connection refused errors [OK]

Common Mistakes:

• Restarting service without checking status
• Deleting users unnecessarily
• Changing ports blindly