Discover Scans Stuck in Starting status

Products

• Data Loss Prevention Core Package
• Data Loss Prevention
• Data Loss Prevention API Detection
• Data Loss Prevention API Detection for Developer Apps Virtual Appliance
• Data Loss Prevention Cloud Detection Service
• Data Loss Prevention Cloud Detection Service for ICAP
• Data Loss Prevention Cloud Detection Service for REST
• Data Loss Prevention Cloud Package
• Data Loss Prevention Cloud Prevent for Microsoft Office 365
• Data Loss Prevention Cloud Service for Discovery/Connector
• Data Loss Prevention Cloud Service for Email
• Data Loss Prevention Cloud Storage
• Data Loss Prevention Data Access Governance
• Data Loss Prevention Discover Suite
• Data Loss Prevention Endpoint Discover
• Data Loss Prevention Endpoint Prevent
• Data Loss Prevention Enforce
• Data Loss Prevention Enterprise Suite
• Data Loss Prevention for Mobile
• Data Loss Prevention Form Recognition
• Data Loss Prevention Network Discover
• Data Loss Prevention Network Monitor
• Data Loss Prevention Network Monitor and Prevent for Email
• Data Loss Prevention Network Monitor and Prevent for Email and Web
• Data Loss Prevention Network Monitor and Prevent for Web
• Data Loss Prevention Network Prevent for Email
• Data Loss Prevention Network Prevent for Email Virtual Appliance
• Data Loss Prevention Network Prevent for Web Virtual Appliance
• Data Loss Prevention Network Protect
• Data Loss Prevention Oracle Standard Edition 2
• Data Loss Prevention Plus Suite
• Data Loss Prevention Sensitive Image Recognition

Issue/Introduction

Scans appear to be stuck in starting

Environment

DLP 16.x

Cause

The SymantecDLPDetector0.log shows the following: 

<<Date the Scan ran>> com.vontu.util.fsm.AsynchronousInputProcessor$ProcessInputsTask run
SEVERE: Failed to process state machine inputs
java.nio.file.InvalidPathException: Malformed input or input contains unmappable characters: /var/log/Symantec/DataLossPrevention/DetectionServer/16.1.00000/<ScanName_Log>.log.lck
    at sun.nio.fs.UnixPath.encode(UnixPath.java:147)
.......

Root issue, Malformed input or input contains unmappable characters

Resolution

It was found that the issue was caused by the discover target names having whitespace in them. Removing the whitespace from the discover target name allowed the scans to be started and process properly