Issue with path.repo while starting Elasticsearch as a service

Describe the feature : Elasticsearch service doesn't get started if path.repo contains a repository path that needs credentials.

Elasticsearch version ( bin/elasticsearch --version ): 6.5.4

Plugins installed : [Search guard]

JVM version ( java -version ): 1.8

OS version ( uname -a if on a Unix-like system): Windows 10, Windows Server 2012 R2

Description of the problem including expected versus actual behavior :

When we give a repository path which needs credentials in path.repo & we connect to that repository using net use command, elasticsearch doesn't start as a service. However, elasticsearch.bat works perfectly fine.

Fails with error message like this: "Exception java.lang.IllegalStateException: Unable to access 'path.repo', Caused by: java.nio.file.FileSystemException, Unable to determine if root directory exists "

Steps to reproduce :

  1. Open elasticsearch.yml & add a repository path to path.repo. The repository path should be asking for credentials (may be give cross domain machine's share)
  2. Now execute this command to connect to the share: "net use '\machine-name\share1'"
  3. Once you are connected, start Elasticsearch as a service. Fails with above mentioned exception. Try starting the same using "elasticsearch.bat", it works perfectly.

Provide logs (if relevant) :

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.