Date: Thu, 17 Dec 1998 10:10:39 +1300 (NZDT) From: Andrew McNaughton <andrew@squiz.co.nz> To: Marcos Viterbo <mavit@vecom.com> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: CGI problems Message-ID: <Pine.BSF.4.05.9812171003310.334-100000@aniwa.sky> In-Reply-To: <009701be28e1$cbcb3f00$0600000a@work.eca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 16 Dec 1998, Marcos Viterbo wrote: > Greetings. > > I am facing some problems with CGIs (freebsd_2.2.6 + apache_1.3.0). When the > system reaches about 55 apache instances the CGIs won't execute anymore and > returns a 500 error. I recompiled the kernel and libc altring > FD_SETSIZE=1024, maxusers=256, open_max, max_proc (child_max) in the kernel > and login.conf, maxconn to 256, nmbclusters=8192, recompiled apache with a > higher maxclients. The system has 128 MB RAM (it never goes beyond 50MB). > It happens only with external CGIs (PHP3 supports as many instances as the > apache is configured to). Sounds familiar. I had problems first with number of processes and then with number of file handles. It's not your system wide resources that are limited, but your per-process limits. If you set up a CGI like this you'll see it: #!/bin/sh echo Content-type: text/html echo limits My solution was to put some ulimit statements near the head of apachectl. Andrew McNaughton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9812171003310.334-100000>