Shovel connection fails and reports an authentication error

[NishantMunot28]

Describe the bug

shovellog.txt
1] shovel is working local to local on both the rabbitmq new and old.
2] shovel from old rabbit (3.10.5) to new (3.12.13) failed.
3] shovel from new rabbit (3.12.13) to old (3.10.5) failed
4] for testing I have created another rabbit with old version (3.10.5) and shovel is working for old version.

Reproduction steps

1. Create a rabbitmq with version 3.10.5 add queue and vhost.
2. export definition from old rabbit
3. create new rabbitmq with version 3.12.13.
4. import defination.
5. create shovel to migrate message from old rabbitmq queue to new rabbitmq queue

Expected behavior

Shovel should migrate the messages to the new rabbitmq

Additional context

No response

[lukebakken]

https://github.com/rabbitmq/rabbitmq-server/blob/main/COMMUNITY_SUPPORT.md#who-is-eligible-for-community-support

Hello, thanks for using RabbitMQ.

RabbitMQ 3.10 and 3.12 are both out of support.

If you can demonstrate this issue while shoveling messages to RabbitMQ 3.13.6, please include EVERYTHING we need to reproduce the issue, like exported definitions including the shovel itself. We won't guess how to reproduce this issue, even if it seems very simple.

I will re-open this discussion if you are able to reproduce with the latest version of RabbitMQ.

[NishantMunot28]

ok. Thanks for your quick response. one question, can I test shovel migration from 3.10.5 to 3.13.6 or it will still be unsupported version testing?

[johanrhodin]

ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN
Check the username and password.

[lukebakken]

Thanks for looking at the log!

[michaelklishin]

Or whether guest is used to access a remote node, which is prohibited by design by default. Dedicated users with generated credentials should be used instead.

[NishantMunot28]

we have checked the username, password and access of the user on the vhost all seems correct, locally shovel is working with same username and passsword, getting error when using shovel from 3.10.5 to 3.12.13

[michaelklishin]

@NishantMunot28 the error message is very specific: your shovels fail to authenticate or have no permissions to access the target virtual host.

A very common reason for succeeding local and failing remote connections was suggested.

There is a dedicated doc section for troubleshooting authentication.

We will not troubleshoot authentication for you. Please take it from here.

[michaelklishin]

Two other suggestions:

• See logs of the node (or all nodes in a cluster) that accepts shovel connections
• ACCESS_REFUSED may mean missing permissions for accessing a virtual host and not incorrect credentials. See Granting Permissions to a User and rabbitmqctl help set_permissions.

[michaelklishin]

@NishantMunot28 if you file one more duplicate issue you will be permanently banned from this org.

[lukebakken]

@NishantMunot28 please carefully read @michaelklishin's comment - #12108 (comment)

I took about 30 minutes of my time to put together a COMPLETE demonstration of setting up a shovel between a 3.10 and 3.12 node:

https://github.com/lukebakken/rabbitmq-server-12108?tab=readme-ov-file#demonstration

If you have questions about the above project, start a discussion here:

https://github.com/lukebakken/rabbitmq-server-12108/discussions

Do NOT open any more issues concerning this topic in rabbitmq/rabbitmq-server, or you will be re-blocked.