Log analysis and troubleshooting in RabbitMQ - Mini Project: Build & Apply

Log Analysis and Troubleshooting with RabbitMQ

📖 Scenario: You are a system administrator managing a RabbitMQ server. You want to analyze the RabbitMQ logs to find error messages and troubleshoot issues quickly.

🎯 Goal: Build a simple script that reads RabbitMQ log entries, filters error messages, and displays them for troubleshooting.

📋 What You'll Learn

Create a list of sample RabbitMQ log entries

Add a filter keyword variable to identify error logs

Use a loop to filter logs containing the error keyword

Print the filtered error log entries

💡 Why This Matters

🌍 Real World

System administrators often need to analyze RabbitMQ logs to quickly find errors and fix issues in message queues.

💼 Career

This skill helps in troubleshooting and maintaining reliable message broker services in production environments.

1

Create sample RabbitMQ log entries

Create a list called rabbitmq_logs with these exact entries:
"2024-06-01 10:00:00 INFO Starting RabbitMQ server",
"2024-06-01 10:05:00 ERROR Connection refused",
"2024-06-01 10:10:00 WARNING Disk space low",
"2024-06-01 10:15:00 ERROR Queue not found",
"2024-06-01 10:20:00 INFO Server running"

RabbitMQ

# Create a list called rabbitmq_logs with the specified log entries
# Your code here

Hint

Use a Python list with the exact log strings inside double quotes.

2

Add error filter keyword

Create a variable called error_keyword and set it to the string "ERROR" to identify error log entries.

RabbitMQ

rabbitmq_logs = [
    "2024-06-01 10:00:00 INFO Starting RabbitMQ server",
    "2024-06-01 10:05:00 ERROR Connection refused",
    "2024-06-01 10:10:00 WARNING Disk space low",
    "2024-06-01 10:15:00 ERROR Queue not found",
    "2024-06-01 10:20:00 INFO Server running"
]
# Create a variable error_keyword with value "ERROR"
# Your code here

Hint

Use a simple string variable to hold the keyword.

3

Filter error log entries

Create a list called error_logs that contains only the entries from rabbitmq_logs which include the error_keyword. Use a for loop with variable log and an if statement.

RabbitMQ

rabbitmq_logs = [
    "2024-06-01 10:00:00 INFO Starting RabbitMQ server",
    "2024-06-01 10:05:00 ERROR Connection refused",
    "2024-06-01 10:10:00 WARNING Disk space low",
    "2024-06-01 10:15:00 ERROR Queue not found",
    "2024-06-01 10:20:00 INFO Server running"
]
error_keyword = "ERROR"
# Create a list error_logs with logs containing error_keyword
# Your code here

Hint

Use a loop to check each log and add matching ones to error_logs.

4

Display filtered error logs

Use a for loop with variable error_log to print each entry in the error_logs list.

RabbitMQ

rabbitmq_logs = [
    "2024-06-01 10:00:00 INFO Starting RabbitMQ server",
    "2024-06-01 10:05:00 ERROR Connection refused",
    "2024-06-01 10:10:00 WARNING Disk space low",
    "2024-06-01 10:15:00 ERROR Queue not found",
    "2024-06-01 10:20:00 INFO Server running"
]
error_keyword = "ERROR"
error_logs = []
for log in rabbitmq_logs:
    if error_keyword in log:
        error_logs.append(log)
# Print each error log entry
# Your code here

Hint

Use a loop to print each error log on its own line.

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