Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleClick to see detailled instructions ...

Symptom:

ClamAV is not running and cannot be started anymore. The following warning is shown: Can't connect to clamd through /var/run/clamav/clamd-socket: No such file or directory

Cause:

This occurs if the ClamAV virus definitions were not updated successfully during an automatic update.

Solution:

Follow these steps to repair the definitions:

  •  Log in on your Cryptshare appliance via SSH
  •  

    Run the following commands:

    Code Block
    languagebash
    themeEmacs
    systemctl stop clamd.service
    rm /var/lib/clamav/daily.*
    rm /var/lib/clamav/main.*
    freshclam
    systemctl start clamd.service


  •  

    Check the ClamAV daemon status

    Code Block
    languagebash
    themeEmacs
    systemctl status clamd.service



4. (optional) Increase timeout of clamd.service

Expand
titleClick to see detailled instructions ...

Symptom:

The clamd service cannot be started

Cause:

This occurs if the clamd service runs into a timeout

Solution:

Follow these steps to increase the timeout to 180 seconds:


Insert the line "TimeoutSec=180" in the File "/usr/lib/systemd/system/clamd.service" beneath the [Service] tag:


Image Added


WinSCP can also be used to edit the file: (https://winscp.net/eng/download.php)

Image Added