$PreserveFQDN and $LocalHostName not always used

Bug #1191460 reported by Lars Hansson
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
rsyslog (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The $PreserveFQDn and $LocalHostname options are not always used when configured. To be precise, they seem to only be used in messages from rsyslog itself and not from other daemons or applications.
OS: Ubuntu 13.04
Rsyslog: 5.8.11-2ubuntu2.2

Steps to reproduce:

- Configure $PreserveFQDN or $LocalHostName
- Restart rsyslog
- Check in /var/log/syslog. Messages from rsyslog itself will use the fqdn or the configured hostname, messags from sudo, sshd etc etc will only use the plain hostname.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in rsyslog (Ubuntu):
status: New → Confirmed
Revision history for this message
Evan Broder (broder) wrote :

There's a comment at http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/rsyslog/saucy/view/head:/tools/syslogd.c#L2428 that says we need to re-call GenerateLocalHostNameProperty after parsing config, but as far as I can tell, that doesn't happen.

Does adding a call to queryLocalHostname() around line 2958 of tools/syslogd.c make this work?

Revision history for this message
Jason Dusek (solidsnack) wrote :

If you run `reload rsyslog` (which sends SIGHUP) then it will start printing FQDNs for all processes. I noticed this when my Rsyslog started printing FQDNs after logrotate ran...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.