Need assistance with shovels

[KazzmanK]

Describe the bug

in my rabbitmq windows installation I have a shovel declared by CLI

C:\Program Files\RabbitMQ Server\rabbitmq_server-4.1.1\sbin>rabbitmqctl.bat set_parameter shovel rsd-import "{""src-protocol"": ""amqp091"", ""src-uri"":""amqps://user:password@url:port/vhost"", ""src-queue"": ""src"", ""dest-protocol"": ""amqp091"", ""dest-uri"": ""amqp://user:pass@url/vhost"", ""dest-queue"": ""dest"", ""dest-queue-args"": {""x-queue-type"": ""quorum""}}"
Setting runtime parameter "rsd-import" for component "shovel" to "{"src-protocol": "amqp091", "src-uri":"amqps://......", "src-queue": "...", "dest-protocol": "amqp091", "dest-uri": "amqp://....", "dest-queue": "....", "dest-queue-args": {"x-queue-type": "quorum"}}" in vhost "/" ...

C:\Program Files\RabbitMQ Server\rabbitmq_server-4.1.1\sbin>

No OK or something message printed

It is shown in management ui as (i`ve tried shovel different names)

But in management ui status page is empty

and CLI command also fails

C:\Program Files\RabbitMQ Server\rabbitmq_server-4.1.1\sbin>rabbitmqctl shovel_status --formatter=pretty_table
Shovel status on node rabbit@NET

C:\Program Files\RabbitMQ Server\rabbitmq_server-4.1.1\sbin>rabbitmqctl eval "rabbit_shovel_status:status()."
[]

C:\Program Files\RabbitMQ Server\rabbitmq_server-4.1.1\sbin>rabbitmqctl restart_shovel rsd-import
Restarting dynamic Shovel rsd-import in virtual host / on node rabbit@NET
Error:
Shovel with the given name was not found on the target node 'rabbit@NET' and / or virtual host '/'

C:\Program Files\RabbitMQ Server\rabbitmq_server-4.1.1\sbin>

Shovel plugin is enabled and rinning

C:\Program Files\RabbitMQ Server\rabbitmq_server-4.1.1\sbin>rabbitmq-plugins list
Listing plugins with pattern ".*" ...
 Configured: E = explicitly enabled; e = implicitly enabled
 | Status: * = running on rabbit@NET
 |/
[  ] rabbitmq_amqp1_0                        4.1.1
[  ] rabbitmq_auth_backend_cache             4.1.1
[  ] rabbitmq_auth_backend_http              4.1.1
[  ] rabbitmq_auth_backend_internal_loopback 4.1.1
[  ] rabbitmq_auth_backend_ldap              4.1.1
[  ] rabbitmq_auth_backend_oauth2            4.1.1
[  ] rabbitmq_auth_mechanism_ssl             4.1.1
[  ] rabbitmq_consistent_hash_exchange       4.1.1
[  ] rabbitmq_event_exchange                 4.1.1
[  ] rabbitmq_federation                     4.1.1
[  ] rabbitmq_federation_management          4.1.1
[  ] rabbitmq_federation_prometheus          4.1.1
[  ] rabbitmq_jms_topic_exchange             4.1.1
[E*] rabbitmq_management                     4.1.1
[e*] rabbitmq_management_agent               4.1.1
[  ] rabbitmq_mqtt                           4.1.1
[  ] rabbitmq_peer_discovery_aws             4.1.1
[  ] rabbitmq_peer_discovery_common          4.1.1
[  ] rabbitmq_peer_discovery_consul          4.1.1
[  ] rabbitmq_peer_discovery_etcd            4.1.1
[  ] rabbitmq_peer_discovery_k8s             4.1.1
[  ] rabbitmq_prometheus                     4.1.1
[  ] rabbitmq_random_exchange                4.1.1
[  ] rabbitmq_recent_history_exchange        4.1.1
[  ] rabbitmq_sharding                       4.1.1
[E*] rabbitmq_shovel                         4.1.1
[E*] rabbitmq_shovel_management              4.1.1
[  ] rabbitmq_shovel_prometheus              4.1.1
[  ] rabbitmq_stomp                          4.1.1
[  ] rabbitmq_stream                         4.1.1
[  ] rabbitmq_stream_management              4.1.1
[  ] rabbitmq_top                            4.1.1
[  ] rabbitmq_tracing                        4.1.1
[  ] rabbitmq_trust_store                    4.1.1
[e*] rabbitmq_web_dispatch                   4.1.1
[  ] rabbitmq_web_mqtt                       4.1.1
[  ] rabbitmq_web_mqtt_examples              4.1.1
[  ] rabbitmq_web_stomp                      4.1.1
[  ] rabbitmq_web_stomp_examples             4.1.1

Any help is welcome

Reproduction steps

1. Enable shovel and management plugin
2. restart
3. declare shovel
4. no shovel activity , no statuses

Expected behavior

messages are transferred from source to destination, shovel status is correctly displayed

Additional context

windows environment

[michaelklishin]

@KazzmanK we cannot suggest anything without shovel status output from CLI tools and the logs.

Most likely your shovel fails to connect so it never reaches the state where it starts emitting stats displayed by the management UI. In this case there will be visible errors logged by the node hosting the shovels.