Hi,
which OS are you using?
If you're using linux and your /var/log partition's filesystem
is ext2 or ext3, the problem is that these filesystems
by default don't supports files larger than 2gb.
To solve this problem you should reformat your
/var/log partition (with mkfs), specifing an higher limit.
This is not a squid problem but a filesystem limit.
Another solution is to use a software like logrotate
to rotate the logs when they grow to more than 1.5gb
ciao
Roberto
----- Original Message -----
From: "Ampugnani, Fernando" <fernando.ampugnani@eds.com>
To: <squid-users@squid-cache.org>
Sent: Wednesday, March 26, 2003 4:04 PM
Subject: [squid-users] Service down.
Hi all,
My access.log had 2.0 Gb more or less and squid shut down alone. The
question is, support squid an access.log as big as 2.0 gb or more?.
I have 3.6 gb in the log īs file system.
I send the cache.log error of that moment.
2003/03/26 11:10:35| Took 2.9 seconds (56618.3 entries/sec).
FATAL: logfileWrite: /usr/local/squid/logs/access.log: (0) Success
Squid Cache (Version 2.4.STABLE4): Terminated abnormally.
CPU Usage: 141873.640 seconds = 53158.470 user + 88715.170 sys
Maximum Resident Size: 0 KB
Page faults with physical i/o: 360775
Memory usage for squid via mallinfo():
total space in arena: 150678 KB
Ordinary blocks: 106093 KB 9375 blks
Small blocks: 0 KB 0 blks
Holding blocks: 176 KB 1 blks
Free Small blocks: 0 KB
Free Ordinary blocks: 44584 KB
Total in use: 106269 KB 71%
Total free: 44584 KB 30%
Thanks in advance.
Fernando Ampugnani
EDS Argentina - Software, Storage & Network
Global Operation Solution Delivery
Tel: 5411 4704 3428
Mail: fernando.ampugnani@eds.com
Received on Wed Mar 26 2003 - 09:14:02 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:14:21 MST