[
https://issues.apache.org/jira/browse/SOLR-9745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954100#comment-15954100
]
Mikhail Khludnev commented on SOLR-9745:
----------------------------------------
Checking the patch. It make sense:
{quote}
ERROR: Failed to start Solr using command:
C:\cygwin64\home\mike\lucene-solr\solr\bin\solr.cmd start -p 8983 -s
"C:\cygwin64\home\mike\lucene-solr\solr\example\techproducts\solr" Exception :
org.apache.commons.exec.ExecuteException: Execution failed (Exit value:
-559038737. Caused by java.io.IOException: Cannot run program
"C:\cygwin64\home\mike\lucene-solr\solr\bin\solr.cmd" (in directory "."):
CreateProcess error=5, Отказано в доступе)
{quote}
> SolrCLI swallows errors from solr.cmd
> -------------------------------------
>
> Key: SOLR-9745
> URL: https://issues.apache.org/jira/browse/SOLR-9745
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Server
> Affects Versions: 6.3, master (7.0)
> Reporter: Mikhail Khludnev
> Assignee: Mikhail Khludnev
> Labels: newbie, newdev
> Attachments: SOLR-9745.patch, SOLR-9745.patch
>
>
> It occurs on mad scenario in LUCENE-7534:
> * solr.cmd weren't granted +x (it happens under cygwin, yes)
> * coolhacker worked it around with cmd /C solr.cmd start -e ..
> * but when SolrCLI runs solr instances with the same solr.cmd, it just
> silently fails
> I think we can just pass ExecuteResultHandler which will dump exception to
> console.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
