Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| antivirus [2018_07_26 13:07] – jim | antivirus [2025_07_29 22:34] (current) – [Checking ClamAV Service Logs] steven | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| # Virus Scanning Protection | # Virus Scanning Protection | ||
| + | Last updated: Jul 29, 2025 | ||
| - | The Enterprise File Fabric | + | <WRAP center round info 100%> |
| + | **NOTE:** This guide is for Access Anywhere 2402.1 and above. | ||
| + | </ | ||
| + | |||
| + | Access Anywhere | ||
| {{:: | {{:: | ||
| Line 9: | Line 14: | ||
| File solution-brief.pdf uploaded to My Cloud files/ | File solution-brief.pdf uploaded to My Cloud files/ | ||
| - | ClamAV is the officially supported virus scanner available for use with the File Fabric. ClamAV is a high performance multi-threaded daemon supporting many file formats including file and archive unpacking. | + | ClamAV is the officially supported virus scanner available for use with Access Anywhere. ClamAV is a high performance multi-threaded daemon supporting many file formats including file and archive unpacking. |
| - | In High Availability environments each appliance will run a local ClamAV service | + | In High Availability environments each appliance |
| - | Works with: | + | <WRAP center round info 100%> |
| + | Files larger than 1.5GB will be uploaded without being scanned, and only the first 1.5GB of files that expand during scanning to more than 1.5GB will be scanned. | ||
| + | </ | ||
| - | * Enterprise Appliance (since 1712.00) | ||
| - | ## Configuration | + | ## Service |
| - | The virus scanning of uploads is a configuration option for the organization. The option is available when added to the user package. | + | ClamAV must first be enabled and configured on each web node. |
| + | ## 1. Start and Enable ClamAV | ||
| + | |||
| + | SSH to the appliance as user smeconfiguser, | ||
| + | |||
| + | su - | ||
| + | |||
| + | Start the Antivirus container. | ||
| + | |||
| + | cd / | ||
| + | docker compose up -d | ||
| + | |||
| + | Next verify that it is running and enabled: | ||
| + | **NOTE:** It might take 60+ seconds for the health to change from **starting** to **healthy** | ||
| + | |||
| + | # docker compose ps | ||
| + | NAME IMAGE COMMAND | ||
| + | clamav | ||
| + | |||
| + | |||
| + | ## 2. Verify Appliance Integration with ClamAV | ||
| + | |||
| + | The appliance configuration file can be found at: | ||
| + | |||
| + | / | ||
| + | |||
| + | Verify that the settings below are configured as shown: | ||
| + | |||
| + | var $enableantivirus = 1; | ||
| + | var $clamavsocketpath = '/ | ||
| + | |||
| + | ## Enabling ClamAV for Organizations | ||
| + | The virus scanning of uploads is a configuration option for organizations. The option is available when added to the user package. | ||
| ## 1. Adding the ClamAV Option to a User Package | ## 1. Adding the ClamAV Option to a User Package | ||
| Line 34: | Line 72: | ||
| ## Troubleshooting | ## Troubleshooting | ||
| + | ### Checking ClamAV Service Logs | ||
| + | Once started the ClamAV service will generate log data. | ||
| - | ### Checking that the ClamAV | + | To review |
| - | The ClamAV service is preinstalled on the appliance and is enabled and running by default. | + | |
| - | To verify ClamAV has been running successfully check the last entries in the log: | + | docker logs -f clamav |
| - | $ tail / | ||
| - | ... | ||
| - | Fri Feb 2 00:34:21 2018 -> SelfCheck: Database status OK | ||
| - | |||
| - | Use systemctl to verify ClamAV is both enabled (that is, will startup on boot), and running: | ||
| - | |||
| - | $ systemctl status clamd@scan | ||
| - | Loaded: loaded (/ | ||
| - | Active: active (running) | ||
| - | |||
| - | If needed, to stop, start, enable, disable or restart run systemctl as root: | ||
| - | |||
| - | systemctl restart clamd@scan | ||
| #### Configuration | #### Configuration | ||
| Line 58: | Line 84: | ||
| ClamAV configuration settings can be found at: | ClamAV configuration settings can be found at: | ||
| - | /etc/clamd.d/scan.conf | + | /var/www/smestorage/ |
| ### Checking Virus Signatures are Fresh | ### Checking Virus Signatures are Fresh | ||
| Line 64: | Line 90: | ||
| The Freshclam application updates the antivirus signature database. It is preinstalled on the appliance and by default is scheduled to run once an hour. | The Freshclam application updates the antivirus signature database. It is preinstalled on the appliance and by default is scheduled to run once an hour. | ||
| - | To verify Freshclam has been running successfully check the last entries in the log: | + | To verify Freshclam has been running successfully check the definition version and date |
| - | | + | |
| + | ClamAV 1.4.3/27713/Mon Jul 28 08:36:30 2025 | ||
| - | To verify the connection to the online database (and update definitions) run as root: | ||
| - | freshclam | + | In the output above ClamAV |
| - | + | ||
| - | By default virus definitions are updated once an hour (see / | + | |
| - | + | ||
| - | 47 * * | + | |
| - | + | ||
| - | #### Configuration | + | |
| - | + | ||
| - | Freshclam can be configured through | + | |
| - | + | ||
| - | / | + | |
| - | + | ||
| - | ### Checking Appliance Integration with ClamAV | + | |
| - | + | ||
| - | This configuration file can be found at: | + | |
| - | + | ||
| - | / | + | |
| - | + | ||
| - | Make sure the following settings are present: | + | |
| - | + | ||
| - | var $enableantivirus = 1; | + | |
| - | var $clamavsocketpath = '/ | + | |
| ### Error: Socket Operation Failed | ### Error: Socket Operation Failed | ||