Hi again :)
Another follow-up to this tiny thread: I've done the dh-autoreconf and
rebuilt the packages, as Michael suggested. Now omelasticsearch is loading
up fine. Thanks again!
Still, the issues previously reported are the same:
- segfault when receiving a message from UNIX socket
- stopping
Hi again :)
Another follow-up to this tiny thread: I've done the dh-autoreconf and
rebuilt the packages, as Michael suggested. Now omelasticsearch is
loading
up fine. Thanks again!
Still, the issues previously reported are the same:
- segfault when receiving a message from UNIX socket
Just a quick follow-up: I currently work with Rick on this issue. It looks like
there are actually two issues in one:
1) in v5, it can happen that an action in front of an included get's reordered,
and this seems to have happened here. This is actually the second time in many
years that I see
Aha! Nice catch, Rainer! It happens with the manually compiled rsyslog as
well.
Attached you can find my debug log, while the config is as easy as:
# cat /etc/rsyslog.conf
module(load=imuxsock)
*.* /var/log/syslog
I got a clean VirtualBox machine running Ubuntu 12.04 server - always
reverting to
-Original Message-
From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog-
boun...@lists.adiscon.com] On Behalf Of Radu Gheorghe
Sent: Monday, December 17, 2012 3:28 PM
To: rsyslog-users
Subject: [rsyslog] Segfault on UNIX socket message (was: Ubuntuv7-devel
packages)
Aha! Nice
2012/12/17 Rainer Gerhards rgerha...@hq.adiscon.com
-Original Message-
From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog-
boun...@lists.adiscon.com] On Behalf Of Radu Gheorghe
Sent: Monday, December 17, 2012 3:28 PM
To: rsyslog-users
Subject: [rsyslog] Segfault on UNIX
-Original Message-
From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog-
boun...@lists.adiscon.com] On Behalf Of Radu Gheorghe
Sent: Monday, December 17, 2012 3:46 PM
To: rsyslog-users
Subject: Re: [rsyslog] Segfault on UNIX socket message (was: Ubuntuv7-
devel packages)
Thanks again Michael, I changed the debian rules, and added build dep as you
recommended and updated the packages.
I will also change the naming to 0adisconX when 7.3.5 comes out.
Best regards,
Andre
-Original Message-
From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog-
-Original Message-
From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog-
boun...@lists.adiscon.com] On Behalf Of Andre Lorbach
Sent: Monday, December 17, 2012 4:08 PM
To: rsyslog-users
Subject: Re: [rsyslog] Ubuntu 12 (Precise) v7-devel packages
Thanks again Michael, I
2012/12/17 Rainer Gerhards rgerha...@hq.adiscon.com
-Original Message-
From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog-
boun...@lists.adiscon.com] On Behalf Of Radu Gheorghe
Sent: Monday, December 17, 2012 3:46 PM
To: rsyslog-users
Subject: Re: [rsyslog] Segfault on
Just a quick follow-up: I currently work with Rick on this issue. It
looks like there are actually two issues in one:
1) in v5, it can happen that an action in front of an included get's
reordered, and this seems to have happened here. This is actually the
second time in many years that I
-Original Message-
From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog-
boun...@lists.adiscon.com] On Behalf Of Rainer Gerhards
Sent: Monday, December 17, 2012 6:27 PM
To: rsyslog-users
Subject: Re: [rsyslog] imfile and omudpspoof
Just a quick follow-up: I currently work
Hello everyone,
I'm running into a strange problem with some new RHEL 6 servers I've
built. I can go for days without anything appearing to get logged (to
any file/remote server), but then when I restart rsyslog via the
provided initscripts, logs magically appear! Obviously there's some
There was a bug in some old version that enabled buffered mode by default. Not
sure if you have such a version. Look at omfile doc, if you turn it off
manually, that will work.
Rainer
-Original Message-
From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog-
On Mon, 17 Dec 2012, John Miller wrote:
On 12/17/2012 05:02 PM, David Lang wrote:
My guess is that something is interrupting the TCP connection and logs
then stop (possibly a firewall or NAT timeout), logs are then buffered
until something gets restarted and they start flowing again.
Right
By the way, as the original author of omudpspoof, I want to try and discourage
anyone from using it if they have any other way of making things work.
It is a very ugly hack, and it's performance is always going to be poor due to
the overhead of changing the source IP address for the forgery.
16 matches
Mail list logo