Management plugin is not working properly

[VijayJIndal]

After starting the image, the management console is giving following error:
"undefined: There is no template at js/tmpl/undefined.ejs"

Image used: rabbitmq:3.7.3-management

System details

$ docker -v
Docker version 17.09.0-ce, build afdb6d4

$ uname -a
Linux localhost.localdomain 3.10.0-229.1.2.39163.MSSr4.el7.centos.x86_64 #1 SMP Mon Nov 23 12:23:20 IST 2015 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/centos-release
CentOS Linux release 7.1.1503 (Core)

[yosifkit]

How are you running it? Do you have custom configuration that might be changing things? I am unable to see any breakage here. I even visited the interface at http:///ip:15672.

$ docker pull rabbitmq:3.7.3-management
3.7.3-management: Pulling from library/rabbitmq
Digest: sha256:ce1f6f597861a0e11942ad30415b192379a69b491a5899eead98abcf88430e31
Status: Downloaded newer image for rabbitmq:3.7.3-management
$ docker run -it --rm --name rabbit rabbitmq:3.7.3-management
2018-02-08 17:53:57.160 [info] <0.33.0> Application lager started on node rabbit@0d21625668ba
2018-02-08 17:53:57.662 [info] <0.33.0> Application mnesia started on node rabbit@0d21625668ba
2018-02-08 17:53:57.735 [info] <0.33.0> Application inets started on node rabbit@0d21625668ba
2018-02-08 17:53:57.735 [info] <0.33.0> Application recon started on node rabbit@0d21625668ba
2018-02-08 17:53:57.740 [info] <0.33.0> Application os_mon started on node rabbit@0d21625668ba
2018-02-08 17:53:57.740 [info] <0.33.0> Application crypto started on node rabbit@0d21625668ba
2018-02-08 17:53:57.741 [info] <0.33.0> Application cowlib started on node rabbit@0d21625668ba
2018-02-08 17:53:57.741 [info] <0.33.0> Application jsx started on node rabbit@0d21625668ba
2018-02-08 17:53:57.741 [info] <0.33.0> Application xmerl started on node rabbit@0d21625668ba
2018-02-08 17:53:57.741 [info] <0.33.0> Application asn1 started on node rabbit@0d21625668ba
2018-02-08 17:53:57.741 [info] <0.33.0> Application public_key started on node rabbit@0d21625668ba
2018-02-08 17:53:57.801 [info] <0.33.0> Application ssl started on node rabbit@0d21625668ba
2018-02-08 17:53:57.806 [info] <0.33.0> Application ranch started on node rabbit@0d21625668ba
2018-02-08 17:53:57.806 [info] <0.33.0> Application ranch_proxy_protocol started on node rabbit@0d21625668ba
2018-02-08 17:53:57.808 [info] <0.33.0> Application cowboy started on node rabbit@0d21625668ba
2018-02-08 17:53:57.809 [info] <0.33.0> Application rabbit_common started on node rabbit@0d21625668ba
2018-02-08 17:53:57.819 [info] <0.189.0> 
 Starting RabbitMQ 3.7.3 on Erlang 20.1.7
 Copyright (C) 2007-2018 Pivotal Software, Inc.
 Licensed under the MPL.  See http://www.rabbitmq.com/

  ##  ##
  ##  ##      RabbitMQ 3.7.3. Copyright (C) 2007-2018 Pivotal Software, Inc.
  ##########  Licensed under the MPL.  See http://www.rabbitmq.com/
  ######  ##
  ##########  Logs: <stdout>

              Starting broker...
2018-02-08 17:53:57.836 [info] <0.189.0> 
 node           : rabbit@0d21625668ba
 home dir       : /var/lib/rabbitmq
 config file(s) : /etc/rabbitmq/rabbitmq.conf
 cookie hash    : mRq85tDIuTnqV12SG9pBrA==
 log(s)         : <stdout>
 database dir   : /var/lib/rabbitmq/mnesia/rabbit@0d21625668ba
2018-02-08 17:54:00.187 [info] <0.197.0> Memory high watermark set to 9645 MiB (10113838284 bytes) of 24113 MiB (25284595712 bytes) total
2018-02-08 17:54:00.196 [info] <0.199.0> Enabling free disk space monitoring
2018-02-08 17:54:00.196 [info] <0.199.0> Disk free limit set to 50MB
2018-02-08 17:54:00.202 [info] <0.201.0> Limiting to approx 1048476 file handles (943626 sockets)
2018-02-08 17:54:00.202 [info] <0.202.0> FHC read buffering:  OFF
2018-02-08 17:54:00.202 [info] <0.202.0> FHC write buffering: ON
2018-02-08 17:54:00.204 [info] <0.189.0> Node database directory at /var/lib/rabbitmq/mnesia/rabbit@0d21625668ba is empty. Assuming we need to join an existing cluster or initialise from scratch...
2018-02-08 17:54:00.204 [info] <0.189.0> Configured peer discovery backend: rabbit_peer_discovery_classic_config
2018-02-08 17:54:00.205 [info] <0.189.0> Will try to lock with peer discovery backend rabbit_peer_discovery_classic_config
2018-02-08 17:54:00.205 [info] <0.189.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping randomized startup delay.
2018-02-08 17:54:00.205 [info] <0.189.0> All discovered existing cluster peers: 
2018-02-08 17:54:00.205 [info] <0.189.0> Discovered no peer nodes to cluster with
2018-02-08 17:54:00.210 [info] <0.33.0> Application mnesia exited with reason: stopped
2018-02-08 17:54:00.330 [info] <0.33.0> Application mnesia started on node rabbit@0d21625668ba
2018-02-08 17:54:01.429 [info] <0.189.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2018-02-08 17:54:01.511 [info] <0.189.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2018-02-08 17:54:01.620 [info] <0.189.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2018-02-08 17:54:01.620 [info] <0.189.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping registration.
2018-02-08 17:54:01.621 [info] <0.189.0> Priority queues enabled, real BQ is rabbit_variable_queue
2018-02-08 17:54:01.679 [info] <0.374.0> Starting rabbit_node_monitor
2018-02-08 17:54:01.715 [info] <0.189.0> message_store upgrades: 1 to apply
2018-02-08 17:54:01.715 [info] <0.189.0> message_store upgrades: Applying rabbit_variable_queue:move_messages_to_vhost_store
2018-02-08 17:54:01.715 [info] <0.189.0> message_store upgrades: No durable queues found. Skipping message store migration
2018-02-08 17:54:01.715 [info] <0.189.0> message_store upgrades: Removing the old message store data
2018-02-08 17:54:01.717 [info] <0.189.0> message_store upgrades: All upgrades applied successfully
2018-02-08 17:54:01.772 [info] <0.189.0> Management plugin: using rates mode 'basic'
2018-02-08 17:54:01.773 [info] <0.189.0> Adding vhost '/'
2018-02-08 17:54:02.039 [info] <0.408.0> Making sure data directory '/var/lib/rabbitmq/mnesia/rabbit@0d21625668ba/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L' for vhost '/' exists
2018-02-08 17:54:02.082 [info] <0.408.0> Starting message stores for vhost '/'
2018-02-08 17:54:02.082 [info] <0.412.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_transient": using rabbit_msg_store_ets_index to provide index
2018-02-08 17:54:02.086 [info] <0.408.0> Started message store of type transient for vhost '/'
2018-02-08 17:54:02.087 [info] <0.415.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent": using rabbit_msg_store_ets_index to provide index
2018-02-08 17:54:02.089 [warning] <0.415.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent": rebuilding indices from scratch
2018-02-08 17:54:02.092 [info] <0.408.0> Started message store of type persistent for vhost '/'
2018-02-08 17:54:02.095 [info] <0.189.0> Creating user 'guest'
2018-02-08 17:54:02.132 [info] <0.189.0> Setting user tags for user 'guest' to [administrator]
2018-02-08 17:54:02.178 [info] <0.189.0> Setting permissions for 'guest' in '/' to '.*', '.*', '.*'
2018-02-08 17:54:02.217 [info] <0.453.0> started TCP Listener on [::]:5672
2018-02-08 17:54:02.275 [info] <0.189.0> Setting up a table for connection tracking on this node: tracked_connection_on_node_rabbit@0d21625668ba
2018-02-08 17:54:02.343 [info] <0.189.0> Setting up a table for per-vhost connection counting on this node: tracked_connection_per_vhost_on_node_rabbit@0d21625668ba
2018-02-08 17:54:02.344 [info] <0.33.0> Application rabbit started on node rabbit@0d21625668ba
2018-02-08 17:54:02.344 [info] <0.33.0> Application amqp_client started on node rabbit@0d21625668ba
2018-02-08 17:54:02.345 [info] <0.33.0> Application rabbitmq_web_dispatch started on node rabbit@0d21625668ba
2018-02-08 17:54:02.352 [info] <0.33.0> Application rabbitmq_management_agent started on node rabbit@0d21625668ba
2018-02-08 17:54:02.381 [info] <0.514.0> Management plugin started. Port: 15672
2018-02-08 17:54:02.381 [info] <0.620.0> Statistics database started.
2018-02-08 17:54:02.384 [info] <0.33.0> Application rabbitmq_management started on node rabbit@0d21625668ba
 completed with 3 plugins.
2018-02-08 17:54:02.584 [info] <0.5.0> Server startup complete; 3 plugins started.
 * rabbitmq_management
 * rabbitmq_management_agent
 * rabbitmq_web_dispatch

[VijayJIndal]

yosifkit, thanks for replying. I tried to start the container with same command which you are using and still getting the same issue. Foliowing are the runs logs:

$ docker run -it -p 15672:15672 --rm --name rabbit rabbitmq:3.7.3-management
_2018-02-09 06:04:45.222 [info] <0.33.0> Application lager started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:45.438 [info] <0.33.0> Application mnesia started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:45.471 [info] <0.33.0> Application inets started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:45.471 [info] <0.33.0> Application recon started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:45.473 [info] <0.33.0> Application os_mon started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:45.474 [info] <0.33.0> Application crypto started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:45.474 [info] <0.33.0> Application cowlib started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:45.474 [info] <0.33.0> Application jsx started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:45.474 [info] <0.33.0> Application xmerl started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:45.474 [info] <0.33.0> Application asn1 started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:45.474 [info] <0.33.0> Application public_key started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:45.502 [info] <0.33.0> Application ssl started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:45.505 [info] <0.33.0> Application ranch started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:45.505 [info] <0.33.0> Application ranch_proxy_protocol started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:45.506 [info] <0.33.0> Application cowboy started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:45.506 [info] <0.33.0> Application rabbit_common started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:45.512 [info] <0.189.0>
 Starting RabbitMQ 3.7.3 on Erlang 20.1.7
 Copyright (C) 2007-2018 Pivotal Software, Inc.
 Licensed under the MPL.  See http://www.rabbitmq.com/

 ##  ##
  ##  ##      RabbitMQ 3.7.3. Copyright (C) 2007-2018 Pivotal Software, Inc.
  ##########  Licensed under the MPL.  See http://www.rabbitmq.com/
  ######  ##
  ##########  Logs: <stdout

              Starting broker...
2018-02-09 06:04:45.521 [info] <0.189.0>
 node           : rabbit@f7b0b78d38fe
 home dir       : /var/lib/rabbitmq
 config file(s) : /etc/rabbitmq/rabbitmq.conf
 cookie hash    : fVnjvAzK/to6w8WiStb+DQ==
 log(s)         : <stdout>
 database dir   : /var/lib/rabbitmq/mnesia/rabbit@f7b0b78d38fe
2018-02-09 06:04:46.654 [info] <0.197.0> Memory high watermark set to 3090 MiB (3240894464 bytes) of 7726 MiB (8102236160 bytes) total
2018-02-09 06:04:46.656 [info] <0.199.0> Enabling free disk space monitoring
2018-02-09 06:04:46.656 [info] <0.199.0> Disk free limit set to 50MB
2018-02-09 06:04:46.658 [info] <0.201.0> Limiting to approx 65436 file handles (58890 sockets)
2018-02-09 06:04:46.658 [info] <0.202.0> FHC read buffering:  OFF
2018-02-09 06:04:46.658 [info] <0.202.0> FHC write buffering: ON
2018-02-09 06:04:46.659 [info] <0.189.0> Node database directory at /var/lib/rabbitmq/mnesia/rabbit@f7b0b78d38fe is empty. Assuming we need to join an existing cluster or initialise from scratch...
2018-02-09 06:04:46.659 [info] <0.189.0> Configured peer discovery backend: rabbit_peer_discovery_classic_config
2018-02-09 06:04:46.659 [info] <0.189.0> Will try to lock with peer discovery backend rabbit_peer_discovery_classic_config
2018-02-09 06:04:46.659 [info] <0.189.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping randomized startup delay.
2018-02-09 06:04:46.659 [info] <0.189.0> All discovered existing cluster peers:
2018-02-09 06:04:46.659 [info] <0.189.0> Discovered no peer nodes to cluster with
2018-02-09 06:04:46.661 [info] <0.33.0> Application mnesia exited with reason: stopped
2018-02-09 06:04:46.684 [info] <0.33.0> Application mnesia started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:46.779 [info] <0.189.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2018-02-09 06:04:46.803 [info] <0.189.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2018-02-09 06:04:46.829 [info] <0.189.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2018-02-09 06:04:46.829 [info] <0.189.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping registration.
2018-02-09 06:04:46.830 [info] <0.189.0> Priority queues enabled, real BQ is rabbit_variable_queue
2018-02-09 06:04:46.834 [info] <0.376.0> Starting rabbit_node_monitor
2018-02-09 06:04:46.853 [info] <0.189.0> message_store upgrades: 1 to apply
2018-02-09 06:04:46.853 [info] <0.189.0> message_store upgrades: Applying rabbit_variable_queue:move_messages_to_vhost_store
2018-02-09 06:04:46.853 [info] <0.189.0> message_store upgrades: No durable queues found. Skipping message store migration
2018-02-09 06:04:46.853 [info] <0.189.0> message_store upgrades: Removing the old message store data
2018-02-09 06:04:46.853 [info] <0.189.0> message_store upgrades: All upgrades applied successfully
2018-02-09 06:04:46.874 [info] <0.189.0> Management plugin: using rates mode 'basic'
2018-02-09 06:04:46.875 [info] <0.189.0> Adding vhost '/'
2018-02-09 06:04:46.907 [info] <0.410.0> Making sure data directory '/var/lib/rabbitmq/mnesia/rabbit@f7b0b78d38fe/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L' for vhost '/' exists
2018-02-09 06:04:46.911 [info] <0.410.0> Starting message stores for vhost '/'
2018-02-09 06:04:46.911 [info] <0.414.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_transient": using rabbit_msg_store_ets_index to provide index
2018-02-09 06:04:46.912 [info] <0.410.0> Started message store of type transient for vhost '/'
2018-02-09 06:04:46.912 [info] <0.417.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent": using rabbit_msg_store_ets_index to provide index
2018-02-09 06:04:46.912 [warning] <0.417.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent": rebuilding indices from scratch
2018-02-09 06:04:46.913 [info] <0.410.0> Started message store of type persistent for vhost '/'
2018-02-09 06:04:46.913 [info] <0.189.0> Creating user 'guest'
2018-02-09 06:04:46.917 [info] <0.189.0> Setting user tags for user 'guest' to [administrator]
2018-02-09 06:04:46.923 [info] <0.189.0> Setting permissions for 'guest' in '/' to '.*', '.*', '.*'
2018-02-09 06:04:46.930 [info] <0.455.0> started TCP Listener on [::]:5672
2018-02-09 06:04:46.936 [info] <0.189.0> Setting up a table for connection tracking on this node: tracked_connection_on_node_rabbit@f7b0b78d38fe
2018-02-09 06:04:46.941 [info] <0.189.0> Setting up a table for per-vhost connection counting on this node: tracked_connection_per_vhost_on_node_rabbit@f7b0b78d38fe
2018-02-09 06:04:46.941 [info] <0.33.0> Application rabbit started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:46.941 [info] <0.33.0> Application amqp_client started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:46.941 [info] <0.33.0> Application rabbitmq_web_dispatch started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:46.943 [info] <0.33.0> Application rabbitmq_management_agent started on node rabbit@f7b0b78d38fe
2018-02-09 06:04:46.962 [info] <0.516.0> Management plugin started. Port: 15672
2018-02-09 06:04:46.962 [info] <0.622.0> Statistics database started.
2018-02-09 06:04:46.962 [info] <0.33.0> Application rabbitmq_management started on node rabbit@f7b0b78d38fe
 completed with 3 plugins.
2018-02-09 06:04:47.069 [info] <0.5.0> Server startup complete; 3 plugins started.
 * rabbitmq_management
 * rabbitmq_management_agent
 * rabbitmq_web_dispatch_

[yosifkit]

It could be image corruption; have you tried deleting and pulling the image again?

[VijayJIndal]

yosifkit, I tried it but facing the same issue. I also tried it on a different machine and the same issue persists.
I am expecting there may be an issue with docker installation. I have followed commands for installation:

$ sudo curl -SsL https://download.docker.com/linux/centos/docker-ce.repo -o /etc/yum.repos.d/docker-ce.repo
$ sudo yum install docker-ce-17.06.0.ce-1.el7.centos

Let me know if this is the right way to install docker engine. I cannot use the standard way of docker installation, as:
$ wget -qO- https://get.docker.com/ | sh

because above command always install the latest version which is not supported by my centos-version.

[michaelklishin]

Try invoking HTTP API with curl to see if the plugin is functional (excluding the UI code).

Try clearing your browser's cache (as the upgrade docs now recommend).

[tianon]

Sorry, but since we cannot reproduce the issue, I'm going to close. Hopefully the suggested solutions help!

In the future, these sorts of questions/requests would be more appropriately posted to the Docker Community Forums, the Docker Community Slack, or Stack Overflow. Thanks!