Hi All,

I have my rsyslog set to authpriv.*, and I can see in my etc/ssh/secure I have log messages, but they are not being written to my syslog server. I am wondering if someone can point out the obivious I am missing. Thanks.


# 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 c ommand)
$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 ####

rsyslog.conf 
# Use default timestamp format
:
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
:

:
# File syncing capability is disabled by default. This feature is usually not re :
quired,
:
# not useful and an extreme performance hit
:
#$ActionFileEnableSync on
:

:
# Include all config files in /etc/rsyslog.d/
:
$IncludeConfig /etc/rsyslog.d/*.conf
:

:

:
#### 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/iport, e.g. 192.168.0.1:514, port optional
:
#*.* @@remote-host:514
:
*.* @@192.168.20.12:514
:
# ### end of the forwarding rule ###

What is that long thing you posted? Is it a file? What kind of system do you have?