4

I am using a Centos Linux OS with ssh tools. I get these messages every minute.

Message from syslogd@rakhsh4 at May  6 17:48:34 ...
 kernel:[Hardware Error]: Corrected error, no action required.

Message from syslogd@rakhsh4 at May  6 17:48:34 ...
 kernel:[Hardware Error]: CPU:6 (10:9:1) MC4_STATUS[Over|CE|MiscV|-|AddrV|CECC]: 0xdc02400021080a13

Message from syslogd@rakhsh4 at May  6 17:48:34 ...
 kernel:[Hardware Error]: Error Addr: 0x0000000654f3f030

Message from syslogd@rakhsh4 at May  6 17:48:34 ...
 kernel:[Hardware Error]: MC4 Error (node 1): DRAM ECC error detected on the NB.

Message from syslogd@rakhsh4 at May  6 17:48:34 ...
 kernel:[Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: RD, part-proc: RES (no timeout)

I really don't care about those messages. Mainly because it's not my business to care about the system. I don't have access to the root privileges. So the solutions like this which requires changing and commenting some stuff in the /etc/rsyslog.conf will not be an option for me.

So, my question is, how can I suppress these messages for my own user without having the root privileges?

Rui F Ribeiro
  • 55,929
  • 26
  • 146
  • 227
sajad.k
  • 41
  • 1
  • 2
  • Best ting to do is a polite request to the system administrator to make the change to `etc/rsyslog.conf` with reason for the change being given that it is interfering with your productivity. – doneal24 May 06 '19 at 16:30

1 Answers1

5

The quick and dirty workaround is to comment out this line in /etc/rsyslog.conf:

# Everybody gets emergency messages
#*.emerg                    :omusrmsg:*

At least it worked for my CentOS 7 box.

To preserve these messages and make them easy to find, you could write them to a specific file. Something like this:

*.emerg                    /var/log/EMERG

Yes. That setting as a default is super intrusive. On a syslog server, any server in the environment throwing emerg messages can bork the console.

KurtB
  • 151
  • 3