How to disable kernel messages (dmesg) Flooding on the console<\/p>\n
Edit the syslog config file\u00a0\/etc\/rsyslog.conf<\/b> and do the following modification.<\/p>\n
#kern.* \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \/dev\/console<\/b>
\nUnhide and Modify the above line as below
\nkern.* \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \/dev\/null<\/b><\/p>\n
Restart the rsyslog service
\n#service rsyslog restart<\/b><\/p>\nMethod. 2<\/u><\/h3>\n
If the above method is not solving the problem, then try changing the dmesg log level.<\/p>\n
To see the current log level
\n#sysctl kernel.printk<\/b>
\n4<\/b>\u00a0\u00a0 \u00a0 \u00a0 4 \u00a0 \u00a0 \u00a0 1 \u00a0 \u00a0 \u00a0 7<\/p>\n
To Change the log level<\/p>\n
#dmesg -n 1<\/b><\/p>\n 0 – emerg – system is unusable How to disable kernel messages (dmesg) Flooding on the console Method. 1 Edit the syslog config file\u00a0\/etc\/rsyslog.conf and do the following modification. #kern.* \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0… Read more »<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[127],"tags":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/posts\/63"}],"collection":[{"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/comments?post=63"}],"version-history":[{"count":4,"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/posts\/63\/revisions"}],"predecessor-version":[{"id":654,"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/posts\/63\/revisions\/654"}],"wp:attachment":[{"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/media?parent=63"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/categories?post=63"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/tags?post=63"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n1\u00a0<\/b>\u00a0 \u00a0 \u00a0 4 \u00a0 \u00a0 \u00a0 1 \u00a0 \u00a0 \u00a0 7To fix at each reboot, add the following line to \/etc\/rc.local<\/b> file
\ndmesg -n 1<\/b><\/div>\n<\/div>\nSupported log levels (priorities):<\/u><\/b><\/h4>\n
\n1 – alert – action must be taken immediately<\/b>
\n2 – \u00a0crit – critical conditions
\n3 – \u00a0 \u00a0 err – error conditions
\n4 – \u00a0 \u00a0warn – warning conditions
\n5 – \u00a0notice – normal but significant condition
\n6 – \u00a0 \u00a0info – informational
\n7 – \u00a0 debug – debug-level messages<\/p>\n","protected":false},"excerpt":{"rendered":"