[Expired for rabbitmq-server (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: rabbitmq-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
** Changed in: rabbitmq-server (Ubuntu)
Status: Expired => New
--
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
[Expired for rabbitmq-server (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: rabbitmq-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
