probably just add
@version 3.0
to the top of the configfile if you're running at syslog-ng 3.x, only that version communicates with the supervisor process using pipes. This is just a cosmetical change to silence syslog-ng 3.x otherwise it will complain about the configfile.

As I mentioned your host doesn't even seem to receive the logs. As long as you don't see logs with DEBUG severity arriving to your server there is nothing to do on the server side.

Did you check logging settings on your other devices?

On Sat, Nov 13, 2010 at 11:45 AM, add gy <addyg420@yahoo.com> wrote:
Hi,
 
So what changes should i make in syslog config file ???
 
Regards,
Add

--- On Fri, 12/11/10, Matthew Hall <mhall@mhcomputing.net> wrote:

From: Matthew Hall <mhall@mhcomputing.net>
Subject: Re: [syslog-ng] Not able to recive all syslog messages

To: syslog-ng@lists.balabit.hu
Cc: "Sandor Geller" <Sandor.Geller@morganstanley.com>
Date: Friday, 12 November, 2010, 11:08 PM

On Friday, November 12, 2010 06:21:17 Sandor Geller wrote:
> Just out of curiousity: what are these pipes? IIRC your config doesn't
> contain pipes at all.

My guess without having time to read the source: they are probably used for
connecting the master and slave syslog-ng processes for checking the status
to keep syslog-ng running even if there are any crashes or errors.

> Regards,
> Sandor

--
Matthew Hall
______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.campin.net/syslog-ng/faq.html



______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.campin.net/syslog-ng/faq.html