ratelimit.numratelimiters=0
no imtcp ipv4/ipv6 601
no imudp ipv4 514
Idea ?
--
View this message in context:
http://rsyslog-users.1305293.n2.nabble.com/Big-issues-with-Rsyslog-listening-on-port-514-with-IMRELP-tp7579826p7584196.html
Sent from the rsyslog-users mailing list archive at Nabble.com
/syslogLAN
stop
What's the next step to understand what happens ?
--
View this message in context:
http://rsyslog-users.1305293.n2.nabble.com/Big-issues-with-Rsyslog-listening-on-port-514-with-IMRELP-tp7579826p7584177.html
Sent from the rsyslog-users mailing list archive at Nabble.com
this message in context:
http://rsyslog-users.1305293.n2.nabble.com/Big-issues-with-Rsyslog-listening-on-port-514-with-IMRELP-tp7579826p7584177.html
Sent from the rsyslog-users mailing list archive at Nabble.com.
___
rsyslog mailing list
http://lists.adiscon.net
On Feb 3, 2014, at 12:11 PM, David Lang da...@lang.hm wrote:
On Mon, 3 Feb 2014, ecze wrote:
So , I'm still blocked. Why rsyslog :
1. stop to listen imtcp for new connection
2. stop to listen imudp 514
what is probably happening is that since you can't send logs to postgres, the
:
http://rsyslog-users.1305293.n2.nabble.com/Big-issues-with-Rsyslog-listening-on-port-514-with-IMRELP-tp7579826p7584152.html
Sent from the rsyslog-users mailing list archive at Nabble.com.
___
rsyslog mailing list
http://lists.adiscon.net/mailman
On Fri, 31 Jan 2014, ecze wrote:
Hi all,
Same issue here in our environment.
RHEL 6.5 latest rsyslog V7 stable from adiscon
rsyslog, listen to port udp 514 some seconds and stops...
imtcp 514: same issue...
I see with netstat a 0.0.0.0:514 but after 3-4 incoming streams, the
daemon stop
tell you something.
Alan Edmonds
-Original Message-
From: rsyslog-boun...@lists.adiscon.com
[mailto:rsyslog-boun...@lists.adiscon.com] On Behalf Of David Lang
Sent: 11 March 2013 21:36
To: rsyslog-users
Subject: Re: [rsyslog] Big issues with Rsyslog listening on port 514
with IMRELP
] On Behalf Of David Lang
Sent: 11 March 2013 21:36
To: rsyslog-users
Subject: Re: [rsyslog] Big issues with Rsyslog listening on port 514
with IMRELP
On Mon, 11 Mar 2013, Nicolas HAHN wrote:
Hello all,
I'm writing for the first time to this mailing-list in the hope that
somebody already
Hello Rainer,
We run it only with -d.
I'll try to run it with -dn as you suggest, and I'll come back to the mailing
list :)
Then, I'll try after that to run it under valgrind as per your second
suggestion.
Also, I've seen that when I stop rsyslog using the famous well known command
service
On Tue, 2013-03-12 at 16:35 +0100, Nicolas HAHN wrote:
Hello Rainer,
We run it only with -d.
I'll try to run it with -dn as you suggest, and I'll come back to the mailing
list :)
Then, I'll try after that to run it under valgrind as per your second
suggestion.
Also, I've seen that
I'm back as said previously :)
Well, I did the test launching rsyslogd like this:
rsyslogd -4 -dn
and also like this:
rsyslogd -dn
I stopped and started again rsyslogd several times like that. I let it run
several minutes each time, redirecting all the debug output to a file.
First
On Tue, 2013-03-12 at 17:22 +0100, Nicolas HAHN wrote:
I'm back as said previously :)
Well, I did the test launching rsyslogd like this:
rsyslogd -4 -dn
and also like this:
rsyslogd -dn
I stopped and started again rsyslogd several times like that. I let it run
several minutes
Hello all,
I'm writing for the first time to this mailing-list in the hope that somebody
already experimented the issue I describe below.
At first, here is the Linux server profile on which is running Rsyslog, if it
can have an importance:
- Server type: physical and dedicated (not a VM). HP
On Mon, 11 Mar 2013, Nicolas HAHN wrote:
Hello all,
I'm writing for the first time to this mailing-list in the hope that somebody
already experimented the issue I describe below.
At first, here is the Linux server profile on which is running Rsyslog, if it
can have an importance:
- Server
14 matches
Mail list logo
