From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 04:18:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21B6B16A4CF for ; Sun, 28 Mar 2004 04:18:37 -0800 (PST) Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE69943D39 for ; Sun, 28 Mar 2004 04:18:35 -0800 (PST) (envelope-from Holger.Kipp@alogis.com) Received: from intserv.int1.b.intern (localhost [127.0.0.1]) by alogis.com (8.11.1/8.9.3) with SMTP id i2SCIVb41656; Sun, 28 Mar 2004 14:18:31 +0200 (CEST) (envelope-from hk@alogis.com) Message-Id: <200403281218.i2SCIVb41656@alogis.com> Date: Sun, 28 Mar 2004 12:18:26 +0000 From: Holger Kipp To: martin@mullet.se X-Mailer: phpGroupWare (http://www.phpgroupware.org) MIME-version: 1.0 Content-type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-description: Mail message body cc: freebsd-current@freebsd.org Subject: [SOLVED] mod_usertrack: apache "exited on signal 11" on FreeBSD 5.2 CURRENT (now) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Holger.Kipp@alogis.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Mar 2004 12:18:38 -0000 Martin Nilsson (martin@mullet.se) wrote: > > >Holger Kipp wrote: >> Just checked if this is the same with the latest FreeBSD 5.2-CURRENT >> from now (cvsupped an hour ago), also rebuilding apache13-modssl >> with portupgrade. >> >> Same behaviour: Everything works fine with CookieTracking off, but >> with CookieTracking on, I get clean 'signal 11'. This is with >> CookieStyle Netscape and CookieStyle Cookie. CookieStyle Cookie2 >> seems to work, but then I receive a different Cookie per request :-( > >Hi, I had the same problem but solved it with adding the following to my >httpd.conf: > >CookieName Apache > [...] >This problem is also present in 4.9, I heven't had time to debug it further. That bug was introduced with the 'latest' version of mod_usertrack. See http://issues.apache.org/bugzilla/show_bug.cgi?id=24483 for details. It is only necessary to set CookieName explicitly. As soon as the latest version of Apache (affects both 1.3 and 2.0) is in the ports, the problem should go away. Fix for 2.0.49 went only in 25.03.2004, though. Sorry for the noise. Regards, Holger Kipp