> In the context of the issues we are seeing with charms the 10 minute
> timeout should be sufficient.

right, but this isn't just changing rabbitmq-server used by charms, this
is changing the behavior for *all* Ubuntu users of rabbitmq-server, as
well as upstream. Since upstream did accept it, my *assumption* is yes,
10 minutes is a good default, but since mismatched timeouts is
essentially the cause of this entire problem, I thought it was worth
just re-checking again, to make sure we all thought about it carefully
with *all users* in mind, before leaving it at that.

To poke the thought button further, note that since the upstream (and
f/g) service files also have 'Restart=on-failure' set, and will go 10
minutes (as configured with the TimeoutStartSec=600 param), the service
is *effectively* set to never, ever timeout, since it will just restart
itself each time it times out; as the StartLimitIntervalSec= and
StartLimitBurst= will never be exceeded (since they default to 10s and
5, respectively).

So, I suppose since the effective result is that in F and later
(including upstream), the service will wait forever, with restart-on-
failure happening every 10 minutes, until it successfully is able to
start.  With that in mind, I don't think the actual TimeoutStartSec=
setting makes any difference at all (as long as it's long enough to
avoid reaching the restart StartLimit settings), besides controlling how
often the service logs a failure and then restart.

I guess this all means that 1) the version in focal-proposed is correct,
and 2) the xenial and bionic versions need the addition of
TimeoutStartSec=600 and Restart=on-failure to their service file, right?
Is that all that's needed?

-- 
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

Reply via email to