[Lovecaroline275]

wow,but i am sorry that i can not help you.

[crowarth]

Hi Neil,

Just an FYI - I had to do this change on a VM despite the customer support email saying it would be corrected on all machines deployed since the correction was made.

[crowarth]

Hello

Maybe for the formatting is wrong, the steps should be:
service rsyslog stop
cp /etc/rsyslog.conf /etc/rsyslog.conf.backup
sed -i -e 's/^\$ModLoad imklog/#\$ModLoad imklog/g' /etc/rsyslog.conf
service rsyslog start

Neil

That's done the trick, thanks

[Neil]

Hello

Maybe for the formatting is wrong, the steps should be:
service rsyslog stop
cp /etc/rsyslog.conf /etc/rsyslog.conf.backup
sed -i -e 's/^\$ModLoad imklog/#\$ModLoad imklog/g' /etc/rsyslog.conf
service rsyslog start

Neil

[crowarth]

So I got this email, like many probably did. Except when you run the command they've provided (at least on Ubuntu) I get this:

sudo cp /etc/rsyslog.conf /etc/rsyslog.conf.backup sed -i -e 's/^\$ModLoad imklog/#\$ModLoad imklog/g' /etc/rsyslog.conf
cp: invalid option -- 'e'
Try 'cp --help' for more information.

The email:

Dear Customer,

Many of our customers have informed us that Rsyslog is excessively consuming CPU.

Our teams have looked into it and it seems that the issue is affecting Ubuntu and Debian on VPS Classic.

We have corrected the distributions, and the issue will no longer occur for all new orders or reinstallations.
Below is a bug fix so that you can fix the issue yourself on your VPS:

service rsyslog stop
cp /etc/rsyslog.conf /etc/rsyslog.conf.backup sed -i -e 's/^\$ModLoad imklog/#\$ModLoad imklog/g' /etc/rsyslog.conf service rsyslog start

You do not need to reboot your VPS; the update will be effective immediately.

Do not hesitate to contact us if you have any queries.

We always welcome your feedback.