RabbitMQ stuck in 'Management only mode' after redeploy on Railway
guilhermebsantiago
PROOP

a month ago

Hi everyone

I’m running RabbitMQ on Railway (with rabbitmq:management docker image) and after a simple redeploy the Management UI started showing:

“Overview: Management only mode”

Since then, all queue/exchange metrics and graphs disappeared, even though the broker is working normally (connections, queues and consumers are active).

What I’ve already tried

  • Switching to rabbitmq:4.2-management (in docker docs the collector is enabled in this image)

  • Redeploying

  • Deleting and recreating queues

  • Enabling all stable feature flags

  • Confirmed rabbitmq_management plugin is enabled

Key log line

This line always appears right after startup:

Metrics collection disabled in management agent, management only interface started

Question

Is Railway injecting or mounting any RabbitMQ config by default that sets:

  • management_agent.disable_metrics_collector = true

  • or management.disable_stats = true ?

If so:

  • Where can I see or override this configuration?

  • Is there an officially supported way on Railway to re-enable full RabbitMQ metrics without SSH access?

Any guidance would be appreciated — especially if someone has RabbitMQ running with full Management metrics on Railway.

Thanks!

Solved$20 Bounty

Pinned Solution

guilhermebsantiago
PROOP

a month ago

Solução

Entrando via railway ssh, removendo o arquivo e reiniciando o RabbitMQ, as métricas voltam imediatamente:

railway ssh
rm -f /etc/rabbitmq/conf.d/20-management_agent.disable_metrics_collector.conf
# ou remover qualquer *disable_metrics_collector*.conf
exit
# restart/redeploy service

Depois disso o RabbitMQ inicia normal e a UI volta a exibir métricas.
Obs: com 4.2.x também aparece um warning de deprecated feature:

deprecated_features.permit.management_metrics_collection = false

Mas isso é só aviso — o collector volta a funcionar.

Solution
Using railway ssh, deleting the file and restarting RabbitMQ immediately restores full metrics:

railway ssh
rm -f /etc/rabbitmq/conf.d/20-management_agent.disable_metrics_collector.conf
# or remove any *disable_metrics_collector*.conf
exit
# restart/redeploy service

After that, management UI shows full metrics again.
On 4.2.x there’s also a warning about a deprecated feature flag, but it’s just a warning.

1 Replies

guilhermebsantiago
PROOP

a month ago

Solução

Entrando via railway ssh, removendo o arquivo e reiniciando o RabbitMQ, as métricas voltam imediatamente:

railway ssh
rm -f /etc/rabbitmq/conf.d/20-management_agent.disable_metrics_collector.conf
# ou remover qualquer *disable_metrics_collector*.conf
exit
# restart/redeploy service

Depois disso o RabbitMQ inicia normal e a UI volta a exibir métricas.
Obs: com 4.2.x também aparece um warning de deprecated feature:

deprecated_features.permit.management_metrics_collection = false

Mas isso é só aviso — o collector volta a funcionar.

Solution
Using railway ssh, deleting the file and restarting RabbitMQ immediately restores full metrics:

railway ssh
rm -f /etc/rabbitmq/conf.d/20-management_agent.disable_metrics_collector.conf
# or remove any *disable_metrics_collector*.conf
exit
# restart/redeploy service

After that, management UI shows full metrics again.
On 4.2.x there’s also a warning about a deprecated feature flag, but it’s just a warning.

Status changed to Solved noahd • about 1 month ago

Loading...