Thank you for taking the time to file a bug report.
Would you be able to come up with a way for us to reproduce this bug? I
understand that it must be happening in a production environment where
thousands of connections are being made, but maybe we can come up with a
way to reproduce it locally as well.
Does this bug happen often, or is it the first time it happened?
I tried finding some similar cases on the internet, but what I found
were reports of real scenarios where increasing the fd limit solved the
problem. Curiously, one of the solutions was to add the LimitNOFILE
directive to the systemd unit file, which is already present in your
case.
I'm subscribing the Ubuntu Server team to this bug so that we can follow
it closely.
** 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
