[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=15623355#comment-15623355
]
Jan Høydahl commented on SOLR-8384:
---
I can agree with you. Looks like the {{-d}} option is designed to work even if
the solr/server dir is missing completely, which is not the case for neither
bin/solr or bin/solr.cmd currently. bin/solr uses DEFAULT_SERVER_DIR for the
run_tool stuff.
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[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=15622416#comment-15622416 ] Jeremy Anderson commented on SOLR-8384: --- It's been a while since I was messing with this. Essentially I believe I had all the binaries in a different path and was starting SOLR.cmd with the -d command option to direct it to that directory. (I may have been doing this so that I could package SOLR into a different Jetty instance for a prod style deploy) SOLR starts up fine, however the secondary checks performed assume those binaries reside in the Default path which they no longer did. By changing them to use the proper new path of SOLR_SERVER_DIR (set by the -d option if I recall) everything ran fine and as expected. Take a look at :set_server_dir which is what is called when starting with the -d option. Here is where SOLR_SERVER_DIR is set. It may be best to also change the value of DEFAULT_SERVER_DIR here as well. > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[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=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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
