On 05/12/12 11:17, Simon MacMullen wrote: > I've traced this to the rabbitmq_tracing plugin. > > To the OP: thank you for the bug report, this will be fixed in 3.0.1. ...meanwhile, if you disable the tracing plugin then 'rabbitmqctl status' should work fine. Matthias.