[Bug 1022545] Re: Backport upstream bugfix "$PreserveFQDN on" not working properly

Steve Langasek steve.langasek at canonical.com
Sat May 25 01:59:29 UTC 2013


Hello stchesmeli, 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.3 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

** Tags added: verification-needed

** Changed in: rsyslog (Ubuntu Raring)
       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/1022545

Title:
  Backport upstream bugfix "$PreserveFQDN on" not working properly

Status in “rsyslog” package in Ubuntu:
  Fix Released
Status in “rsyslog” source package in Precise:
  Fix Committed
Status in “rsyslog” source package in Quantal:
  Won't Fix
Status in “rsyslog” source package in Raring:
  Fix Committed

Bug description:
  SRU justification :

  The $PreserveFQDN functionality does not work as expected. Even when
  defining it as 'on', the fully qualified domain name is not reported
  by rsyslog

  Impact :

  Unable to have the FQDN added to the hostname in syslog

  Fix :

  Upstream fix committed to upcoming 7.4 version of rsyslog :

  http://git.adiscon.com/?p=rsyslog.git;a=commitdiff_plain;h=89ace1e401dc179a20ec283c2f7c2f80becf4700

  Test Case :

  1. Configure rsyslog on a system that has the hostname defined with fully
     qualified domain name in /etc/hosts :

  192.168.122.10      rsyslogserver.localdomain.com    rsyslogserver

  The hostname -f command should return the hostname with FQDN appended
  :

  $ hostname -f
  rsyslogserver.localdomain.com

  2. Add the following entry in /etc/rsyslog.conf

  $PreserveFQDN on

  3. Restart rsyslogd :

  $ restart rsyslog

  4. Verify in /var/log/syslog that hostname + fqdn appears :

  Apr 25 14:13:29 rsyslogserver.localdomain.com kernel: imklog 5.8.6,
  log source = /proc/kmsg started.

  With the current version of rsyslog, only the hostname appears

  Regression :

  Minimal risk as the value defined by the patch is only used if the
  $PreserveFQDN variable is defined in /etc/rsyslog.conf, which is
  absent by default.

  Description of the problem :

  When adding $PreserveFQDN on in /etc/rsyslog.conf to have the Fully
  Qualified Domain Name appended to the hostname reported by rsyslog,
  the functionality does not work and only the hostname is reported.

  
  Original description (which is wrong as the cited commit does not fix the problem)

  You will find patch and information here:

  http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=dec9bcfe2a869b0f70b5f2a18e08a0322ebf5517

  Please backport this patch for precise.

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




More information about the foundations-bugs mailing list