Performing verification for rabbitmq-server in -proposed for focal. I know the focal package is released to -updates, but I will verify again regardless.
I installed 3.8.2-0ubuntu1.1 from -proposed, and followed the instructions I wrote in comment #59. I sent a message to host 1, checked that host 1 was master, and host 2 was the slave. I shut host 1 down, and then sent a message to host 2. Host 2 became the new master. I shut host 2 down. I then started host 1 up again. When I ran "sudo systemctl status rabbitmq-server.service", rabbit was in the "activating" state, due to having its systemd service as type=notify. I let it sit on "activating" for an entire 10 minutes, at which point it timed out as planned, and the service restarted as expected after 10 seconds. The service came up again in the "activating" state as expected. I then started host 2 up again, and after it had come up, both rabbitmq-server services were in the active state, and servicing requests. The package is behaving as expected on focal, and I am happy to mark this as verified. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
