Operational Defect Database
BugZero found this defect 2014 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
WatchGuard Technologies | kA10H000000g3b9SAA
Signature updates can fail on FireboxV and Firebox Cloud instances with less than 4GB RAM
Last update date:
11/13/2018
Affected products:
FireboxV
Firebox Cloud
Affected releases:
All
Fireware
12.x
12.0.x
12.1.x
12.1
12.1.1
12.1.3
12.2.x
Fixed releases:
All
Description:
Issue
Note Even if your FireboxV or Firebox Cloud instance has less than 4GB of RAM, this issue may not be the cause of signature update problems. Make sure your Firebox is correctly configured for signature updates and can correctly resolve DNS. To learn more, see Configure the Gateway AV Update Server. Gateway AV signature updates can fail to update on FireboxV and Firebox Cloud instances with less than 4GB of RAM. IPS, Botnet Detection, and Application Control signature updates are not affected. When you deploy FireboxV or Firebox Cloud with less than 4GB of RAM, Gateway AV will create an on disk cache. When this cache is created, there is not enough space for Gateway AV to download the new Gateway AV signature set. When the system has 4GB or more RAM, Gateway AV will unpack and scan files in memory and does not use a disk cache. Systems initially deployed with less than 4GB of memory and later updated can also be affected. If Gateway AV logging is set to debug, the sigd process will report a SHASUM value mismatch error for some of the update files. sigd sigd_download_file_cb: downloading file='emalware.i18' from url='http://cdn.watchguard.com/svcs2/svcactive/payload/bitdefender/201810300845/av_plugins_x86_64_full/emalware.i18' Debugsigd download_file_simple: file='/sigs/tmp/emalware.i18' shasum value mismatch Debugsigd sigd_download_file_cb: fail to download file='emalware.i18' from url='http://cdn.watchguard.com/svcs2/svcactive/payload/bitdefender/201810300845/av_plugins_x86_64_full/emalware.i18' Debugsigd fail to download AV plugin file Debugsigd URL string for update status report: https://services.watchguard.com/test/ServiceJoined/ServiceJoined.asmx/RegisterResultJoined Debug
Workaround/Solution
This issue does not occur if you deploy the instance with 4GB of RAM or more. The RAM must be 4GB before the first time the FIreboxV or Firebox Cloud instance is started
