I have installed clamav and I want to to update the files that it uses to identify viruses:

$ sudo freshclam

ERROR: /var/log/clamav/freshclam.log is locked by another process
ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log).

What should I do with this error?


$ sudo lsof /var/log/clamav/freshclam.log

freshclam 866 clamav    3wW  REG  259,1   100134 10486045 /var/log/clamav/freshclam.log
| improve this question | | | | |
  • What is the output of sudo lsof /var/log/clamav/freshclam.log? – Ravexina Apr 26 '17 at 20:14
  • 1
    So no need to run it, it's automatically has been started. – Ravexina Apr 26 '17 at 20:16
  • @Ravexina no need to run what? – laukok Apr 26 '17 at 20:17
  • 1
    sudo freshclam – Ravexina Apr 26 '17 at 20:18
  • 1
    I guess it should be the log of update process, so no harm ... it's just adds what is happening to that file. – Ravexina Apr 26 '17 at 20:26

Short answer:

You don't have to run it manually because it has been run automatically and is running in the background, that's why you receive that message.

If you want to stop the daemon and run it manually:

sudo systemctl stop clamav-freshclam.service

run it manually:

sudo freshclam

What is happening and how to handle it?

Every time when you encounter into a similar situations, errors like file x has been locked or Another process is using this file : /path/to/x you can use the lsof command to find out which process is using that file, in your case if you run:

sudo lsof /var/log/clamav/freshclam.log

You should get an output like:

abc       126   user   3wW  REG  259,1  100          1048 /var/log/clamav/freshclam.log

The abc is the name of process which is using that file, in your case it's: freshclam.

That means freshclam which you want to run has been already ran by clamav daemons.

you can use less /var/log/clamav/freshclam.log or similar commands to see what's going on.

So you don't have to run it manually anymore, it's a process to avoid any conflict and having multiple instance of a same process doing same thing at the same time.

If you want to make it stop and run it manually, then send a SIGTERM to its process, that gives the process a chance to finish its job and close itself cleanly, something like:

sudo pkill -15 -x freshclam
  • in this case sudo may be necessary.
  • 15: SIGTERM is the default

Then run it manually:

sudo freshclam

However in this case you can use:

sudo systemctl stop clamav-freshclam.service

to stop the daemon.

| improve this answer | | | | |
  • Will the daemon start up again after a reboot? If so, do you know the best way to prevent that? Thanks. – Joshua Pinter Oct 1 '19 at 16:44
  • sudo systemctl disable clamav-freshclam.service might be the way. – Ravexina Oct 1 '19 at 17:50
  • Thanks, I'll try that out if it pops back up again. – Joshua Pinter Oct 1 '19 at 19:01
sudo /etc/init.d/clamav-freshclam stop
sudo freshclam
sudo /etc/init.d/clamav-freshclam start
| improve this answer | | | | |

This might be another option for this...

sudo service clamav-freshclam stop
sudo freshclam
sudo service clamav-freshclam start

Hope this helps...

| improve this answer | | | | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.