Re: Problems with Apache 1.3 segfaulting in 5.2.1-RC?

[Dirk-Willem van Gulik]

On Feb 18, 2004, at 5:38 PM, Linh Pham wrote:

Has anyone ran into problems with Apache 1.3.x segfaulting (signal 11)
under FreeBSD 5.2.1-RC[12]? I had to recently re-install FreeBSD on my
home server and grabbed the latest src-all for RELENG_5_2, which ended
up being for 5.2.1-RC2. Afterwards, I compiled and installed Apache 1.3
plus PHP5 and PostgreSQL and got it up and running without any 
problems.

Easiest thing is to obtain a core dump; see the man page for 'ulimit', 
check
'/etc/login.conf' and the apache directive for this.

Otherwise - if it happens a LOT - you can run (from screen if needed)

	gdb /usr/local/sbin/httpd -X

it will then run single process/thread mode; and if there is a segfault 
you'll
inmediately see the culprit. This is generally too slow for a production
server; but will easily handle hobby sites.

Given your setup my guess is some PHP5 plugin (I had similar issues
until I fixed/recompiled gd).
Dw.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Problems with Apache 1.3 segfaulting in 5.2.1-RC?

[Linh Pham]

(I'm not subscribed on the list, so please include me in all replies)

Has anyone ran into problems with Apache 1.3.x segfaulting (signal 11)
under FreeBSD 5.2.1-RC[12]? I had to recently re-install FreeBSD on my
home server and grabbed the latest src-all for RELENG_5_2, which ended
up being for 5.2.1-RC2. Afterwards, I compiled and installed Apache 1.3
plus PHP5 and PostgreSQL and got it up and running without any problems.

Until I checked /var/log/messages. For two nights in a row, I got a slew
of "exited on signal 11" messages for httpd as listed below:

Feb 17 08:13:56 q kernel: pid 21546 (httpd), uid 80: exited on signal 11
Feb 17 08:13:56 q kernel: pid 21236 (httpd), uid 80: exited on signal 11
Feb 17 08:13:56 q kernel: pid 1210 (httpd), uid 80: exited on signal 11
Feb 17 08:13:56 q kernel: pid 508 (httpd), uid 80: exited on signal 11
Feb 17 08:13:56 q kernel: pid 472 (httpd), uid 0: exited on signal 11 (core dumped)
Feb 17 18:33:25 q kernel: pid 84255 (httpd), uid 80: exited on signal 11
Feb 17 18:33:27 q kernel: pid 84254 (httpd), uid 80: exited on signal 11
Feb 17 18:33:29 q kernel: pid 84253 (httpd), uid 80: exited on signal 11
Feb 17 18:33:31 q kernel: pid 84252 (httpd), uid 80: exited on signal 11
Feb 17 18:33:33 q kernel: pid 84251 (httpd), uid 80: exited on signal 11
Feb 17 18:33:35 q kernel: pid 84250 (httpd), uid 80: exited on signal 11
Feb 17 18:33:37 q kernel: pid 84249 (httpd), uid 80: exited on signal 11
Feb 17 18:33:39 q kernel: pid 84248 (httpd), uid 80: exited on signal 11
Feb 17 18:33:41 q kernel: pid 84247 (httpd), uid 80: exited on signal 11

[EMAIL PROTECTED]:~ --> httpd -v
Server version: Apache/1.3.29 (Unix)
Server built:   Feb 17 2004 08:16:33
[EMAIL PROTECTED]:~ --> uname -a
FreeBSD q.internal.closedsrc.org 5.2.1-RC2 FreeBSD 5.2.1-RC2 #0: Sun Feb 15 16:07:21 
PST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/Q  i386

The apache13 port was built and compiled using only "make all install"
and the following in make.conf:

CPUTYPE=p3
CFLAGS=-O -pipe
COPTFLAGS=-O -pipe

Is this a known issue or is there something really b0rked with my
install? Thanks.

-- 
Linh Pham [EMAIL PROTECTED]
Webmaster and FreeBSD Geek  http://closedsrc.org
Apprentice Manager Editor and Writer   http://www.daemonnews.org
Courage: The things I do for love | And So Western Civilization Crumbles


pgp0.pgp
Description: PGP signature