Symantec Protection Engine NOT getting updated virusdefs

Products

• Protection Engine for NAS

Issue/Introduction

Symantec Protection Engine (SPE) does not appear to update the date of its virus definitions, or during initial rollout, admins seek steps to prove that SPE attempts to download and apply virus definitions on demand.

 

 

Environment

Release : 8.2.2-9.0.1

Component :

Resolution

 

1. In cmd(Windows) or bash(Linux), navigate to the installation folder of SPE
2. Create the file LuNowFlag
3. Check the directory listing to confirm the LuNowFlag file disappears
4. After LUNowFlag disappears, check the report.xml to confirm whether definitions updated
5. If definitions date did not change, check lux.log for error
   
   
   

 

To test LU download of definitions on Windows

1. To navigate to default location of installation folder of SPE, type:
   cd "C:\Program Files\Symantec\Scan Engine"
   
   
2. To create the file LUNowFlag, type:
   echo "" >LUNowFlag
   
   
3. To confirm the LUNowFlag file disappears, wait two to five minutes, then type:
   dir LUNowFlag
   
   
4. To check report.xml for definitions date, type:
   find "AntiVirus" report.xml
   
   
5. To check lux.log for error, type:
   type "C:\Program Files\Symantec\Scan Engine\Definitions\Stargate\logs\lux.log"

 

To test download of definitions on Linux

1. To navigate to default location of installation folder of SPE, type:
   cd  /opt/SYMCScan/bin
   
   
2. To create the file LUNowFlag, type:
   touch LUNowFlag
   
   
3. To confirm the LUNowFlag file disappears, wait two to five minutes, then type:
   ls LUNowFlag
   
   
4. To check report.xml for definitions date, type:
   grep "AntiVirus" report.xml
   
   
5. To check lux.log for error, type:
   less /opt/SYMCScan/bin/definitions/Stargate/logs/lux.log
   
      Within less, press G to move to the end of the file.
      Use up and down row keys to scroll through the file as desired.
      When done, press q to quit.

 

 

Additional Information

For more information on a specific error code in the lux.log, see:

https://knowledge.broadcom.com/external/article?articleId=181764