Undercloud RabbitMQ Container Fails

Solution Verified - Updated -

Issue

  • Unable to start rabbitmq container on the undercloud after a reboot
  • Failure seen in /var/log/messages:
Sep  8 02:30:56 undercloud systemd[1]: tripleo_rabbitmq.service: Main process exited, code=exited, status=1/FAILURE
Sep  8 02:30:56 undercloud systemd[1]: tripleo_rabbitmq.service: Failed with result 'exit-code'.
Sep  8 02:30:56 undercloud systemd[1]: tripleo_rabbitmq.service: Service RestartSec=100ms expired, scheduling restart.
Sep  8 02:30:56 undercloud systemd[1]: tripleo_rabbitmq.service: Scheduled restart job, restart counter is at 8.
Sep  8 02:30:56 undercloud systemd[1]: Stopped rabbitmq container healthcheck.
Sep  8 02:30:56 undercloud systemd[1]: Stopping rabbitmq container healthcheck.
Sep  8 02:30:56 undercloud systemd[1]: tripleo_rabbitmq_healthcheck.timer: Start request repeated too quickly.
Sep  8 02:30:56 undercloud systemd[1]: tripleo_rabbitmq_healthcheck.timer: Failed with result 'start-limit-hit'.
Sep  8 02:30:56 undercloud systemd[1]: Failed to start rabbitmq container healthcheck.
Sep  8 02:30:56 undercloud systemd[1]: Stopped rabbitmq container.
Sep  8 02:30:56 undercloud systemd[1]: tripleo_rabbitmq.service: Start request repeated too quickly.
Sep  8 02:30:56 undercloud systemd[1]: tripleo_rabbitmq.service: Failed with result 'exit-code'.
Sep  8 02:30:56 undercloud systemd[1]: Failed to start rabbitmq container.
  • Rabbitmq was working without this issue before the reboot

Environment

  • Red Hat OpenStack Platform 16.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In