This bug was fixed in the package rabbitmq-server -
3.5.7-1ubuntu0.16.04.4
---------------
rabbitmq-server (3.5.7-1ubuntu0.16.04.4) xenial; urgency=medium
* d/rabbitmq-server.service:
- add TimeoutStartSec, Restart, RestartSec parameters (LP: #1874075)
rabbitmq-server (3.5.7-1ubuntu0.16.04.3) xenial; urgency=medium
* Fix timeout discrepancy between SysV and systemd (LP: #1874075)
upstream, rabbitmq-server-release - 694540270c8
* d/rabbitmq-server.init
- Add RABBITMQ_STARTUP_TIMEOUT and default to 600
* d/rabbitmq-env.conf
- Default TimeoutStartSec to 600
* d/rabbitmq-server-wait
- Use value of RABBITMQ_STARTUP_TIMEOUT in wait
-- Matthew Ruffell <[email protected]> Mon, 29 Jun 2020
15:43:21 +1200
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874075
Title:
rabbitmq-server startup timeouts differ between SysV and systemd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
