From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1049 Path: news.gmane.org!not-for-mail From: "George Georgalis" Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: apache2 logs -> svlogd Date: Wed, 15 Feb 2006 10:09:46 -0500 Message-ID: <20060215150946.GC15560@sta.duo> References: <20060213173813.GA6585@home.power> <20060213180402.GA30800@wolfpuppy.org.uk> <20060213182520.GE6585@home.power> <20060214142532.GA1378@sta.duo> <20060214144706.GW3065@always.joy.eth.net> <20060214155838.GB29956@home.power> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1140016218 23807 80.91.229.2 (15 Feb 2006 15:10:18 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 15 Feb 2006 15:10:18 +0000 (UTC) Original-X-From: supervision-return-1285-gcsg-supervision=m.gmane.org@list.skarnet.org Wed Feb 15 16:10:16 2006 Return-path: Envelope-to: gcsg-supervision@gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by ciao.gmane.org with smtp (Exim 4.43) id 1F9OHv-0005QM-4D for gcsg-supervision@gmane.org; Wed, 15 Feb 2006 16:09:51 +0100 Original-Received: (qmail 30913 invoked by uid 76); 15 Feb 2006 15:10:12 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 30908 invoked from network); 15 Feb 2006 15:10:11 -0000 Original-To: supervision@list.skarnet.org Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: <20060214155838.GB29956@home.power> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1049 Archived-At: On Tue, Feb 14, 2006 at 05:58:38PM +0200, Alex Efros wrote: >On Tue, Feb 14, 2006 at 08:17:06PM +0530, Joshua N Pritikin wrote: >> On Tue, Feb 14, 2006 at 09:25:32AM -0500, George Georgalis wrote: >> > >Recommended solution was put 'sleep 1' before svlogd, but for me it's a >> > >little ugly and unreliable. I quoted that; I didn't say it, though I was quoted as doing so a few messages back. It was the context of my question. 'sleep 1' does seem reasonable to me, though not correct and therefore not reliable... the respawn svlogd, as required, approach seems hardly justified though. Yet, I don't completely understand why it is proported to work -- part of the reason I quoted it. (I have an unrelated problem below.) >> What isn't ugly about creating named pipes? I don't think the named >> pipe solution wins the beauty contest either. I'm curious about Alex's runscript: ---[ /service/apache2_access_log/run ]--- #!/bin/sh exec >&2 exec svlogd /var/log/apache2/access/ <>/var/log/apache2/access_log ---[ /service/apache2_access_log/run ]--- because I don't understand the use of '<>'. Any comments or links on this are welcome -- though it doesn't address my needs, I use a standard access logfile for each virtual domain, and would like to use a svlogd for each domain's error log; both cases to manage rotation. Not sure an access (or error) service will help me, besides the apache logfile is being written (in addition) which is what I thought was being avoided by using svlogd... >Named pipes... In short, I think named pipes is better because: >- this is universal solution which can be used for any daemon which prefer > to write log files itself, for example: Xorg :) , xdm, ntpd, emerge :) , > iptraf, mysql, oops (webproxy), samba... maybe some of them can be > configured to use svlogd, but not all (so SINGLE UNIVERSAL UGLY solution > is much better than number of different custom more-or-less ugly > solutions) >- svlogd for named pipe supervised by runsv and won't restart with it > service - no problems with sleep 1 and so >- svlogd can be reconfigured&restarted without restarting service(apache) >- you can have many services sending their logs into same named pipe > (can't imagine how this can be used in real world yet :)) >- ... anything else? ...I think we have a different set of problems and/or concerns... in any event, I won't be doing any apache2 svlogd in the near future, per my unanswered post (log to pipe not working in pkgsrc apache2) on the pkgsrc list, below. >> Ultimately we may need to go beat up apache developers. ;-) Count me in! Cheers, // George ----- Forwarded message from George Georgalis ----- Date: Tue, 14 Feb 2006 13:21:25 -0500 Message-ID: <20060214182125.GD1378@sta.duo> Return-Path: bounces-tech-pkg-owner-george=galis.org@NetBSD.org From: George Georgalis To: tech-pkg@netbsd.org Subject: www/apache2 not accepting command for ErrorLog The pkgsrc apache2 is not happy with a command for ErrorLog, as documented here http://httpd.apache.org/docs/2.2/mod/core.html#errorlog It surprises me that this would be broken. Is there something wrong with the package? With the original source? Or my execution? In this httpd.conf fragment, the former works #ErrorLog /tmp/apache2.ErrorLog ErrorLog "|/bin/cat >>/tmp/apache2.ErrorLog" but the latter causes apache to exit with the error: [crit] (28)No space left on device: mod_rewrite: could not create rewrite_log_lock Configuration Failed I'm quite certain I have free space and inodes, seems like apache2 is trying to do locking on the exec? but what does mod_rewrite have to do with it? I don't load it. My configuration is generic accept for the invocation /usr/pkg/sbin/httpd -DNO_DETACH -f /usr/local/etc/apache2/httpd.conf -e debug -E /tmp/apache.start.err and a very standard NameVirtualHost. // George -- George Georgalis, systems architect, administrator < http://galis.org/ cell:646-331-2027 mailto:george@galis.org ----- End forwarded message ----- -- George Georgalis, systems architect, administrator < http://galis.org/ cell:646-331-2027 mailto:george@galis.org