RabbitMQ Logs

RabbitMQ logs are critical for diagnosing issues related to job queue processing, agent connectivity, and audit log transmission.

Common log entries and issues include:

• Job Queue Errors: Logs may show errors like "Unable to write job to job queue (Unknown error): rabbitmq" when jobs cannot be added, often after a location has already been scanned. This can result in jobs not being published or processed as expected.
• Acknowledgment Timeouts: Logs may contain repeated errors such as "delivery acknowledgement on channel 1 timed out," leading to jobs being requeued and reprocessed multiple times. This causes redundant work and agent failures, with cycles of reconnection and timeout every 30 minutes.
• Permission and Connection Errors: Logs can show permission errors for vhosts or connection failures, e.g., "RabbitMQ.Client.Exceptions.BrokerUnreachableException: None of the specified endpoints were reachable" or "Connection refused," often due to misconfiguration or network issues.
• Audit Log Transmission: Audit events are queued in RabbitMQ and then consumed and persisted to the database. Logs can be monitored to confirm that audit messages are processed through the AuditingQueue.
• Telemetry and Central Logging: RabbitMQ metrics and telemetry can be transmitted to a central logging tool for analysis of unexpected behavior.

Log file locations may vary depending on installation method and user context:

• Default directory - C:\Users\<user>\AppData\Roaming\RabbitMQ\log\
• Misplaced log/db files can cause scan failures after upgrades or automated installations.

Monitoring RabbitMQ logs is essential for troubleshooting issues such as job queue failures, agent reconnections, audit log processing, and connectivity problems.