Hi, I'm currently somehow unable to reproduce the previous behaviour. However with config attached, messages from imklog has FQDN, but from imuxsock has only hostname (without domain). This weird behaviour apply to v5 and v7.
Milan ATTACHEMENT rsyslog.conf: # rsyslog v5 configuration file # For more information see /usr/share/doc/rsyslog-*/rsyslog_conf.html # If you experience problems, see http://www.rsyslog.com/doc/troubleshoot.html #### MODULES #### $ModLoad imuxsock # provides support for local system logging (e.g. via logger command) $ModLoad imklog # provides kernel logging support (previously done by rklogd) #$ModLoad immark # provides --MARK-- message capability # Provides UDP syslog reception #$ModLoad imudp #$UDPServerRun 514 # Provides TCP syslog reception #$ModLoad imtcp #$InputTCPServerRun 514 #### GLOBAL DIRECTIVES #### # Use default timestamp format $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat # File syncing capability is disabled by default. This feature is usually not required, # not useful and an extreme performance hit #$ActionFileEnableSync on # Include all config files in /etc/rsyslog.d/ #$IncludeConfig /etc/rsyslog.d/*.conf $PreserveFQDN on #### RULES #### # Log all kernel messages to the console. # Logging much else clutters up the screen. #kern.* /dev/console # Log anything (except mail) of level info or higher. # Don't log private authentication messages! *.info;mail.none;authpriv.none;cron.none /var/log/messages # The authpriv file has restricted access. authpriv.* /var/log/secure # Log all the mail messages in one place. mail.* -/var/log/maillog # Log cron stuff cron.* /var/log/cron # Everybody gets emergency messages *.emerg * # Save news errors of level crit and higher in a special file. uucp,news.crit /var/log/spooler # Save boot messages also to boot.log local7.* /var/log/boot.log # ### begin forwarding rule ### # The statement between the begin ... end define a SINGLE forwarding # rule. They belong together, do NOT split them. If you create multiple # forwarding rules, duplicate the whole block! # Remote Logging (we use TCP for reliable delivery) # # An on-disk queue is created for this action. If the remote host is # down, messages are spooled to disk and sent when it is up again. #$WorkDirectory /var/lib/rsyslog # where to place spool files #$ActionQueueFileName fwdRule1 # unique name prefix for spool files #$ActionQueueMaxDiskSpace 1g # 1gb space limit (use as much as possible) #$ActionQueueSaveOnShutdown on # save messages to disk on shutdown #$ActionQueueType LinkedList # run asynchronously #$ActionResumeRetryCount -1 # infinite retries if host is down # remote host is: name/ip:port, e.g. 192.168.0.1:514, port optional #*.* @@remote-host:514 # ### end of the forwarding rule ### ----- Original Message ----- > From: "Rainer Gerhards" <[email protected]> > To: "rsyslog-users" <[email protected]> > Sent: Tuesday, October 30, 2012 4:11:41 PM > Subject: Re: [rsyslog] $PreserveFQDN with imuxsock on rsyslog v7.2.1? > > > -----Original Message----- > > From: [email protected] [mailto:rsyslog- > > [email protected]] On Behalf Of Milan Bartos > > Sent: Tuesday, October 30, 2012 10:59 AM > > To: rsyslog-users > > Subject: [rsyslog] $PreserveFQDN with imuxsock on rsyslog v7.2.1? > > > > Hi, > > > > I've a little lack of understanding of $PreserveFQDN directive. > > It's > > set to "on", but FQDN is preserved only in messages from rsyslog > > itself, not from imuxsock (don't know about messages from other > > modules): > > > > Oct 30 08:47:46 localhost.localdomain rsyslogd: [origin > > software="rsyslogd" swVersion="7.2.1" x-pid="1613" x- > > info="http://www.rsyslog.com";] start > > Oct 30 08:47:52 localhost mbartos: message > > > > The second log is sent via logger command. > > Is this correct behaviour that appears in 7.2.1? It works as > > expected > > with 5.8.10: > > > > Oct 30 10:04:47 localhost.localdomain rsyslogd: [origin > > software="rsyslogd" swVersion="5.8.10" x-pid="1447" x- > > info="http://www.rsyslog.com";] start > > Oct 30 10:04:55 localhost.localdomain mbartos: message > > Does this happen with the same config file? If so, can you pls mail > it to me (there are a couple of parameters that are interrelated and > I want to be sure to test with the right set). > > Thanks, > Rainer > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a > myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT > POST if you DON'T LIKE THAT. >
rsyslog.conf
Description: Binary data
_______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
