Hey Nathan,
I want to go back into the basic levels which we are talking about.
After reviewing the proxy configuration I am not sure why and how but:
Can you start running the proxy from scratch with basic squid.conf and
go one step at a time forward?
If you have a network then allow this network the access.
If you use ssl_crtd remove it and start working with basic squid.
One step at a time can help you research the issue.
If for example we do know that for 24\48 hours that the server works
fine with no visible issue and memory growth which is out of any limit
of the hardware we can say that we are on the basic stage of "ok" and
now we need to find out more.
Else then the memory growth(which can lead to swapping) are there any
visible issues?
Can you disable the ICAP service for a while for example?
Eliezer
* you can find me at freenode#squid
On 13/12/13 03:50, Nathan Hoad wrote:
This leads me to believe that the objects that are consuming all of
the memory are genuinely using that memory, and are freed on shutdown.
The pools in the 'mem' cache manager page don't reflect this memory
usage at all, so I'm reasonably confident that it's of a type that
doesn't have memory pools, or are reported inaccurately by the pools.
Examples of these are the MemBuf and MemBlob objects, which contain
char* members and thus variable sizes.
So I'm basically at a loss as to what I can do now. Does anyone have
any ideas on what I can do to squash this problem?
Thanks,
Nathan.
