[rsyslog-notify] Forum Thread: Re: messages are missing from the log - (Mode 'reply')
noreply at adiscon.com
noreply at adiscon.com
Fri Apr 4 20:41:53 CEST 2014
User: awolfson
Forumlink: http://kb.monitorware.com/viewtopic.php?p=24484#p24484
Message:
----------
I got back to rsyslog issues debugging and enabled statistics.
This is what I got after sending 10000 messages by
[code:21vyiq3y]
Messages=10000 delay(usec)=10
Sent 10000 messages
9380 84420 514819 /var/log/test-rsyslog.log
[/code:21vyiq3y]
rsyslog-stat tail (I ran more then once)
[code:21vyiq3y]
pr 4 14:22:00 g5161 rsyslogd-pstats: imuxsock:
submitted=9380 ratelimit.discarded=0 ratelimit.numratelimiters=0
Apr 4 14:22:00 g5161 rsyslogd-pstats: main Q: size=1
enqueued=9387 full=0 maxqsize=25
Apr 4 14:22:30 g5161 rsyslogd-pstats: imuxsock:
submitted=9384 ratelimit.discarded=0 ratelimit.numratelimiters=0
Apr 4 14:22:30 g5161 rsyslogd-pstats: main Q: size=1
enqueued=9394 full=0 maxqsize=25
Apr 4 14:23:00 g5161 rsyslogd-pstats: imuxsock:
submitted=9384 ratelimit.discarded=0 ratelimit.numratelimiters=0
Apr 4 14:23:00 g5161 rsyslogd-pstats: main Q: size=1
enqueued=9396 full=0 maxqsize=25
Apr 4 14:23:30 g5161 rsyslogd-pstats: imuxsock:
submitted=9384 ratelimit.discarded=0 ratelimit.numratelimiters=0
Apr 4 14:23:30 g5161 rsyslogd-pstats: main Q: size=1
enqueued=9399 full=0 maxqsize=25
[/code:21vyiq3y]
Does it mean that some of my 10000 messages were not even submitted to main
queue? What can be done?
This is /etc/rsyslog.conf
[code:21vyiq3y]
# 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
#### 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;local0.none;local1.none;local2.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 ###
[/code:21vyiq3y]
and this is /etc/system.d/test-rsyslog.conf
[code:21vyiq3y]
# GEM customizations:
# 3 File producing logging channels for g4k analytical module,
# postgresql database, and g4k network manager info proxy respectively
# to actually gather the data:
$ModLoad impstats
$PStatInterval 30
$PStatSeverity 7
syslog.=debug /var/log/rsyslog-stats
$SystemLogRateLimitInterval 0
#$MainMsgQueueSize 10000
$MainMsgQueueType LinkedList
$MainMsgQueueDequeueSlowdown 0
#$NainMsgQueueWorkerThreadMinimumMessages 100
#$MainMsgQueueDequeueBatchSize 5000
#$MainMsgQueueWorkerThreads 24
#$ActionQueueType LinkedList
#$ActionQueueSize 100000
#$ActionQueueWorkerThreads 24
#$ActionQueueDequeueBatchSize 5000
##$OMFilelOBufferSize 32k
##$OMFileAsyncWriting on
#$MaxMessageSize 64k
local0.*
/var/log/test-rsyslog.log
local0.* ~
local2.*
/var/log/pgsql.log
[/code:21vyiq3y]
Thanks for the help. I really appreciate it
More information about the rsyslog-notify
mailing list