Syncplicity Support

Search our knowledgebase to get the help you need, today


After an upgrade, the DLP Connector service does not start

After upgrading the Data Loss Prevention(DLP) Connector appliance from 1.1.0 to 1.2.0, the connector does not work.


The DLP connector service does cannot start after an upgrade from version 1.1.0 to1.2.0.

The following error messages appear in the virtual appliance console.

Aug 08 16:15:22 systemd[1]: Starting Syncplicity DAS Connector Application...
-- Subject: Unit syncp-das.service has begun start-up
-- Defined-By: systemd
-- Support:
-- Unit syncp-das.service has begun starting up.
Aug 08 16:15:22 syncp-das-presetup[7008]: Starting Syncplicity DAS Connector Application (syncp-
Aug 08 16:15:30 systemd[1]: PID 7046 read from file /var/run/syncp-das/ does not exist.
Aug 08 16:15:30 systemd[1]: Failed to start Syncplicity DAS Connector Application.
-- Subject: Unit syncp-das.service has failed
-- Defined-By: systemd
-- Support:
-- Unit syncp-das.service has failed.
-- The result is failed.
Aug 08 16:15:30 systemd[1]: Unit syncp-das.service entered failed state.
Aug 08 16:15:30 systemd[1]: syncp-das.service failed.
Aug 08 16:15:32 systemd[1]: syncp-das.service holdoff time over, scheduling restart.

The following error messages appear in the log file in directory /var/log/syncp-das/ of the DLP appliance.

2019-08-08 16:19:34,369 [E] [app] - Configuration validation failed - Uninitialized keystore
2019-08-08 16:19:34,369 [E] [app] - Please check your configuration and restart the syncp-storage service.
2019-08-08 16:19:44,650 [E] [config] - Can't read password from null java.lang.NullPointerException: null
2019-08-08 16:19:44,674 [E] [config] - Can't load keystore /etc/syncp-das/dlpKeyStore DerInputStream.getLength(): lengthTag=109, too big.


Between version 1.1.0 and version 1.2.0 of the DLP connector, the names of the configuration directories were changed and several properties were moved between the configuration files as follows.

Renamed configuration files

Configuration file\DLP versionDLP 1.1.0DLP 1.2.0
Java configuration/etc/syncp-dlp/dlp.yml/etc/syncp-das/syncp-das.yml
Scala configuration/etc/syncp-dlp/syncp-dlp.conf/etc/syncp-das/syncp-das.conf

Renamed and moved properties

Property in DLP 1.1.0 /etc/syncp-dlp/dlp.ymlProperty in DLP 1.2.0 /etc/syncp-das/syncp-das.conf



As a result, the DLP connector service is unable to start because the configuration validation fails and the authorization cannot complete. 


  1. Move the values of the following properties from the /etc/syncp-dlp/dlp.yml file on DLP 1.1.0 to the /etc/syncp-das/syncp-das.conf file in DLP 1.2.0




  2. Add the following property in file /etc/syncp-das/syncp-das.conf. JKS

Powered by Zendesk