[ 
https://issues.apache.org/jira/browse/SOLR-17598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christos Malliaridis updated SOLR-17598:
----------------------------------------
    Description: 
On Windows, when setting the {{SOLR_LOGS_DIR}} in the environment variables, it 
prevents Solr from starting. Additionally, if the variable contains a space, 
trying to stop a running Solr service with {{bin\solr.cmd stop --all}} fails.

I have also observed situations where {{SOLR_LOGS_DIR}} in environment 
variables is simply ignored, but I am not sure if this is still preproducable.
h3. Steps to reproduce

1. Set the environment variable {{SOLR_LOGS_DIR}} to an absolute path that does 
or does not exist
2. ensure that in your current terminal the envrionment variable you set is 
present via "echo %SOLR_LOGS_DIR%"
3. Launch Solr with {{bin\solr.cmd start}}
h3. Expected Behavior

Setting the environment variable is supported and should not make a difference 
with setting the value in solr.in.cmd
h3. Actual Behavior

The environment variable is not supported.
h3. Workaround

Setting {{SOLR_LOGS_DIR}} via the {{solr.in.cmd}} file (which overrides the 
environment variable) works and avoids the issues. Spaces are also supported 
this way.
h3. Additional Information

This behavior was tested for the {{{}SOLR_LOGS_DIR{}}}, but it is not 
guaranteed that other environment variables work. This may affect all 
environment variables on Windows.

  was:
h3. Description

On Windows, when setting the {{SOLR_LOGS_DIR}} in the environment variables, it 
prevents Solr from starting. Additionally, if the variable contains a space, 
trying to stop a running Solr service with {{bin\solr.cmd stop --all}} fails.

I have also observed situations where {{SOLR_LOGS_DIR}} in environment 
variables is simply ignored, but I am not sure if this is still preproducable.

h3. Steps to reproduce

1. Set the environment variable {{SOLR_LOGS_DIR}} to an absolute path that does 
or does not exist
2. ensure that in your current terminal the envrionment variable you set is 
present via "echo %SOLR_LOGS_DIR%"
3. Launch Solr with {{bin\solr.cmd start}}

h3. Expected Behavior

Setting the environment variable is supported and should not make a difference 
with setting the value in solr.in.cmd

h3. Actual Behavior

The environment variable is not supported.

h3. Workaround

Setting {{SOLR_LOGS_DIR}} via the {{solr.in.cmd}} file (which overrides the 
environment variable) works and avoids the issues. Spaces are also supported 
this way.

h3. Workaround

This behavior was tested for the {{SOLR_LOGS_DIR}}, but it is not guaranteed 
that other environment variables work. This may affect all environment 
variables on Windows.


> Windows Script logic that handles SOLR_LOGS_DIR is faulty
> ---------------------------------------------------------
>
>                 Key: SOLR-17598
>                 URL: https://issues.apache.org/jira/browse/SOLR-17598
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: cli
>    Affects Versions: 9x, 9.8
>         Environment: Windows 11
>            Reporter: Christos Malliaridis
>            Priority: Major
>
> On Windows, when setting the {{SOLR_LOGS_DIR}} in the environment variables, 
> it prevents Solr from starting. Additionally, if the variable contains a 
> space, trying to stop a running Solr service with {{bin\solr.cmd stop --all}} 
> fails.
> I have also observed situations where {{SOLR_LOGS_DIR}} in environment 
> variables is simply ignored, but I am not sure if this is still preproducable.
> h3. Steps to reproduce
> 1. Set the environment variable {{SOLR_LOGS_DIR}} to an absolute path that 
> does or does not exist
> 2. ensure that in your current terminal the envrionment variable you set is 
> present via "echo %SOLR_LOGS_DIR%"
> 3. Launch Solr with {{bin\solr.cmd start}}
> h3. Expected Behavior
> Setting the environment variable is supported and should not make a 
> difference with setting the value in solr.in.cmd
> h3. Actual Behavior
> The environment variable is not supported.
> h3. Workaround
> Setting {{SOLR_LOGS_DIR}} via the {{solr.in.cmd}} file (which overrides the 
> environment variable) works and avoids the issues. Spaces are also supported 
> this way.
> h3. Additional Information
> This behavior was tested for the {{{}SOLR_LOGS_DIR{}}}, but it is not 
> guaranteed that other environment variables work. This may affect all 
> environment variables on Windows.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to