From owner-freebsd-apache@FreeBSD.ORG Sat Feb 28 00:27:03 2015 Return-Path: Delivered-To: freebsd-apache@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E846CB3B for ; Sat, 28 Feb 2015 00:27:03 +0000 (UTC) Received: from internal.electricembers.net (internal.electricembers.net [208.90.215.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.electricembers.net", Issuer "DigiCert High Assurance CA-3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D3C84210 for ; Sat, 28 Feb 2015 00:27:03 +0000 (UTC) Received: from mail.electricembers.net (npomail1 [208.90.215.73]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ben) by internal.electricembers.net (Postfix) with ESMTPSA id 2A4C027333; Fri, 27 Feb 2015 16:26:56 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 27 Feb 2015 16:26:55 -0800 From: Benjamin Connelly To: freebsd-apache@freebsd.org Subject: ftasv and ScoreBoardFile on FreeBSD 10 with jails Message-ID: X-Sender: ben@electricembers.coop User-Agent: Roundcube Webmail/1.0.2 X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Feb 2015 00:27:04 -0000 We recently upgraded some FreeBSD 9.1 servers to FreeBSD 10.1 and found it broke the scoreboard viewing utility we were using, the "ftasv" port. For that tool to work apache is supposed to be configured to use 'a "name based" shared memory segment' (from their README) by the directive ScoreBoardFile /var/run/apache_status That used to (on 9.1) create that "file". Then we could execute 'ftasv /var/run/apache_status' to interpret that file, and see what requests apache was working to serve. This even worked with many different apache instances running each in their own jail, where all the jails actually share the same basejail /usr/local/sbin/httpd binary. Inside each jail we could see just the requests that instance of apache was working on. But after the FreeBSD upgrade to 10.1 we no longer see the apache_status file in the filesystem, and ftasv seems to actually report the most recent hits from the most recently restarted instance of apache, even if that's in another jail!? (On a system with no jails, it's not a problem, so I suppose I'll cross post to the freebsd-virtualization list too. . .) Has anybody else seen this behavior? Ben