Date: Thu, 20 Mar 2003 13:08:29 -0500 From: Scott Lambert <lambert@lambertfam.org> To: FreeBSD-questions@FreeBSD.org Cc: lambert@lambertfam.org Subject: ulimit data seg size / analog Message-ID: <20030320180829.GA36374@laptop.lambertfam.org>
next in thread | raw e-mail | index | archive | help
I am not subscribed to -questions, please cc: me. I have a web site that has recently been getting a lot of traffic. The apache logs for one week are 1.2GB gzip'ed. Analog is bombing out on me while running dealing with a week's log during the build of the request report. analog.cfg has: FILELOWMEM 1 HOSTLOWMEM 1 BROWLOWMEM 1 REFLOWMEM 1 It is still bombing on a machine with 1GB RAM and 2 GB swap. I think the data segment size and/or virtual memory portions of the ulimit values are to blame but I have not yet found the magic to up that limit. # ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) 524288 file size (blocks, -f) unlimited max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) 11095 pipe size (512 bytes, -p) 1 stack size (kbytes, -s) 65536 cpu time (seconds, -t) unlimited max user processes (-u) 5547 virtual memory (kbytes, -v) 589824 What makes me think it's a 512MB limit?: Thu Mar 20 11:22:47 EST 2003 scott 82337 83.1 32.4 338512 337412 p0 R 11:03AM 15:40.98 analog +O/hom e/ Thu Mar 20 11:22:52 EST 2003 scott 82337 86.5 32.4 338940 337908 p0 R 11:03AM 15:45.99 analog +O/hom e/ Thu Mar 20 11:22:57 EST 2003 scott 82337 89.3 33.8 353796 352860 p0 R 11:03AM 15:50.99 analog +O/hom e/ Thu Mar 20 11:23:02 EST 2003 scott 82337 91.4 43.8 457912 457096 p0 R 11:03AM 15:55.98 analog +O/hom e/ Thu Mar 20 11:23:07 EST 2003 Thu Mar 20 11:23:12 EST 2003 -rw-r--r-- 1 scott scott 340 Mar 20 11:23 030303.runanalog.log analog: analog version 5.24/Unix analog: Warning D: In Browser Summary, SORTBY (requests) doesn't match SUBSORTBY (pages) (For help on all errors and warnings, see docs/errors.html) analog: Warning D: In Browser Summary, FLOOR (requests) doesn't match SUBFLOOR (pages) analog: Fatal error: Ran out of memory: cannot continue: exiting I think the 100+MB growth in 5 seconds happenned immediately after it finished reading the log files. It also implies to me that before the next 5 seconds passed, it crossed 512MB and the kernel refused to allow it to allocate more RAM. -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030320180829.GA36374>