ok, here is the update. I have built a standalone ubuntu box to be
the central server so now have that I can 'play' with. It's a clean
install,and really not sure what to do as this list seems to be the best
resource. So, I would think you can specify 'a' logfile, but I need ALL
the apache logs centrally located, so going to say, take everything from
/var/log/apache2 and send it to the central log server.
The
central log server as I said is a default setup, due to size, I copied them up
to a play webserver, the server can be seen here;
server.conf and the client
here (the only thing changed is the remote IP)
client.confWhen left
like that and syslog-ng is started on the client I get the
following;
Error binding socket; addr='AF_UNIX(/var/log/apache2)',
error='Address already in use (98)'
Error initializing source driver;
source='inputs'
As I said before, I am not looking for anything complex,
etc. Just want ALL the weblogs to goto one box which is really the
function of syslog-ng. I am sure there is one or two things that need a
tweak, and I can go from there.
Thanks.
On Wed, Jul 15, 2009 at 3:45 AM, Sandor Geller
<Sandor.Geller@morganstanley.com> wrote:
Hi,
On Tue, Jul 14, 2009 at 10:06 PM, lance raymond<
lance.raymond@gmail.com> wrote:
> What I thought of
was to make each file unique;
> ws = webserver;
>
>
ws1.domain.com-access_log
> ws2.domain.com-access_log
>
>
and just write them each to an nfs share.
(like syslog-ng) writes to a
file then NFS behaves well. The problems
start when there are multiple
processes trying to access the same
file. Disabling attribute caching in
the NFS client could help, but
this could have a big impact on
performance.
> Not flaming the group at all, actually Bazsi your name shows up
more than
> any of my normal mail :) But, I have tried twice
with a reply or two, and
> once conf files were sent up and/or shown the
thread died. I see some very
> intersting questions, answers on
the group and it would be nice to see some
> of these things, but
really, I am talking about a handful of webservers
> (nothing fancy)
just to write to a central log and it's not working. The
> basic
syslog @server worked perfect, since the platform updates, just not
>
working, but I appreciate the reply.
So could you please tell
what is the actual problem?
Regards,
Sandor