[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
Ćukasz Zemczak
1874075 at bugs.launchpad.net
Thu May 14 13:41:32 UTC 2020
Hello Nicolas, or anyone else affected,
Accepted rabbitmq-server into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/rabbitmq-
server/3.5.7-1ubuntu0.16.04.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: rabbitmq-server (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1874075
Title:
rabbitmq-server startup timeouts differ between SysV and systemd
Status in rabbitmq-server package in Ubuntu:
Fix Released
Status in rabbitmq-server source package in Xenial:
Fix Committed
Status in rabbitmq-server source package in Bionic:
Fix Committed
Status in rabbitmq-server source package in Eoan:
Won't Fix
Status in rabbitmq-server source package in Focal:
Fix Committed
Status in rabbitmq-server source package in Groovy:
Fix Released
Status in rabbitmq-server package in Debian:
New
Bug description:
The startup timeouts were recently adjusted and synchronized between
the SysV and systemd startup files.
https://github.com/rabbitmq/rabbitmq-server-release/pull/129
The new startup files should be included in this package.
[Impact]
After starting the RabbitMQ server process, the startup script will
wait for the server to start by calling `rabbitmqctl wait` and will
time out after 10 s.
The startup time of the server depends on how quickly the Mnesia
database becomes available and the server will time out after
`mnesia_table_loading_retry_timeout` ms times
`mnesia_table_loading_retry_limit` retries. By default this wait is
30,000 ms times 10 retries, i.e. 300 s.
The mismatch between these two timeout values might lead to the
startup script failing prematurely while the server is still waiting
for the Mnesia tables.
This change introduces variable `RABBITMQ_STARTUP_TIMEOUT` and the
`--timeout` option into the startup script. The default value for this
timeout is set to 10 minutes (600 seconds).
This change also updates the systemd service file to match the timeout
values between the two service management methods.
[Scope]
Upstream patch: https://github.com/rabbitmq/rabbitmq-server-
release/pull/129
* Fix is not included in the Debian package
* Fix is not included in any Ubuntu series
* Groovy and Focal can apply the upstream patch as is
* Bionic and Xenial need an additional fix in the systemd service file
to set the `RABBITMQ_STARTUP_TIMEOUT` variable for the
`rabbitmq-server-wait` helper script.
[Test Case]
In a clustered setup with two nodes, A and B.
1. create queue on A
2. shut down B
3. shut down A
4. boot B
The broker on B will wait for A. The systemd service will wait for 10
seconds and then fail. Boot A and the rabbitmq-server process on B
will complete startup.
[Regression Potential]
This change alters the behavior of the startup scripts when the Mnesia
database takes long to become available. This might lead to failures
further down the service dependency chain.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list