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

Sean Mackrory commented on BIGTOP-1736:
---------------------------------------

So I did some tinkering this morning and fortunately only found simple 
problems. tomcat-deployment.sh should be using /usr/lib/solr/server/webapps 
instead of /usr/lib/solr/webapps, and /etc/default/solr needed a couple of 
lines uncommented to point to ZK and HDFS, etc.. but it appear Puppet already 
takes care of this. I was able to create a Solr collection, etc. and start the 
service. I'm not sure exactly why things in /usr/lib/solr are structured the 
way they are so I'm going to do a bit more digging before I submit a patch to 
fix those things. Just updating here in case anyone is blocked on this with 
post 0.8.0 packages...

> Determine why SOLRCTL fails and add error messages to puppet.
> -------------------------------------------------------------
>
>                 Key: BIGTOP-1736
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1736
>             Project: Bigtop
>          Issue Type: Bug
>          Components: solr
>            Reporter: jay vyas
>
> I tried testing solr spin up in bigtop.  
> I noticed two things.
> 1) Zookeeper wasn't running when it attempted to do the solr setup/apply.  I 
> assume this is a bug, because, solrcloud reallly needs ZK from what i 
> understand.
> 2) There is a cryptic error message... the below puppet logs show it is 
> trying to run **init** on {{solrctl}} .  Its not immediately clear why it 
> fails.  lets make puppet report the error better. 
> {noformat} 
> ==> bigtop1: Error: /bin/bash -c '/usr/bin/solrctl debug-dump | grep -q 
> solr.xml || /usr/bin/solrctl init' returned 1 instead of one of [0]
> ==> bigtop1: Error: /Stage[main]/Solr::Server/Exec[solr init]/returns: change 
> from notrun to 0 failed: /bin/bash -c '/usr/bin/solrctl debug-dump | grep -q 
> sol
> r.xml || /usr/bin/solrctl init' returned 1 instead of one of [0]
> {noformat}



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

Reply via email to