I unfortunately do not have a way to reproduce this. This indeed happened in a large-ish production env with lots of clients. It's the first time I saw this.
One thing I'm wondering, if rabbit were started with $ sudo rabbitmqctl start_app the systemd unit file probably would not go into effect, and the default limits would apply, right? It's possible that by way of troubleshooting this rabbit instance had been started up via rabbitmqctl (I don't know for sure though). -- 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
