Hi Ben,
Thanks for taking your time with this and other questions. Fortunately,
it was the custom code not closing properly a sockets we use. I disabled
our modifications and it became stable again, so it is internal business
now.
As a reference, I used two programs to monitor the number of open file
descriptors:
# Number of FD owned by ovs
lsof | grep ovs-vswitchd | wc -l
# Total FD amount and related figures
sysctl fs.file-nr | awk '{print $3}'
More dettail here
http://www.cyberciti.biz/tips/linux-procfs-file-descriptors.html
Best regards,
Ferran
On 06/06/15 07:21, Ben Pfaff wrote:
> On Wed, Jun 03, 2015 at 03:55:47PM +0200, ferran wrote:
>> Well then, do you think that it's normal to reach the limit of open
>> files under these conditions?
>> Is there any way to limit this so it doesn't crash?
>> And who is openning this file, here?
> OVS file usage should be pretty stable under normal conditions; that is,
> I would not expect it to open an increasing number of files over time.
> The exception is if you add more and more ports or bridges over time,
> since each port or bridge requires OVS to use more file descriptors.
>
> When you see this, can you take a look at the files that OVS has open?
> e.g. "ls -l /proc/$pid/fd" where $pid is the OVS process ID? It would
> also be a good idea to try this with a more recent version of OVS.
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
