You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jan Høydahl (JIRA)" <ji...@apache.org> on 2016/10/31 13:51:58 UTC
[jira] [Commented] (SOLR-8384) Windows Start Script when Changing
SOLR_SERVER_DIR via -d option
[ https://issues.apache.org/jira/browse/SOLR-8384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15622201#comment-15622201 ]
Jan Høydahl commented on SOLR-8384:
-----------------------------------
As I can see that command is correct, it only uses DEFAULT_SERVER_DIR to find the SolrCLI tool, which is then looking for a running Solr over HTTP.
Please detail exactly what caused you problems? Did you delete the solr/server directory so the binary could not be found?
> Windows Start Script when Changing SOLR_SERVER_DIR via -d option
> ----------------------------------------------------------------
>
> Key: SOLR-8384
> URL: https://issues.apache.org/jira/browse/SOLR-8384
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
> Affects Versions: 5.3.1
> Environment: Windows
> Reporter: Jeremy Anderson
> Priority: Trivial
>
> bin\solr.cmd Requires change of environment variables used in the " REM now wait to see Solr come online ..." command. Currently this call uses DEFAULT_SERVER_DIR which is no longer correct when starting SOLR with a different server directory using the -d command option.
> Replace DEFAULT_SERVER_DIR with SOLR_SERVER_DIR so that the proper libraries are able to be found when checking that SOLR started.
> There may be other uses in the script where this issue is present when starting SOLR from a different directory other than 'server'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org