You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2014/12/01 00:35:12 UTC

[jira] [Commented] (BIGTOP-1475) Zookeeper zkcli.sh doesn't run

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

Roman Shaposhnik commented on BIGTOP-1475:
------------------------------------------

[~sandersonshea] this makes sense. I've reopned the bug, but I don't think I'm going to have cycles to actually take care of fixing it. Thus, if you think you can help it'll be greatly appreciated!

Keep in mind, that zkcli.sh would constitute a private interface for solrctl. As such we don't need to make zkcli.sh work for a general purpose case, but just for solrctl. 

> Zookeeper zkcli.sh doesn't run
> ------------------------------
>
>                 Key: BIGTOP-1475
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1475
>             Project: Bigtop
>          Issue Type: Bug
>    Affects Versions: 0.8.0
>            Reporter: Andrew Kuchling
>            Assignee: Roman Shaposhnik
>
> /usr/lib/solr/bin/zkcli.sh doesn't run, probably because file paths have changed.  When installed on a CentOS machine, I get:
> [ec2-user@ip-X-Y-Z-W ~]$ /usr/lib/solr/bin/zkcli.sh      
> unzip:  cannot find or open /usr/lib/solr/bin/../../webapps/solr.war,
> /usr/lib/solr/bin/../../webapps/solr.war.zip or /usr/lib/solr/bin/../../webapps/solr.war.ZIP.
> Error: Could not find or load main class org.apache.solr.cloud.ZkCLI
> I managed to get zkcli.sh working for my purposes by commenting out the 
> invocation of unzip to unpack the .war file, and replaced the Java invocation with the following:
> PATH=$JAVA_HOME/bin:$PATH $JVM -Dlog4j.configuration=file:/etc/solr/conf.dist/log4j.properties -classpath "/usr/lib/solr/server/webapps/solr/WEB-INF/lib/*" org.apache.solr.cloud.ZkCLI ${1+"$@"}
> Note that I've changed both the path to log4j.properties and to the directory used with -classpath.



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