[syslog-ng] fails if dns error [fixed in 2.1]

[JV]

Thank you Bazsi, 

it is indeed working in 2.1 

/etc/init.d/syslog-ng start
Starting syslog-ng: Error resolving hostname; host='sysremote'
Target host cannot be resolved, persistent disk buffer file will be lost; host='sysremote'
Error resolving hostname; host='sysremote'
Initiating connection failed, reconnecting; time_reopen='10'
[  OK  ]

--- On Wed, 11/12/08, Balazs Scheidler <bazsi at balabit.hu> wrote:

> From: Balazs Scheidler <bazsi at balabit.hu>
> Subject: Re: [syslog-ng] fails if dns error resolvehostnamedestinationforwarding
> To: nycfresh at yahoo.com, "Syslog-ng users' and developers' mailing list" <syslog-ng at lists.balabit.hu>
> Cc: "Peck, Jonathan" <Jonathan.Peck at firstdata.com>, "Geller, Sandor (IT)" <Sandor.Geller at morganstanley.com>
> Date: Wednesday, November 12, 2008, 1:33 PM
> On Wed, 2008-11-12 at 12:12 -0800, JV wrote:
> > I don't expect syslog-ng to resolve a name when
> its not in dns or hosts but i expect syslog-ng to still
> start & run as it has other filter rules saying it needs
> to log to local files.
> > 
> > 
> > Use case is when a system reboots syslog-ng starts up
> before network is fully up on the host, syslog-ng won't
> start and no local logging takes place either. 
> > 
> > We're talking UDP here , so no reason syslog-ng
> can't keep trying to resolve and send new lines when
> needed once network connectivity is working and name
> resolution is complete.
> > Isn't that how the OS native "syslog"
> works ?
> 
> syslog-ng 2.1 has support for retrying the connection after
> start-up,
> but I didn't backport it to 2.0 as it would be too
> risky. Please try
> 2.1, it should work in this case too.
> 
> -- 
> Bazsi