Adding scanner to SPE 9.0 console generates an error.

Products

• Protection Engine for NAS
• Protection Engine for Cloud Services

Issue/Introduction

When trying to add a new scanner to the SPE 9.x console you get the following error.

Failed to add following server(s);

<IPAddress>.  Reason: No connection could be made because the target machine actively refused it

<IP Address>:8008

 

Environment

Windows 

SPE 9.x console

 

Cause

(a) The REST API service is listening on a port other than 8008

(b) The REST API service is not started

(c) The REST API service is started but the destination port is being blocked by a firewall or another entity on the network.

Resolution

(a) Review the "server.port" setting in the file application.properties to see what port the service is supposed to be listening on. The default port is 8008 but can be changed during installation or afterwards:

  Linux:  /opt/SYMCScan/RestAPI/

  Windows:  C:\Program Files\Symantec\Scan Engine\RestAPI

(b) Verify if the REST API Service is running:

  Linux:  /opt/SYMCScan/RestAPI/restapi.sh status

  Windows: Open the windows services panel and look for the service "Symantec Protection Engine REST API"  and verify if it is running.

 

  If the service is not started then try starting it.  If the service throws an error and will not start an explanation should be registered in the file SymantecProtectionEngineRESTAPIAbortLog.txt which should be found in the SPE home folder.

  If the service is started verify that it is indeed listening on the port designated in application.properties

  Linux:   netstat -an |grep 8008     You should see something similar to the following:

   

Windows: netstat -an | findstr 8008    You should see something similar to the following:

 

 

(c) If the service is started try opening a web browser and see if you are able to connect to the swagger-ui page which interfaces with the REST API service (if it is running)

       http://<<SPE Scanner IP>>:8008/swagger-ui.html

Reference: Symantec Protection Engine REST APIs

 
 If the page is inaccessible then check for a firewall or some other entity on the network that is preventing communication with the service.