On Fri, 14 Mar 2014, Tanky Woo wrote:
On Fri, 14 Mar 2014, Tanky Woo wrote:
> Thank you very much, I have read the doc of omfwd module, It is a built-in
module and no need to be loaded.
>
> So: "*.* @xxx.com:514" will use this module, if the action queue is direct,
the dns resolve will be st
> On Fri, 14 Mar 2014, Tanky Woo wrote:
>
> > Thank you very much, I have read the doc of omfwd module, It is a built-in
> > module and no need to be loaded.
> >
> > So: "*.* @xxx.com:514" will use this module, if the action queue is
> > direct, the dns resolve will be stalled at this point, am
On Fri, 14 Mar 2014, Tanky Woo wrote:
Thank you very much, I have read the doc of omfwd module, It is a built-in
module and no need to be loaded.
So: "*.* @xxx.com:514" will use this module, if the action queue is direct,
the dns resolve will be stalled at this point, am I right?
and I have
Thank you very much, I have read the doc of omfwd module, It is a built-in
module and no need to be loaded.
So: "*.* @xxx.com:514" will use this module, if the action queue is direct,
the dns resolve will be stalled at this point, am I right?
and I have configured this with action queue Linked
On Fri, 14 Mar 2014, Tanky Woo wrote:
If the timeout is because the name really doesn't exist in DNS and you get
a timeout rather than a 'does not exist' message, a cacheing server won't
help.
but then the system config is wrong in the first place... Why use a name
that cannot be resolved?
R
> >
> > If the timeout is because the name really doesn't exist in DNS and you get
> > a timeout rather than a 'does not exist' message, a cacheing server won't
> > help.
> >
>
> but then the system config is wrong in the first place... Why use a name
> that cannot be resolved?
>
> Rainer
Becaus
Upgrade to a current version, there have been massive changes in this area
between v5 and v7
David Lang
On Thu, 13 Mar 2014, Tanky Woo wrote:
Date: Thu, 13 Mar 2014 19:50:32 +0800
From: Tanky Woo
Reply-To: rsyslog-users
To: rsyslog@lists.adiscon.com
Subject: [rsyslog] rsyslog v5 blocked by
I have do another test today:
The network environment is:
rsyslog config a udp translate with domain:
*.* @xxx.com:514
a host with private network 10.0.0.0/16, default route is 10.0.0.99, will go by
this net.
and my network with above it is 10.0.0.0/8, and name server is 10.10.0.100,
On Mon, Mar 10, 2014 at 1:12 AM, David Lang wrote:
>
> If the timeout is because the name really doesn't exist in DNS and you get
> a timeout rather than a 'does not exist' message, a cacheing server won't
> help.
>
but then the system config is wrong in the first place... Why use a name
that ca
I think the problem is that he is *forwarding* (via omfwd) and then DNS
does not resolve the destination. By default, the action queue is run in
direct mode, and so the DNS lookup will stall. To solve this, define the
action queue
a) to run in linkedlist or fixedarray mode
b) make sure it has suff
On Mon, 10 Mar 2014, Tanky Woo wrote:
On Mon, 10 Mar 2014, Tanky Woo wrote:
>> On Sun, 9 Mar 2014, Tanky Woo wrote:
>>
>> >> On Sun, 9 Mar 2014, Tanky Woo wrote:
>> >>
>> >> > rsyslog version is 5.8
>> >> >
>> >> > I found rsyslogd will be blocked, if the remote server domain name
can’t r
> On Mon, 10 Mar 2014, Tanky Woo wrote:
>
> >> On Sun, 9 Mar 2014, Tanky Woo wrote:
> >>
> >> >> On Sun, 9 Mar 2014, Tanky Woo wrote:
> >> >>
> >> >> > rsyslog version is 5.8
> >> >> >
> >> >> > I found rsyslogd will be blocked, if the remote server domain name
> >> >> > can’t resolve because o
On Mon, 10 Mar 2014, Tanky Woo wrote:
On Sun, 9 Mar 2014, Tanky Woo wrote:
>> On Sun, 9 Mar 2014, Tanky Woo wrote:
>>
>> > rsyslog version is 5.8
>> >
>> > I found rsyslogd will be blocked, if the remote server domain name can’t
resolve because of timeout.
>> >
>> > I configured the rsyslogd
> On Sun, 9 Mar 2014, Tanky Woo wrote:
>
> >> On Sun, 9 Mar 2014, Tanky Woo wrote:
> >>
> >> > rsyslog version is 5.8
> >> >
> >> > I found rsyslogd will be blocked, if the remote server domain name can’t
> >> > resolve because of timeout.
> >> >
> >> > I configured the rsyslogd to send log to r
James"
Reply-To: rsyslog-users
To: rsyslog-users
Subject: Re: [rsyslog] rsyslog v5 blocked by dns timeout
Also, if you are having DNS timeout issues but you are sending it to the same
place regularly, you might consider using NSCD. It will implement the DNS
caching for you if you are unable
-boun...@lists.adiscon.com [rsyslog-boun...@lists.adiscon.com] On
Behalf Of David Lang [da...@lang.hm]
Sent: Sunday, March 09, 2014 3:30 PM
To: rsyslog-users
Subject: Re: [rsyslog] rsyslog v5 blocked by dns timeout
On Sun, 9 Mar 2014, Tanky Woo wrote:
>> On Sun, 9 Mar 2014, Tanky Woo
On Sun, 9 Mar 2014, Tanky Woo wrote:
On Sun, 9 Mar 2014, Tanky Woo wrote:
> rsyslog version is 5.8
>
> I found rsyslogd will be blocked, if the remote server domain name can’t
resolve because of timeout.
>
> I configured the rsyslogd to send log to remote by udp:
>
> *.* @xxx.com:514
>
> now t
> On Sun, 9 Mar 2014, Tanky Woo wrote:
>
> > rsyslog version is 5.8
> >
> > I found rsyslogd will be blocked, if the remote server domain name can’t
> > resolve because of timeout.
> >
> > I configured the rsyslogd to send log to remote by udp:
> >
> > *.* @xxx.com:514
> >
> > now the name server
On Sun, 9 Mar 2014, Tanky Woo wrote:
rsyslog version is 5.8
I found rsyslogd will be blocked, if the remote server domain name can’t
resolve because of timeout.
I configured the rsyslogd to send log to remote by udp:
*.* @xxx.com:514
now the name server has problem and the dns request will
rsyslog version is 5.8
I found rsyslogd will be blocked, if the remote server domain name can’t
resolve because of timeout.
I configured the rsyslogd to send log to remote by udp:
*.* @xxx.com:514
now the name server has problem and the dns request will timeout(only timeout
will cause this pr
20 matches
Mail list logo
