rabbitmq_tracing not working for custom vhost

[Herr-Herner]

I am using Ubuntu 14.04 and have updated RabbitMQ to version 3.6.0. The plugins "rabbitmq_management" and "rabbitmq_tracing" are enabled. Unfortunately, tracing on any vhost fails with:

Enabling tracing for vhost 'test'

=ERROR REPORT==== 4-Jan-2016::14:12:18 ===
webmachine error: path="/api/traces/test/dump.txt"
"Bad Request"

Tracing is running on the vhost '/'. Everything was working fine on RabbitMQ 3.5.7.

Can someone please check if there is a problem with vhost-tracing and version 3.6.0.

[Gabriele Santomaggio]

Hi,
Please check the permission on your virtualhost, this error can happens if you don't have the right permission.

here is and example:

=INFO REPORT==== 4-Jan-2016::15:49:38 ===
Adding vhost 'myvhost'

=INFO REPORT==== 4-Jan-2016::15:49:57 ===
Enabling tracing for vhost 'myvhost'

=ERROR REPORT==== 4-Jan-2016::15:49:57 ===
webmachine error: path="/api/traces/myvhost/myvhostlog"
"Bad Request"

=INFO REPORT==== 4-Jan-2016::15:50:04 ===
Setting permissions for 'guest' in 'myvhost' to '.*', '.*', '.*'

=INFO REPORT==== 4-Jan-2016::15:50:08 ===
Disabling tracing for vhost 'myvhost'

=INFO REPORT==== 4-Jan-2016::15:50:18 ===
Enabling tracing for vhost 'myvhost'

=INFO REPORT==== 4-Jan-2016::15:50:18 ===
Tracer opened log file "/var/tmp/rabbitmq-tracing/myvhostlog.log"

-
Gabriele

[Michael Klishin]

On 4 January 2016 at 17:52:12, Gabriele Santomaggio (g.sant...@gmail.com) wrote:
> Please check the permission on your virtualhost, this error
> can happens if you don't have the right permission.

Also: in 3.6.0, tracing has configurable vhost and username/password. Default values
are still the same as before ("/" and "guest"/"guest"). Could this have an effect in your
case? 
--
MK

Staff Software Engineer, Pivotal/RabbitMQ

[Herr-Herner]

Tracing is working now without any issue. The user 'guest' was missing the required permissions on the custom vhost.

Strange, why this behaviour firstly appears in 3.6.0 and not in <= 3.5.7.

Thank you very much for your support!

Regards,
Christoph

[Michael Klishin]

On 5 January 2016 at 08:27:03, Herr-Herner (christo...@gmail.com) wrote:
> Strange, why this behaviour firstly appears in 3.6.0 and not
> in <= 3.5.7.

Because someone reported this as a missing feature not too long before 3.6.0.