An issue seen when working with a customer is that rabbitMQ was "exiting" upon startup.
service rabbitmq-server stop -- stop the service
service rabbitmq-server start -- start the service
service rabbitmq-server status -- verify rabbitmq is working properly
Error code seen critical information found in BOLD
expedition@Expedition:~$ service rabbitmq-server status
● rabbitmq-server.service - RabbitMQ broker
Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2020-04-14 14:07:19 CDT; 380ms ago
Process: 85685 ExecStop=/bin/sh -c while ps -p $MAINPID >/dev/null 2>&1; do sleep 1; done (code=exited, status=0/SUCCESS)
Process: 85538 ExecStop=/usr/lib/rabbitmq/bin/rabbitmqctl stop (code=exited, status=0/SUCCESS)
Process: 85164 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited, status=1/FAILURE)
Main PID: 85164 (code=exited, status=1/FAILURE)
Apr 14 14:07:19 Expedition systemd: Failed to start RabbitMQ broker.
Apr 14 14:07:19 Expedition systemd: rabbitmq-server.service: Unit entered failed state.
Apr 14 14:07:19 Expedition systemd: rabbitmq-server.service: Failed with result 'exit-code'.
We attempted to restart the server and service multiple times however the service was never able to properly run, so a netstat was run to verify that there is not another service running on the rabbitmq service port and preventing it from running. (Default rabbitmq port = 5672) generally found within the rabbitmq.conf file.
sudo service mysql stop
sudo service rabbitmq-server stop
A separate folder was created and we moved the files from ( var/lib/rabbitmq/ ) into that temporary folder after the service was stopped.
sudo service mysql start
sudo service rabbitmq-server start
We first ran a restart of rabbitmq after moving the files into the temporary folder and verified it worked properly. After this verification we moved it back into the correct path and this resolved the issue.
service rabbitmq-server status -- to verify the service is properly running.
I believe this should resolve issues seen with rabbitmq, which affects the panordersreaders (Jobs and Task Manager) on the expedition dashboard.
Special thanks to @alestevez for his assistance in finding a resolution to this issue!
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!