Thanks for the reply, Peter.
Yes, if you start rabbitmqctl directly via the command line then the
systemd unit will not be invoked, and process will use the default
limits specified by the system. If that is the way you invoked
rabbitmqctl, then what you can do is modify the limits before executing
the command, and see if it has any effect in mitigating the issue.
Since it is still unclear how to reproduce the issue reliably, and given
that the program might have been executed without setting the limits
first, I'm marking this as Incomplete again. Let us know if you come up
with more details about the issue. Thanks!
** Changed in: rabbitmq-server (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905423
Title:
Rabbit reports "file descriptor limit alarm set", does not accept
connections
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1905423/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
