If RabbitMQ attempts to start but fails, the reason will be shown in its output (e.g. "journalctl -eu rabbitmq" or whatever the service name is).
One guess is that RabbitMQ is trying to bind to the same port as prometheus. Prometheus uses port 9090 by default, and I think RabbitMQ uses port 5672 and 15672 by default, so they ought to be fine. But maybe there's some additional port configured in one or the other. If there's no attempt even to start RabbitMQ while Prometheus is running, then this would be down to your process manager (e.g. systemd); maybe systemd has some weird dependencies configured between those two packages? This would be unusual. Those are a couple of ideas, but basically this is a problem with your system which you'll need to resolve locally. The best practice in any case would be to run Prometheus and RabbitMQ in separate VMs, or at least separate containers. On Tuesday 20 February 2024 at 02:25:33 UTC+7 Mateus Silva wrote: > When starting the system, the Prometheus service appears with metrics and > exporters, but RabbitMQ does not start. When I stop Prometheus, RabbitMQ > starts. Could you tell me what could be causing this problem? I couldn't > find the error. Thank you for your help if possible > -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/2514533a-2f8e-4a32-a329-c189d9960f20n%40googlegroups.com.
