The following 'worked for me' on CentOS verion 8.
$ cat /etc/systemd/system/rabbitmq-server/limits.conf
[Service]
LimitNOFILE=65536
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783325
Title:
Rabb
@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
Reproducing the problem to get the above outputs gave me better
understading on conditions that lead to this problem.
If there is high load on virtualisation hosts when vms containing Rabbit
server get rebooted the timeout is likely to happen. If reboots happen
when virtualisation hosts have low l
Blame output:
2min 42.650s solr.service
1min 30.057s rabbitmq-server.service
1min 25.356s shibd.service
1min 18.921s kong.service
1min 13.311s postgresql@9.5-main.service
47.776s apache2.service
22.732s cloud-init-local.service
22.192s snapd.service
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 bec
Manual restarts have worked without problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783325
Title:
Rabbitmq-server times out during server startup
To manage notifications about this bug go
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783325
Title:
Rabbitmq-serv
The "@hostname" is placeholder for real hostname which I did not want to
publish. Sorry for confusion.
"Sudo su -" and forward/reverse hostname to ip lookups work without
problem or warnings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Provided required information.
** Changed in: rabbitmq-server (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783325
Title:
Rabbitmq-server times out during
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:
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
Bugs, which is sub
I found one common thing for hosts have had this problem: They are all
vms that run on older and slower hardware. Vms on newer hardware with
similar software and configuration have not had this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783325
Title:
Rabbitmq-server times out during server startup
To manage notifications about this bug go to:
https://bugs.launchp
13 matches
Mail list logo
