When there are a large number of routers and dhcp agents on a host, we see a syslog error repeated:
"hostname ovs-vswitchd: ovs|1762125|netlink_socket|ERR|fcntl: Too many open files"
If I check the number of filehandles owned by the pid for "ovs-vswitchd unix:/var/run/openvswitch/db.sock" I see close to/at 65535 files.
If I then run the following, we double the limit and (in our case) saw the count rise to >80000:
prlimit -p $pid --nofile=131070
We need to be able to: - monitor via nrpe, if the process is running short on filehandles - configure the limit so we have the option to not run out.
Currently, if I restart the process, we'll lose this setting.
Needless to say, openvswitch running out of filehandles causes all manner of problems for services which use it.
When there are a large number of routers and dhcp agents on a host, we see a syslog error repeated:
"hostname ovs-vswitchd: ovs|1762125| netlink_ socket| ERR|fcntl: Too many open files"
If I check the number of filehandles owned by the pid for "ovs-vswitchd unix:/var/ run/openvswitch /db.sock" I see close to/at 65535 files.
If I then run the following, we double the limit and (in our case) saw the count rise to >80000:
prlimit -p $pid --nofile=131070
We need to be able to:
- monitor via nrpe, if the process is running short on filehandles
- configure the limit so we have the option to not run out.
Currently, if I restart the process, we'll lose this setting.
Needless to say, openvswitch running out of filehandles causes all manner of problems for services which use it.