Remove Emergency Messages to all users

This selector-action states "Emergency messages often go to all users currently online to notify them that something strange is happening with the system. To specify this wall(1)-feature use an ":omusrmsg:*"." Comment this line out.

Here's are the steps:

Stop rsyslog service - Due to your console being flooded by messages, you will have a hard time executing commands so I suggest you stop the service first.
```
service rsyslog stop
```
Edit rsyslog configuration file /etc/rsyslog.conf
```
vim /etc/rsyslog.conf
```

Find the line:

*.emerg                                                 :omusrmsg:*

Comment out the whole line and save the file

Start the rsyslog service again
```
service rsyslog start
```

Check and fix configuration file (if there's any)

If the above steps still didn't resolve the issue, maybe there's some other problems from the configuration file that's causing it to ignore the configurations set.

You can try following these steps to find out and fix the configuration issue:

Stop rsyslog service - Due to your console being flooded by messages, you will have a hard time executing commands so I suggest you stop the service first.
```
service rsyslog stop
```

Check rsyslog status

service rsyslog status

It should return something like this:

Redirecting to /bin/systemctl status rsyslog.service
● rsyslog.service - System Logging Service
   Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Thu 2020-04-23 11:52:15 +08; 7s ago
     Docs: man:rsyslogd(8)
           http://www.rsyslog.com/doc/
  Process: 22063 ExecStart=/usr/sbin/rsyslogd -n $SYSLOGD_OPTIONS (code=exited, status=0/SUCCESS)
 Main PID: 22063 (code=exited, status=0/SUCCESS)

Apr 23 11:50:23 site.com systemd[1]: Starting System Logging Service...
Apr 23 11:50:23 site.com rsyslogd[22063]:  [origin software="rsyslogd" swVersion="8.24.0-34.el7" x-pid="22063" x-info="http://www.rsyslog.com"] start
Apr 23 11:50:23 site.com rsyslogd[22063]: action '*' treated as ':omusrmsg:*' - please use ':omusrmsg:*' syntax instead, '*' will not be supported in the futu...m/e/2184 ]
Apr 23 11:50:23 site.com systemd[1]: Started System Logging Service.
Apr 23 11:50:23 site.com rsyslogd[22063]: error during parsing file /etc/rsyslog.conf, on or before line 95: warnings occured in file '/etc/rsyslog.conf' arou...m/e/2207 ]
Apr 23 11:50:23 site.com rsyslogd[22063]: invalid character in selector line - ';template' expected [v8.24.0-34.el7]
Apr 23 11:50:23 site.com rsyslogd[22063]: error during parsing file /etc/rsyslog.conf, on or before line 95: errors occured in file '/etc/rsyslog.conf' around...m/e/2207 ]
Apr 23 11:52:15 site.com systemd[1]: Stopping System Logging Service...
Apr 23 11:52:15 site.com rsyslogd[22063]:  [origin software="rsyslogd" swVersion="8.24.0-34.el7" x-pid="22063" x-info="http://www.rsyslog.com"] exiting on signal 15.
Apr 23 11:52:15 site.com systemd[1]: Stopped System Logging Service.
Hint: Some lines were ellipsized, use -l to show in full.

Analyze the status messages to see which line to fix. On this case, I have an error on line 95 of /etc/rsyslog.conf.
Edit and fix the configuration file according to the status message.
Start the service again
```
service rsyslog start
```