[
https://issues.apache.org/jira/browse/SOLR-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524107#comment-14524107
]
Timothy Potter commented on SOLR-7096:
--------------------------------------
Weird ... I'm not able to reproduce this now ... using SOLR_HOME=/var/solr/data
where /var/solr looks like:
{code}
ubuntu@ip-172-30-1-64:~$ ls -ltr /var/solr
total 20
drwxr-xr-x 2 solr solr 4096 May 1 21:54 data_dir
-rwxr-xr-x 1 solr solr 4556 May 1 21:57 solr.in.sh
-rw-r--r-- 1 solr solr 962 May 1 21:57 log4j.properties
lrwxrwxrwx 1 solr solr 8 May 1 22:00 data -> data_dir
drwxr-xr-x 2 solr solr 4096 May 1 22:01 logs
{code}
Maybe it was a different OS I saw this error on previously?
> The Solr service script doesn't like SOLR_HOME pointing to a path containing
> a symlink
> --------------------------------------------------------------------------------------
>
> Key: SOLR-7096
> URL: https://issues.apache.org/jira/browse/SOLR-7096
> Project: Solr
> Issue Type: Bug
> Affects Versions: 5.0
> Reporter: Timothy Potter
> Assignee: Timothy Potter
> Fix For: Trunk, 5.2
>
>
> While documenting the process to upgrade a SolrCloud cluster from 4.x to 5.0,
> I discovered that the init.d/solr script doesn't like the SOLR_HOME pointing
> to a path that contains a symlink. Work-around is to use an absolute path
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
