Skip to content
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

Erlang Distribution not working when TLS enabled on rabbitmq:3.12.x #54036

Closed
ElectroBuddha opened this issue Dec 21, 2023 · 3 comments
Closed
Assignees
Labels
rabbitmq solved stale 15 days without activity tech-issues The user has a technical issue about an application

Comments

@ElectroBuddha
Copy link

ElectroBuddha commented Dec 21, 2023

Name and Version

bitnami/rabbitmq:3.12.10

What architecture are you using?

amd64

What steps will reproduce the bug?

Startup an docker container with SSL enabled as described in Readme.

What is the expected behavior?

Instance starting normally and being able to use rabbitmqctl

What do you see instead?

AMQP and Management UI are working on proper SSL listeners ports.

EPMD peer discovery not being able to start, producing the following log (debug) messages:

2023-12-20 17:43:17.442778+00:00 [info] <0.601.0> Ready to start client connection listeners
2023-12-20 17:43:17.447690+00:00 [info] <0.877.0> started TCP listener on [::]:5672
2023-12-20 17:43:17.451591+00:00 [info] <0.897.0> started TLS (SSL) listener on [::]:5671
 completed with 9 plugins.
2023-12-20 17:43:17.563441+00:00 [info] <0.601.0> Server startup complete; 9 plugins started.
2023-12-20 17:43:17.563441+00:00 [info] <0.601.0>  * rabbitmq_prometheus
2023-12-20 17:43:17.563441+00:00 [info] <0.601.0>  * rabbitmq_shovel_management
2023-12-20 17:43:17.563441+00:00 [info] <0.601.0>  * rabbitmq_federation_management
2023-12-20 17:43:17.563441+00:00 [info] <0.601.0>  * rabbitmq_federation
2023-12-20 17:43:17.563441+00:00 [info] <0.601.0>  * rabbitmq_consistent_hash_exchange
2023-12-20 17:43:17.563441+00:00 [info] <0.601.0>  * rabbitmq_shovel
2023-12-20 17:43:17.563441+00:00 [info] <0.601.0>  * rabbitmq_management
2023-12-20 17:43:17.563441+00:00 [info] <0.601.0>  * rabbitmq_management_agent
2023-12-20 17:43:17.563441+00:00 [info] <0.601.0>  * rabbitmq_web_dispatch
2023-12-20 17:43:17.656596+00:00 [info] <0.9.0> Time to start RabbitMQ: 9062006 us
Waiting for erlang distribution on node 'rabbit@rabbitmq-0' while OS process '68' is running
Error: operation wait on node rabbit@rabbitmq-0 timed out. Timeout value used: 5000
Waiting for erlang distribution on node 'rabbit@rabbitmq-0' while OS process '68' is running
Error: operation wait on node rabbit@rabbitmq-0 timed out. Timeout value used: 5000

Additional information

The same setup is working fine when reverted to bitnami/rabbitmq:3.11.x docker images.

@ElectroBuddha ElectroBuddha added the tech-issues The user has a technical issue about an application label Dec 21, 2023
@github-actions github-actions bot added the triage Triage is needed label Dec 21, 2023
@github-actions github-actions bot removed the triage Triage is needed label Dec 22, 2023
@github-actions github-actions bot assigned mdhont and unassigned carrodher Dec 22, 2023
@mdhont
Copy link
Contributor

mdhont commented Dec 27, 2023

Could you describe the exact steps to reproduce the issue?

Copy link

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Jan 12, 2024
Copy link

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rabbitmq solved stale 15 days without activity tech-issues The user has a technical issue about an application
Projects
None yet
Development

No branches or pull requests

4 participants