@Th - I think you're probably correct in that this is a load issue,
rather than a specific rabbitmq software issue. It looks like the
system is so loaded you're hitting some sort of 90 second timeout at
which point systemd just gives up:
/etc/systemd/system.conf: DefaultTimeoutStartSec=90s
you
Maybe post the output of these commands when run on a system that was
rebooted and where rabbit failed to start:
sudo systemd-analyze blame
and
sudo systemd-analyze critical-chain
Maybe the resolver or network wasn't ready when rabbit tried to start.
--
You received this bug notification
After the reboot, whether it was one where rabbit failed to start or
not, does a restart of the rabbit service always work?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1783325
Please check that forward/reverse hostname to IP is working OK on the
impacted systems; if it is then set the bug back to New with an
appropriate comment, if not then we can close out this bug report IMHO.
--
You received this bug notification because you are a member of Ubuntu
Server, which is
rabbitmq is also very sensitive to any hostname <-> IP mismatch as it
uses this to communicate with the RMQ daemon.
'rabbit@hostname' looks suspicious here - I'd suggest that maybe
something is a bit wonky.
If a "sudo su -" results a warning about hostnames this is def the
issue.
** Changed in:
