-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error connecting to AMQP broker: Error: connect ECONNREFUSED 172.20.0.3:5672 #154
Comments
Hello, I find it odd that there is no log message related to the rabbitmq container. Can you please comment out everything in the docker-compose.yml file, except the rabbitmq service? I wonder why it didn't start. |
This is frustrating :). I removed all services except rabbitMQ from the compose file, as you suggested. I've now tried many times to bring that container up. I've used the --remove-orphans flag and the --compatibility flag in various combinations. The orphans were removed ( i.e. the old containers containing the images removed from the compose file ). But of the many times I have run this command now, it has worked once. The terminal log is attached. I notice that it appears to start an MQTT broker on the standard MQTT port. The host normally runs mosquitto on this port ( 1883 ). But killing mosquitto on the host does not appear to resolve the problem. There appear to be no significantly helpful messages in the host system log ( attached, editted for relevance ) : |
Frustrating indeed... |
And, by the way, I had never seen it not starting at all. |
Hi there, I get the error given in the title when I attempt to follow the instructions for pulling and running the container(s) using docker compose. I get the error whether or not I issue the compose up command as sudo or not.
I'm using Fedora 37.
containerfail.txt
The text was updated successfully, but these errors were encountered: