From owner-freebsd-questions@FreeBSD.ORG Sat Jul 4 20:13:25 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A366D1065670 for ; Sat, 4 Jul 2009 20:13:25 +0000 (UTC) (envelope-from bferrell@baywinds.org) Received: from baywinds.org (dsl092-017-098.sfo1.dsl.speakeasy.net [66.92.17.98]) by mx1.freebsd.org (Postfix) with ESMTP id 53AE48FC14 for ; Sat, 4 Jul 2009 20:13:24 +0000 (UTC) (envelope-from bferrell@baywinds.org) Received: from [66.92.17.195] (spa3000 [66.92.17.195]) by baywinds.org (8.13.6/8.13.6/SuSE Linux 0.8) with ESMTP id n64KDKLO002393; Sat, 4 Jul 2009 13:13:23 -0700 Message-ID: <4A4FB7E0.3040809@baywinds.org> Date: Sat, 04 Jul 2009 13:13:20 -0700 From: Bruce Ferrell User-Agent: Thunderbird 2.0.0.21 (X11/20090310) MIME-Version: 1.0 To: Per olof Ljungmark References: <4A4F6841.3020408@intersonic.se> In-Reply-To: <4A4F6841.3020408@intersonic.se> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Annoying problem with apache22 / php5 - how to investigate? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jul 2009 20:13:25 -0000 Per olof Ljungmark wrote: > Hi, > > We run 7-STABLE and apache22 with php5 serving pages from a webmail app > (Horde). > > Randomly (as it seems at least), there is a 500 (Internal server error) > and a blank page is presented to the user like > > [04/Jul/2009:15:19:37 +0200] "GET > /services/portal/sidebar.php?httpclient=1 HTTP/1.1" 500 - > > There are no other messages in the logs, not even with LogLevel debug. > The problem has survived several both OS and port upgrades and I really > need to track this down now. > > Question: What OS tools would be the best to further analyze this? > Someone with more exparience running this combo perhaps would know? > > Thanks a lot! > > -- > per I'd look in the Apache error_log