Shulou(Shulou.com)05/31 Report--

Editor to share with you how to use Docker to deploy RabbitMQ without logs, I believe most people do not know much about it, so share this article for your reference, I hope you can learn a lot after reading this article, let's go to know it!

After deploying the RabbitMQ service using Docker, go to the / var/log/rabbitmq directory and see that it is empty and no log files are generated.

Is there no journal? This is not the case. The logs are all typed on standard output. You can view it using the following command:

# docker logs-f container_name

But at ordinary times, it is impossible to look at it this way during operation and maintenance. It is too troublesome.

Here is a question, why type on the standard output instead of exporting to a file?

RabbitMQ has two configurations to define log output:

RABBITMQ_LOG_BASE: log file output path

RABBITMQ_LOGS: specific log file

It's a little different in Docker. If you look at the source code on Github, you can see the following code:

# If $RABBITMQ_LOGS is'-', send all log messages to stdout. This is# particularly useful for Docker images.if ["$RABBITMQ_LOGS" ='-']; then SASL_ERROR_LOGGER=tty RABBIT_LAGER_HANDLER=tty RABBITMQ_LAGER_HANDLER_UPGRADE=ttyelse SASL_ERROR_LOGGER=false RABBIT_LAGER_HANDLER=' "'${RABBITMQ_LOGS}'" 'RABBITMQ_LAGER_HANDLER_UPGRADE=' "' ${RABBITMQ_UPGRADE_LOG}'"'fi "

It means that if RABBITMQ_LOGS is configured as -, the log will be output to standard output.

Print it in my container, and it's true.

# docker exec-it rabbitmq / bin/bashbash-5.0# echo $RABBITMQ_LOGS-bash-5.0#

Once the reason is clear, it's easy to solve, as long as you add two configurations to the docker-compose file.

Version: '2'services: rabbitmq: container_name: rabbitmq image: rabbitmq:3.7-management-alpine restart: always environment:-RABBITMQ_DEFAULT_USER=username-RABBITMQ_DEFAULT_PASS=password-RABBITMQ_LOGS=-RABBITMQ_LOG_BASE=/var/log/rabbitmq volumes:-/ var/log/rabbitmq:/var/log/rabbitmq ports:-"5672 container_name 5672"-"15672 container_name 15672"

The RABBITMQ_LOGS parameter can be left blank, and the log file will be available after restarting the service.

These are all the contents of the article "using Docker to deploy RabbitMQ without logs". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.