[Varnish] #283: varnishlog stops working at 2gb
Varnish
varnish-bugs at projects.linpro.no
Fri Jul 25 12:42:00 CEST 2008
#283: varnishlog stops working at 2gb
------------------------+---------------------------------------------------
Reporter: wichert | Owner: phk
Type: defect | Status: closed
Priority: normal | Milestone: Varnish 2.0 release
Component: varnishlog | Version: trunk
Severity: normal | Resolution: invalid
Keywords: |
------------------------+---------------------------------------------------
Comment (by wichert):
OS limits seem fine:
{{{
[root at wrk-varn01 proxy]# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
max nice (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 27776
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
max rt priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 27776
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
}}}
The filesystem (ext3) also supports larger files. As a test I made a copy
of varnish.log and added it to itself, which worked fine:
{{{
[root at wrk-varn01 log]# cp -a varnish.log /tmp
[root at wrk-varn01 log]# cat varnish.log >> /tmp/varnish.log
[root at wrk-varn01 log]# du -hs /tmp/varnish.log
4.1G /tmp/varnish.log
}}}
.. more poking around ..
strace indeed shows write(2) failing:
{{{
write(4, "\7\0\34\0\03010.7.50.183 59122 0.0.0.0:8"..., 34) = -1 EFBIG
(File too large)
--- SIGXFSZ (File size limit exceeded) @ 0 (0) ---
+++ killed by SIGXFSZ +++
}}}
I wonder why cat succeeds where varnishlog fails.
--
Ticket URL: <http://varnish.projects.linpro.no/ticket/283#comment:2>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator
More information about the varnish-bugs
mailing list