[ 
https://issues.apache.org/jira/browse/SOLR-7921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14695398#comment-14695398
 ] 

Uwe Schindler commented on SOLR-7921:
-------------------------------------

Works on Windows (trunk branch):

{noformat}
C:\Users\Uwe Schindler\Projects\lucene\trunk-lusolr1\solr\bin>solr start -e 
techproducts
Creating Solr home directory C:\Users\Uwe 
Schindler\Projects\lucene\trunk-lusolr1\solr\example\techproducts\solr

Starting up Solr on port 8983 using command:
C:\Users\Uwe Schindler\Projects\lucene\trunk-lusolr1\solr\bin\solr.cmd start -p 
8983 -s "C:\Users\Uwe 
Schindler\Projects\lucene\trunk-lusolr1\solr\example\techproducts\solr"

Waiting up to 30 to see Solr running on port 8983
Started Solr server on port 8983. Happy searching!

Setup new core instance directory:
C:\Users\Uwe 
Schindler\Projects\lucene\trunk-lusolr1\solr\example\techproducts\solr\techproducts

Creating new core 'techproducts' using command:
http://localhost:8983/solr/admin/cores?action=CREATE&name=techproducts&instanceDir=techproducts

{
  "responseHeader":{
    "status":0,
    "QTime":1126},
  "core":"techproducts"}


Indexing tech product example docs from C:\Users\Uwe 
Schindler\Projects\lucene\trunk-lusolr1\solr\example\exampledocs
SimplePostTool version 5.0.0
Posting files to [base] url http://localhost:8983/solr/techproducts/update 
using content-type application/xml...
POSTing file gb18030-example.xml to [base]
POSTing file hd.xml to [base]
POSTing file ipod_other.xml to [base]
POSTing file ipod_video.xml to [base]
POSTing file manufacturers.xml to [base]
POSTing file mem.xml to [base]
POSTing file money.xml to [base]
POSTing file monitor.xml to [base]
POSTing file monitor2.xml to [base]
POSTing file mp500.xml to [base]
POSTing file sd500.xml to [base]
POSTing file solr.xml to [base]
POSTing file utf8-example.xml to [base]
POSTing file vidcard.xml to [base]
14 files indexed.
COMMITting Solr index changes to 
http://localhost:8983/solr/techproducts/update...
Time spent: 0:00:00.293

Solr techproducts example launched successfully. Direct your Web browser to 
http://localhost:8983/solr to visit the Solr Admin UI

C:\Users\Uwe Schindler\Projects\lucene\trunk-lusolr1\solr\bin>
{noformat}

> techproducts example broken; dir with spaces; Linux/Windows
> -----------------------------------------------------------
>
>                 Key: SOLR-7921
>                 URL: https://issues.apache.org/jira/browse/SOLR-7921
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 5.3
>            Reporter: Ishan Chattopadhyaya
>            Assignee: Timothy Potter
>         Attachments: SOLR-7921.patch, SOLR-7921.patch, SOLR-7921.patch, 
> SOLR-7921.patch, SOLR-7921.patch
>
>
> After [~thetaphi] reported that the error with spaces in dir names 
> (SOLR-7016) has reappeared in 5.3.0 RC1, I checked the same on Linux and 
> found it is broken. Here's the console log:
> {noformat}
> [ishan@localhost solr 530]$ bin/solr start -e techproducts
> Creating Solr home directory /home/ishan/solr 530/example/techproducts/solr
> Starting up Solr on port 8983 using command:
> bin/solr start -p 8983 -s "example/techproducts/solr"
> NOTE: Please install lsof as this script needs it to determine if Solr is 
> listening on port 8983.
> Started Solr server on port 8983 (pid=2404). Happy searching!
> Setup new core instance directory:
> /home/ishan/solr 530/example/techproducts/solr/techproducts
> Creating new core 'techproducts' using command:
> http://localhost:8983/solr/admin/cores?action=CREATE&name=techproducts&instanceDir=techproducts
> {
>   "responseHeader":{
>     "status":0,
>     "QTime":2671},
>   "core":"techproducts"}
> Indexing tech product example docs from /home/ishan/solr 
> 530/example/exampledocs
> Error: Unable to access jarfile /home/ishan/solr
> ERROR: Process exited with an error: 1 (Exit value: 1)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to