From 6d2e5443bb5c42117d9f35b0d7d85d6d197ebdec Mon Sep 17 00:00:00 2001 From: Gauvain Pocentek Date: Sun, 26 Mar 2017 20:54:24 +0200 Subject: [PATCH] [ops-guide] Fix a broken :file: Actually replace it with simple ``...```, along its siblings found in the same file. Change-Id: Ie9ff3deb9bf653284688252422b08aaab98255d7 --- doc/ops-guide/source/ops-maintenance-rabbitmq.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/ops-guide/source/ops-maintenance-rabbitmq.rst b/doc/ops-guide/source/ops-maintenance-rabbitmq.rst index d8c3e7857e..f82db214ee 100644 --- a/doc/ops-guide/source/ops-maintenance-rabbitmq.rst +++ b/doc/ops-guide/source/ops-maintenance-rabbitmq.rst @@ -75,7 +75,7 @@ and resolve the issue: #. Attempt to boot a nova instance in the affected environment. #. If you cannot launch an instance, continue to troubleshoot the issue. #. Log in to each of the controller nodes for the affected environment, and - check the :file:`/var/log/rabbitmq` log files for any reported issues. + check the ``/var/log/rabbitmq`` log files for any reported issues. #. Look for connection issues identified in the log files. #. For each controller node in your environment, view the ``/etc/init.d`` directory to check it contains nova*, cinder*, neutron*, or @@ -89,7 +89,7 @@ and resolve the issue: OpenStack services. #. Open OpenStack Dashboard and launch an instance. If the instance launches, the issue is resolved. -#. If you cannot launch an instance, check the :file:`/var/log/rabbitmq` log +#. If you cannot launch an instance, check the ``/var/log/rabbitmq`` log files for reported connection issues. #. Restart the RabbitMQ service on all of the controller nodes: @@ -122,7 +122,7 @@ To address this issue: # rabbitmqctl status -#. Edit the file:`/etc/rabbitmq/rabbitmq.config` configuration file, and change +#. Edit the ``/etc/rabbitmq/rabbitmq.config`` configuration file, and change the ``collect_statistics_interval`` parameter between 30000-60000 milliseconds. Alternatively you can turn off statistics collection by setting ``collect_statistics`` parameter to "none". @@ -145,4 +145,4 @@ limits: {sockets_used,133}]}," Adjust the appropriate limits in the -:file:`/etc/security/limits.conf` configuration file. +``/etc/security/limits.conf`` configuration file.