In case files are removed from transfers, or warnings concerning ClamAV are shown in the Cryptshare logs, please follow the steps below.
1. Checking if minimum system requirements are met
Please check if your Appliance meets the following requirements:
2. Restarting ClamAV service
Several users report that after the file upload has finished, the following message is shown:
This behaviour may be caused by an unresponsive ClamAV daemon which fails to process incoming files.
The following warnings may be shown in the logs:
Follow these steps:
- Log in as root on your appliance
Execute the following commands:
- Perform a test transfer. The message should no longer appear. If it does, apply Solution 3 below.
3. Resetting ClamAV virus definitions
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
This occurs if the ClamAV virus definitions were not updated successfully during an automatic update.
Follow these steps to repair the definitions:
- Log in on your Cryptshare appliance via SSH
Run the following commands:
Check the ClamAV daemon status
4. (optional) Increase timeout of clamd.service
The clamd service cannot be started
This occurs if the clamd service runs into a timeout
Follow these steps to increase the timeout to 900 seconds:
Insert the line TimeoutSec=900 in the File /usr/lib/systemd/system/clamd.service beneath the [Service] tag:
WinSCP can also be used to edit the file: (https://winscp.net/eng/download.php)