This bug was fixed in the package rsyslog - 5.8.6-1ubuntu9.1
---
rsyslog (5.8.6-1ubuntu9.1) quantal-proposed; urgency=low
* debian/patches/101-fix-rfc5424-instabilities.patch:
- bugfix: instabilities when using RFC5424 header fields (LP: #1059592)
-- Chris J Arges
This bug was fixed in the package rsyslog - 5.8.6-1ubuntu8.1
---
rsyslog (5.8.6-1ubuntu8.1) precise-proposed; urgency=low
* debian/patches/101-fix-rfc5424-instabilities.patch:
- bugfix: instabilities when using RFC5424 header fields (LP: #1059592)
-- Chris J Arges
The new rsyslog package has been running overnight under stress test and
is still performing as expected. I'm marking this one verification-
done since no regression seems present.
** Tags removed: removal-candidate verification-needed
** Tags added: verification-done
** Changed in: rsyslog
After a few hours of stress tests on the original version, I'm not able
to get the cited corruption.
I have installed the version in -proposed and will re-run the stress
test overnight to confirm that no regression exist with the new version.
If nothing is outlined, I will mark it as
@Chris: is there any chance you guys test the SRU fix so the update
doesn't go wasted?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059592
Title:
Message and memory corruption in rsyslog
To
@seb128.
Yes, getting help from caribou on verifying this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059592
Title:
Message and memory corruption in rsyslog
To manage notifications about this
@seb128
I'll do my best to test that one tomorrow morning so we don't waste this
one and hopefully I'll be able to reproduce the message
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059592
Title:
reviewing bug #1092936 and the diff for this change, they don't appear
to be related; the SRU version just happens to be the verison that bug
#1092936 was reported against, there's not a causal relationship here.
** Tags removed: verification-failed
--
You received this bug notification because
Hello Stuart, or anyone else affected,
Accepted rsyslog into quantal-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/rsyslog/5.8.6-1ubuntu9.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/precise-proposed/rsyslog
** Branch linked: lp:~ubuntu-branches/ubuntu/quantal/rsyslog/quantal-
proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059592
Title:
** Changed in: rsyslog (Ubuntu Raring)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059592
Title:
Message and memory corruption in rsyslog
To manage
Thanks, I've uploaded to the 3 series
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059592
Title:
Message and memory corruption in rsyslog
To manage notifications about this bug go to:
** Branch linked: lp:ubuntu/raring-proposed/rsyslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059592
Title:
Message and memory corruption in rsyslog
To manage notifications about this bug go
This bug was fixed in the package rsyslog - 5.8.6-1ubuntu11
---
rsyslog (5.8.6-1ubuntu11) raring; urgency=low
* debian/patches/101-fix-rfc5424-instabilities.patch:
- bugfix: instabilities when using RFC5424 header fields (LP: #1059592)
-- Chris J Arges
** Changed in: rsyslog (Ubuntu Raring)
Assignee: (unassigned) = Chris J Arges (christopherarges)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059592
Title:
Message and memory corruption in
@seb128
Linked a branch for raring. Thanks
** Branch linked: lp:~christopherarges/ubuntu/raring/rsyslog/fix-
lp1059592
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059592
Title:
Message and
@Chris: thanks for preparing the updates, do you think you could get the
fix applied for raring as well? We can't SRU a fix before having it
available in the current serie
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: rsyslog (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: rsyslog (Ubuntu Precise)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Noticed this also affects quantal/raring. Getting patches ready.
** Changed in: rsyslog (Ubuntu Precise)
Assignee: (unassigned) = Chris J Arges (christopherarges)
** Also affects: rsyslog (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: rsyslog (Ubuntu Raring)
** Branch linked: lp:~christopherarges/ubuntu/precise/rsyslog/fix-
lp1059592
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059592
Title:
Message and memory corruption in rsyslog
To manage
** Branch linked: lp:~christopherarges/ubuntu/quantal/rsyslog/fix-
lp1059592
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059592
Title:
Message and memory corruption in rsyslog
To manage
Branches linked for Precise/Quantal SRU. Raring could be fixed by a
5.8.7 sync.
** Description changed:
When using the RFC5424 format, I've seen a number of corruptions in the
messages (missing messages and unprintable characters). I've also had
rsyslog crash out with *** glibc detected
submittodebian patch sent:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693910
** Bug watch added: Debian Bug tracker #693910
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693910
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: rsyslog (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693910
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059592
** Description changed:
When using the RFC5424 format, I've seen a number of corruptions in the
messages (missing messages and unprintable characters). I've also had
rsyslog crash out with *** glibc detected *** rsyslogd: corrupted
double-linked list: ... ***. The message corruptions
** Changed in: rsyslog (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059592
Title:
Message and memory corruption in rsyslog
To manage notifications
Triaged: since the reporter points to the upstream bug/fix
High: Corrupted log messages are going to confuse lots of people and make
debugging other things harder
As a precaution I marked as security; memory corruptions in rsyslog
can't be good
** This bug has been flagged as a security
27 matches
Mail list logo
