Date: Sun, 30 Sep 2007 09:29:18 +0200 From: Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no> To: freebsd-stable@freebsd.org Subject: Re: apache core dump signal 11 after portupgrade from 1.3.37 to 1.3.39 Message-ID: <20070930092918.e48593b4.torfinn.ingolfsen@broadpark.no> In-Reply-To: <20070929203953.7C1BA2E01F@claudel.blackrosetech.com> References: <20070929203953.7C1BA2E01F@claudel.blackrosetech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 29 Sep 2007 13:39:28 -0700 David Gessel <gessel@blackrosetech.com> wrote: > I did a portupgrade -ra to 1.3.39 and after a reboot found apache not > running. I've poked around and haven't found much that's useful - > signal 11 being sometimes associated with memory errors (a memory > test comes up fine, though it is unlikely that an update would crack > the RAM). Otherwise few hints. Any suggestions would be much > appreciated. In my experience, when apache crashes after an upgrade, that usually means that one (or more) of the modules used in your Apache setup (httpd.conf) needs to be reinstalled (portupgrade -f). To try to find out which module(s), I usually disable then one after another in httpd.conf until apache runs stable again. For example, it could be php that is the problem. Good luck! -- Regards, Torfinn Ingolfsen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070930092918.e48593b4.torfinn.ingolfsen>