Log analysis and troubleshooting in RabbitMQ - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to view the last 50 lines of the RabbitMQ log file.

RabbitMQ

tail -n [1] /var/log/rabbitmq/rabbitmq.log

Drag options to blanks, or click blank then click option'

A50

B100

C10

D500

Attempts:

3 left

💡 Hint

Common Mistakes

Using too many lines which makes it hard to find recent errors.

Using too few lines and missing important log entries.

The tail -n 50 command shows the last 50 lines of the log file, which helps to quickly check recent log entries.

2fill in blank

medium

Complete the command to search RabbitMQ logs for the keyword 'error'.

RabbitMQ

grep [1] /var/log/rabbitmq/rabbitmq.log

Drag options to blanks, or click blank then click option'

A'warning'

B'info'

C'error'

D'debug'

Attempts:

3 left

💡 Hint

Common Mistakes

Searching for 'info' or 'debug' which show normal operation messages.

Forgetting to use quotes around the keyword.

The grep 'error' command filters log lines containing the word 'error', helping to find issues quickly.

3fill in blank

hard

Fix the error in the command to continuously monitor RabbitMQ logs.

RabbitMQ

tail -f [1]/rabbitmq.log

Drag options to blanks, or click blank then click option'

A/var/log

B/var/log/rabbitmq

C/etc/rabbitmq

D/usr/local/rabbitmq

Attempts:

3 left

💡 Hint

Common Mistakes

Using the config directory /etc/rabbitmq instead of logs.

Using a wrong or non-existent directory.

The RabbitMQ logs are usually stored in /var/log/rabbitmq. Using this path with tail -f allows live monitoring of the log file.

4fill in blank

hard

Complete the code to create a dictionary comprehension that maps queue names to their message counts from a list of tuples.

RabbitMQ

{queue: count for queue, count in queues if count [1] 0}

Drag options to blanks, or click blank then click option'

A:

B>

C<

D=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '=' instead of ':' in dictionary comprehension.

Using '<' instead of '>' which filters wrong queues.

The colon : separates keys and values in a dictionary comprehension. The condition count > 0 filters queues with messages.

5fill in blank

hard

Fill all three blanks to filter and map log entries with severity 'ERROR' and extract their timestamps.

RabbitMQ

[[1] for line in logs if '[2]' in line and line.startswith('[3]')]

Drag options to blanks, or click blank then click option'

Aline.split()[1]

BERROR

C2024-06-

DINFO

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'INFO' instead of 'ERROR' to filter logs.

Extracting wrong part of the line for timestamp.

This list comprehension extracts the timestamp (second word) from lines containing 'ERROR' and starting with the date prefix '2024-06-'.

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