When deploying SPE server on any Linux distribution, you notice SymScan service is not running

Products

• Protection Engine for Cloud Services
• Protection Engine for NAS

Issue/Introduction

After deploying the Symantec Protection Engine (SPE) server on a Linux distribution, the installation completes successfully.

However, upon verification, only the REST API service is running. The SymScan service either fails to start or starts briefly and then stops automatically.

When checking the logs, you see the following:

SymantecProtectionEngineAbortLog.txt:

2025/05/14-21:22:08 300 XML files did not validate : Error Validating configuration.xml. Element '/configuration/QuarantineServerSettings/CloudStore/@relativepath' value: '/opt/SYMCScan/Quarantine' Path does not exists or does not have permission..
2025/05/14-21:22:08 0 Symantec Protection Engine is shutting down; logs may contain more information.

Environment

SPE 9.x on any known Linux distribution

Cause

The writing permission within the directory /opt/SYMCScan/Quarantine has not been setup properly.

Resolution

There is a few actions that needs to be done here:

1. Check if the server is able to download LiveUpdate definitions successfully
2. Check the list of permission on the server and make sure it matches the following:

drwxr-x--- 2    root(or admin of the server username) Quarantine

Finally, during the testing phase, once the permissions have been configured correctly, attempt to create a test file within the designated directory:

• • If the file is created successfully, it indicates that the permissions are correctly set, and the SPE service should start without issues.
  • If the file creation fails, this suggests a permission or mounting issue that must be addressed by the Unix team. In such cases, the directory may need to be properly mounted with the appropriate access rights as per the required configuration.