Need help about an Avast error

Asked By 10 points N/A Posted on -
qa-featured

After updating my Fedora 14 database, I received an Avast error message which says the engine argument is invalid.

What should be the next thing to do?

Could I just use Avast itself to fix the problem or external help is needed?

I have inserted the image of the error message below for more understanding.

Please suggest on what to do.

Error:

An error occurred in avast! engine: Invalid argument

Deleted stale lock file '/root/.avast/lockfile-root'.

An error occurred in avast! engine: Invalid argument

SHARE
Best Answer by Thompson Locker
Best Answer
Best Answer
Answered By 10 points N/A #121256

Need help about an Avast error

qa-featured
I have got two approaches that I will like you to use and try to solve the problem, and they are as follows.
  • First, I will suggest that you redo a reinstallation of the avast antivirus. When you reinstall the antivirus, the old vps will be placed to the /var/lib/avast4/, and this might help solve the problem especially if you were using global vps update and the path that I just gave you is where the most recent vps is located.
  • The other thing that I will suggest that you do is run the following script,but that is in case the first approach does not end up successful.
sudo sysctl -w kernel.shmmax=128000000
kernel.shmmax = 128000000
 
Just go to the terminal and then the command line and copy the command above and paste it in it and execute it.
It should help fix the problem.
 
Regards
 
Thompson Locker
Answered By 0 points N/A #197629

Need help about an Avast error

qa-featured

Hello,

To fix this error, perhaps you should try these following steps:

1. Go to Terminal and enter this:

“sudo gedit /etc/sysctl.conf” (quotes not included)

2. This will open up the ‘sysctl.conf’ as a root. By this you would be able to create and save changes to the file.

3. After the ‘sysctl.conf’ is open. Add this following line at the end:

“kernel.shmmax = 128000000” (quotes not included)

4. When you’re done, try to reboot your computer.

I hope this will help you to fix your problem.

Regards,

Martine Paul

Related Questions