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.