[Bug 1187808] Re: PreserveFQDN fix introduces regression that might cause rsyslog not to start

[Adam Conrad]

Hello Louis, or anyone else affected,

Accepted rsyslog into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/rsyslog/5.8.6-1ubuntu8.4 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: rsyslog (Ubuntu Precise)
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1187808

Title:
  PreserveFQDN fix introduces regression that might cause rsyslog not to
  start

Status in “rsyslog” package in Ubuntu:
  In Progress
Status in “rsyslog” source package in Precise:
  Fix Committed
Status in “rsyslog” source package in Raring:
  Fix Committed

Bug description:
  LP: #1022545 fix introduced a regression that might cause rsyslog not
  to start, even though the upstream commit seems to claim otherwise :

  ChangeLog
    A temporary buffer was allocated one byte too small. Did only
    affect startup, not actual operations. Came up during routine tests,
    and can have no effect once the engine runs. Bug was introduced in
    7.3.11.

  [Impact]
  As reported in duplicate bug #1187876, this issue causes rsyslog to fail to start in some circumstances due to the resulting malloc corruption, which may cause cloud instances to fail to configure themselves correctly on boot.  This is a critical regression introduced in an SRU.

  [Test case]
  1. reproduce the error with rsyslog failing to start, with errors written to /var/log/upstart/rsyslog.log:
  *** Error in `rsyslogd': malloc(): memory corruption: 0x00000000007b2930 ***
  and verify that 'status rsyslog' shows 'start/spawned' instead of 'start/running'.
  2. kill any lingering rsyslog processes with 'sudo killall rsyslogd && sudo stop rsyslog'.
  3. upgrade to the -proposed version of the package.
  4. verify that rsyslogd is now running ('status rsyslog' shows 'start/running').

  [Regression potential]
  Minimal.  This is a targeted one-character fix for a regression introduced in the previous SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1187808/+subscriptions