Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 18 May 1999 11:24:21 -0700 (PDT)
From:      Robert Du Gaue <rdugaue@calweb.com>
To:        freebsd-isp@FreeBSD.ORG
Subject:   Re: Apache log files
Message-ID:  <Pine.BSF.4.05.9905181114380.50313-100000@staff.calweb.com>
In-Reply-To: <199905181545.LAA02511@kiwi.datasys.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the responses! Initially I wasn't aware of this ability within
Apache. Here's what we'll be doing. Any ideas on how to make the logging
efficient would be helpful.

Here's crude drawing...

		   WWW Request
		   	|
	   		|
	Foundry ServerIron (load balance/redundant)
           /        	|	\
          /  		|	 \
         / 		|	  \
    Farm1	      Farm2 	  Farm3

               
File System: All WWW dirs are mounted to the Farm systems from a NetApps
F720.



The Foundry will take the request then select a web server that is most
idle and sent the request to that. If a box dies, it is transparant. We
have 2 Foundrys inline for redundancy there as well. About 800+ Virtual
websites are served, each with their own logfile and stats directory. Best
way to log to one facility? When logged to one place, do we then parse
that file out to split up the log files again or is it practically to have
hundreds of 'loggers' running to separate logfiles (I tend to think this
would not be good). So most likely, the end result is to log to one syslog
machine, then parse later? The my_sql solution is intriging as well, but
it would ofcourse require us to select out specific domains essentially
rebuilding a logfile for a specific domain. Performance, wouldn't be a big
issue as we'll probably put the logfiles on a 4th machine and allow all
the process to take place there and then move the results back to the
webserver's filesystem.



 On Tue, 18 May 1999, Ayan George wrote:

> Date: Tue, 18 May 1999 11:45:57 -0400 (EDT)
> From: Ayan George <ayan@kiwi.datasys.net>
> To: freebsd-isp@FreeBSD.ORG
> Subject: Re: Apache log files
> 
> 
> I wonder how much of a perormance impact forking logger would
> have vs. using syslog(), especially on high traffic servers.
> 
> [ Quoted message from Matthias Meyser, recieved May 18,  5:34pm.]
> 
> > Why hacking apache? Instead of specifying a file to log to in the
> > apache.conf you can also specify a command to pipe the entries to.
> > 
> > What about piping to "logger"?
> > 
> 
> [ End message from Matthias Meyser. ]
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-isp" in the body of the message
> 

--------------------------------------------------------------------------
Robert Du Gaue - rdugaue@calweb.com                  http://www.calweb.com
President, CalWeb Internet Services Inc.                    (916) 641-9320
--------------------------------------------------------------------------



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9905181114380.50313-100000>