[designate][rabbitmq] Worker and Central fail to connect to broker even after authentication
11 Jun
2024
11 Jun
'24
11:07 a.m.
Hi, I'm having a strange issue with Designate. Setup: Central, mdns, producer and worker services up&running; WSGI configured; api disabled in favor of WSGI Issue: Central and Worker state that connection to RabbitMQ failed as refused, but there is nothing in Rabbit logs. Same time and setup, Producer logs correctly reports RPC responses. If I restart services, in RabbitMQ logs designate-producer, designate-central designate-worker and mod_wsgi are reported as authenticated as user 'designate' and given access to the same vhost, but then Central and Worker start failing again Has anyone encountered the same issue? Regards Francesco Di Nucci
151
Age (days ago)
151
Last active (days ago)
0 comments
1 participants
participants (1)
-
Francesco Di Nucci