From owner-freebsd-ports@FreeBSD.ORG Sun May 9 16:23:38 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8CACD106564A for ; Sun, 9 May 2010 16:23:38 +0000 (UTC) (envelope-from Hans.F.Nordhaug@hiMolde.no) Received: from malle.himolde.no (malle.hiMolde.no [158.38.68.22]) by mx1.freebsd.org (Postfix) with ESMTP id 14D798FC13 for ; Sun, 9 May 2010 16:23:37 +0000 (UTC) Received: from harr.himolde.no (harr.hiMolde.no [158.38.68.20]) by malle.himolde.no (8.13.8/8.13.8) with ESMTP id o49GNZ0U001442 for ; Sun, 9 May 2010 18:23:35 +0200 Received: from harr.himolde.no (harr.himolde.no [127.0.0.1]) by harr.himolde.no (8.13.1/8.13.1) with ESMTP id o49GNZRF001218 for ; Sun, 9 May 2010 18:23:35 +0200 Received: (from nordhaug@localhost) by harr.himolde.no (8.13.1/8.13.1/Submit) id o49GNZZE001217 for freebsd-ports@freebsd.org; Sun, 9 May 2010 18:23:35 +0200 Date: Sun, 9 May 2010 18:23:35 +0200 From: "Hans F. Nordhaug" To: freebsd-ports@freebsd.org Message-ID: <20100509162335.GA934@hiMolde.no> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Subject: Re: Apache 22 - FreeBSD 8.0 - (httpd), uid 80: exited on signal 11 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 May 2010 16:23:38 -0000 * Helmut Schneider [2010-05-03]: > Hans F. Nordhaug wrote: > > > * Helmut Schneider [2010-05-02]: > > > Hans F. Nordhaug wrote: > > > > > > > I recently upgrade to FreeBSD 8.0 (from 7.2) and suddenly I get a > > > > lot of "(httpd), uid 80: exited on signal 11" in my logs. I have > > > > similar problems with amavisd - see > > > > http://lists.freebsd.org/pipermail/freebsd-questions/2010-April/thread.html#215757 > > > > I'm have updated and recompiled all ports. The logs > > > > /var/log/messages and the httpd error log both just report > > > > "exited on signal 11" or "Segmentation fault (11)" > > > > > > > > Any hints? > > > > > > Find the .core file, start gdb with the core file, type "bt", post > > > the output. > > > > Sorry, I should have mentioned that I can't find any core files. > > "find / -name '*.core'" returns nothing. > > I guess one can assume that > > - you already checked RAM with memtest or so. > - you already check your hard drive (you mentiened you fsck'ed your > hard drive and found errors that wer corrected) > - you are running one or more perl apps within apache? Thx to you and everybody else who have answered so far: - I have (now) checked RAM with memtest for several days. No issues. - Yes, I have already checked my hard drive using fsck, and the few problems that were reported was fixed a week ago. - My websites are using PHP, not Perl. I have checked/fixed the extension loading order using fixphpextorder.sh as posted on http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround It didn't help. I don't have that many extensions - the order is: root@myserver[~](18:18:19)718:>cat /usr/local/etc/php/extensions.ini extension=pgsql.so extension=iconv.so extension=hash.so extension=dom.so extension=gd.so extension=pdo.so extension=zlib.so extension=mbstring.so extension=pdo_mysql.so extension=openssl.so extension=session.so extension=simplexml.so extension=gettext.so extension=sqlite.so extension=mysql.so extension=xml.so Any more hints? Regards, Hans PS! There are still no core files generated. I have ":coredumpsize=unlimited" in /etc/login.conf, but maybe something else is surpressing the core file generation.) PS! The Perl exit problem is still present, but that was related to amavisd.