squid runs out of file descriptors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Repository Cache Charm |
Triaged
|
Medium
|
Unassigned | ||
ubuntu-repository-cache (Juju Charms Collection) |
Triaged
|
Medium
|
Unassigned |
Bug Description
On one of our ubuntu-
2016/03/08 06:50:21| Attempt to open socket for EUI retrieval failed: (24) Too many open files
2016/03/08 06:50:21| /srv/ubuntu-
...
2016/03/08 06:54:04| Reserved FD adjusted from 100 to 64538 due to failures
...
2016/03/08 06:54:04| WARNING! Your cache is running out of filedescriptors
When the cache goes into this state, performance is severely limited, per the explanation at http://
Looking at the configuration, it seems that squid is configured to use a maximum of 65536 file descriptors, but the system limit is still 1024:
root@juju-
1024
root@juju-
Maximum number of file descriptors: 65536
Largest file desc currently in use: 13
Number of file desc currently in use: 13
Available number of file descriptors: 65523
Reserved number of file descriptors: 64538
ubuntu-
tags: | added: canonical-is |
Changed in ubuntu-repository-cache (Juju Charms Collection): | |
importance: | Undecided → Medium |
Changed in ubuntu-repository-cache (Juju Charms Collection): | |
status: | New → Triaged |
Changed in ubuntu-repository-cache: | |
status: | New → Triaged |
Changed in ubuntu-repository-cache: | |
importance: | Undecided → Medium |
It should be noted that both /etc/init/ squid3. conf and /etc/init. d/squid- deb-proxy include lines to raise the ulimit, but as the above shows, this does not seem to take effect correctly.
The instance in question was in GCE, if that makes any difference.