You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you execute the rabbitmqctl executable (usually in /usr/libexec/rabbitmq), rather than the shell script that is usually installed in /usr/sbin, you can run it as the rabbitmq user and avoid having to run your monitoring scripts as root. Here’s a demonstration:
myserver ~ # cd /var/lib/rabbitmq/
myserver rabbitmq # su rabbitmq -s /bin/sh -c "/usr/libexec/rabbitmq/rabbitmqctl -p myvhost list_queues name"
Listing queues ...
amq.gen-Oiq9xZO6FXr3_0oVpS_LEQ
api
celery
celery@api.myserver.celery.pidbox
celery@recurring.myserver.celery.pidbox
recurring
...done.
The monitoring scripts could run as the rabbitmq user and execute the real rabbitmqctl executable without needing to use su.
The text was updated successfully, but these errors were encountered:
If you execute the
rabbitmqctl
executable (usually in/usr/libexec/rabbitmq
), rather than the shell script that is usually installed in/usr/sbin
, you can run it as therabbitmq
user and avoid having to run your monitoring scripts as root. Here’s a demonstration:The monitoring scripts could run as the
rabbitmq
user and execute the realrabbitmqctl
executable without needing to usesu
.The text was updated successfully, but these errors were encountered: