[rabbitmq-discuss] /api/aliveness-test broken on 2.6.0?
Bill Gerrard
billg at nffs.com
Tue Sep 6 18:17:11 BST 2011
Our ops team just upgraded rabbitmq to 2.6.0 (on debian) and I installed
the new management plugins. After which, our monitoring using the
aliveness-test api call no longer works. All other api calls still
appear to work though.
$ curl -i -u guest:guest http://message-broker:55672/api/aliveness-test/
HTTP/1.1 404 Object Not Found
Server: MochiWeb/1.1 WebMachine/1.7 (participate in the frantic)
Date: Tue, 06 Sep 2011 16:56:51 GMT
Content-Type: text/html
Content-Length: 193
<HTML><HEAD><TITLE>404 Not Found</TITLE></HEAD><BODY><H1>Not
Found</H1>The requested document was not found on this
server.<P><HR><ADDRESS>mochiweb+webmachine web
server</ADDRESS></BODY></HTML>
(just for info, here is vhosts showing it's working)
$ curl -i -u guest:guest http://message-broker:55672/api/vhosts
HTTP/1.1 200 OK
Server: MochiWeb/1.1 WebMachine/1.7 (participate in the frantic)
Date: Tue, 06 Sep 2011 17:15:33 GMT
Content-Type: application/json
Content-Length: 30
Cache-Control: no-cache
[{"name":"/","tracing":false}]
More information about the rabbitmq-discuss
mailing list