Still got messages on the console.

This is the place for you, if you got rsyslog up and running but wonder how to make it do what you want.

Moderator: rgerhards

Still got messages on the console.

Postby vito.tao on Wed Sep 10, 2008 3:27 am

Hi,

In the rsyslog.conf file, the rule on logging kernel messages to the console has been disabled like this,

# Log all kernel messages to the console.
# Logging much else clutters up the screen.
#kern.* /dev/console


However, I still got messages on all the consoles (that means when using multiple consoles, the message will be shown on all of them), as the following,

Message from syslogd@10.0.7.63 at Sep 8 15:51:28 ...
upgrade: APP Version not match, upgrade required!

Message from syslogd@10.0.7.63 at Sep 8 15:51:28 ...
upgrade: backup mtd6

Message from syslogd@10.0.7.63 at Sep 9 17:29:20 ...
kernel: Disabling IRQ #30

I need to receive log information from other devices on the internet, hence, the following command is added to the configure file,

$template DynaFile,"/var/log/system-%HOSTNAME%/%$YEAR%/%$MONTH%/%$DAY%/message.log"
*.* -?DynaFile

It works well.

I don't know how to avoid from receive the messages from the console. Could anyone here help me? Many thanks!

Operating System: Fedora Release 9 (Sulphur)

rsyslog V3

And I use "-c3 -x" to active receiving log information from internet devices.

The configure file:
Code: Select all

#rsyslog v3 config file

# if you experience problems, check
# http://www.rsyslog.com/troubleshoot for assistance

#### MODULES ####

$ModLoad imuxsock.so   # provides support for local system logging (e.g. via logger command)
$ModLoad imklog.so   # provides kernel logging support (previously done by rklogd)
#$ModLoad immark.so   # provides --MARK-- message capability

# Provides UDP syslog reception
$ModLoad imudp.so
$UDPServerRun 514

# Provides TCP syslog reception
$ModLoad imtcp.so 
$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


#### 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

# Save STB messages to STB log
$template DynaFile,"/var/log/system-%HOSTNAME%/%$YEAR%/%$MONTH%/%$DAY%/message.log"
*.* -?DynaFile




# ### 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/spppl/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 ###

Last edited by vito.tao on Wed Sep 10, 2008 9:51 am, edited 1 time in total.
vito.tao
New
 
Posts: 4
Joined: Wed Sep 10, 2008 3:04 am

Professional Services Information

  • Custom written rsyslog.conf?
  • Maintenance Contract?
  • Installation support?

Re: Still got messages on the console.

Postby rgerhards on Wed Sep 10, 2008 9:22 am

Please post your complete config file.
User avatar
rgerhards
Site Admin
 
Posts: 1780
Joined: Thu Feb 13, 2003 11:57 am

Re: Still got messages on the console.

Postby vito.tao on Wed Sep 10, 2008 9:52 am

The config file has been posted. Thanks.
vito.tao
New
 
Posts: 4
Joined: Wed Sep 10, 2008 3:04 am

Re: Still got messages on the console.

Postby rgerhards on Wed Sep 10, 2008 9:55 am

thanks for the config post. Just be warned that I do not always notice edited posts, so it probably is better to reply ;)

The config looks indeed good. Did you restart rsyslogd after making this change? If not, that's the problem. If you restarted it, we need to dig deeper into debugging.
User avatar
rgerhards
Site Admin
 
Posts: 1780
Joined: Thu Feb 13, 2003 11:57 am

Re: Still got messages on the console.

Postby vito.tao on Wed Sep 10, 2008 10:02 am

Yes. I restarted rsyslog after the config file modification. Actually, just now, I restarted it and the remote device again. Still, there were some messages come to my console...

Message from syslogd@10.0.7.61 at Sep 10 16:59:52 ...
bootmenu:****

Message from syslogd@10.0.7.61 at Sep 10 16:59:52 ...
bootmenu: ****

Message from syslogd@10.0.7.61 at Sep 10 16:59:52 ...
bootmenu: ****

Message from syslogd@10.0.7.61 at Sep 10 16:59:53 ...
bootmenu: ****

Message from syslogd@10.0.7.61 at Sep 10 16:59:53 ...
bootmenu: ****

Message from syslogd@10.0.7.61 at Sep 10 16:59:53 ...
bootmenu: ****

Message from syslogd@10.0.7.61 at Sep 10 16:59:53 ...
bootmenu: ****

**** stands for some information that should not to be post here. Sorry for that.
vito.tao
New
 
Posts: 4
Joined: Wed Sep 10, 2008 3:04 am

Re: Still got messages on the console.

Postby vito.tao on Wed Sep 10, 2008 10:27 am

Dear Rgerhards,

I have fixed the problem ^^. The command

*.emerg *

makes the emergency messages come to the console. After ignore this, everything works fine.

Thanks!
vito.tao
New
 
Posts: 4
Joined: Wed Sep 10, 2008 3:04 am

Re: Still got messages on the console.

Postby rgerhards on Wed Sep 10, 2008 10:40 am

oh, lol,, I have overlooked that, too. Actually, it does not only make them appear on the console, but at each user's screen. Note that disabling this rule will probably also disable shutdown, power fail and similar messages... (but that's distro-specific and I do not know exactly who does what ;)).
User avatar
rgerhards
Site Admin
 
Posts: 1780
Joined: Thu Feb 13, 2003 11:57 am

Google Ads



Return to Configuration

Who is online

Users browsing this forum: No registered users and 0 guests

cron