Hi.
I'm trying to get basic squid info by issuing 'squidclient -p 8080
mgr:info'. Port 8080 is where our squid is listening to connections.
All clients works fine through the squid. But squidclient return http
response (lets say mydomain.com is my domain):
ERROR
The requested URL could not be re
Hi.
What are the reasons of squid rebuilding it's cache? Sometimes after
startup sometimes during work it starts to rebuild cache. I see it in
cahce.log:
2009/01/16 09:30:24| Starting Squid Cache version 2.6.STABLE6 for
x86_64-redhat-linux-gnu...
2009/01/16 09:30:24| Process ID 2625
2009/01/16 0
Hi.
You can use cacti but it's MRTG-like. The best tools I know for squid
reports are sarg (which is rather popular) and lightsquid (it makes
reports a lot faster but I don't know if it's popular outside Russia).
Regards,
LPIC-1, EMCPA
Nikita Andreev
>> 2009/01/16 11:00:35| CACHEMGR: @127.0.0.1 requesting 'info'
>>
>> 2009/01/16 11:00:35| The reply for GET
>> cache_object://localhost.mydomain.com/info is DENIED, because it matched
>> 'all'
>>
> What do your "reply_access" lines look like? The reply to this allowed
> request is denied.
Th
>> 2009/01/16 09:30:24| Starting Squid Cache version 2.6.STABLE6 for
>> x86_64-redhat-linux-gnu...
>> 2009/01/16 09:30:24| Process ID 2625
>> 2009/01/16 09:30:24| With 1024 file descriptors available
>> 2009/01/16 09:30:24| Using epoll for the IO loop
>> 2009/01/16 09:30:24| DNS Socket created at
>>> Why does squid eat 100% of processor if the problem is in FS?
> How is your cache_dir defined? aufs (in general) is a better choice
> than ufs, diskd might still have some stability issues under load, and
> coss is a good supplement as a small object cache. Conceivably if Squid
> is set up
>> I'm not sure but maybe it started after we enlarged our outer link
>> from 2Mbps to 4Mbps.
> is that 4 megabits per second or 4 gigabits per second as you mentioned
> before?
4Mbits. I was mistaken.
>> I will try to move squid cache to local disk but squid works in VMware
>> Virtual Infrastru
>> For 6 days uptime:
>> # vmstat
>> procs ---memory-- ---swap-- -io --system--
>> -cpu--
>> r b swpd free buff cache si sobibo in cs us sy id
>> wa st
>> 2 0 92 104052 235704 2309956 00 343 24 33 10 16 73
>> 1 0
> You mention that you are running this server in VMware. Where is it you are
> measuring the CPU usage from? Since if it's with in the virtual machine then
> that is not accurate. The VM only sees as much available CPU as it needs at
> any one time. For example you could have a server with low sha
Damn! I changed squid cache directory to local partition and still
see the same problem.
# vmstat 2
procs ---memory-- ---swap-- -io --system--
-cpu--
r b swpd free buff cache si sobibo in cs us sy id wa st
1 0 0 3148784 297840 206828
> Also, ensure you have changed the
> 'ufs'
> to
> 'aufs' in your cache_dir configuration line.
> 'ufs' can't scale beyond about 10 clients:)
> -Rob
I did it.
BTW, why does squid have ufs in its default configuration if ufs
doesn't scale beyond 10 clients?
Regards,
Nikita.
For some unknown reason squid stopped using CPU even when I returned
cache to NFS partition:
procs ---memory-- ---swap-- -io --system--
-cpu--
r b swpd free buff cache si sobibo in cs us sy id wa st
2 0 96 2665972 119112 5137560
> Was this change noted after change of Storage Scheme from "ufs" to "aufs"?
> Regards
> HASSAN
No, it wasn't after aufs. I don't know what happened.
Regards,
Nikita.
13 matches
Mail list logo