Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 52367F4BA for ; Thu, 28 Mar 2013 20:53:18 +0000 (UTC) Received: (qmail 44934 invoked by uid 500); 28 Mar 2013 20:53:18 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 44916 invoked by uid 500); 28 Mar 2013 20:53:18 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 44907 invoked by uid 99); 28 Mar 2013 20:53:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Mar 2013 20:53:18 +0000 Date: Thu, 28 Mar 2013 20:53:18 +0000 (UTC) From: "Eugene (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CASSANDRA-3512) Getting Started instructions don't work in README.txt - wrong version of jamm, wrong path MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616636#comment-13616636 ] Eugene edited comment on CASSANDRA-3512 at 3/28/13 8:53 PM: ------------------------------------------------------------ I had this error under CentOS 5 using the RPM packages provided by DataStax. The issue for me was '/etc/cassandra/conf/cassandra-env.sh' called jamm using the following: {noformat} cassandra-env.sh: JVM_OPTS="$JVM_OPTS -javaagent:$CASSANDRA_HOME/lib/jamm-0.2.5.jar" {noformat} However, $CASSANDRA_HOME isn't set anywhere. I fixed it by adding the following to '/usr/share/cassandra/cassandra.in.sh': {noformat} CASSANDRA_HOME=/usr/share/cassandra {noformat} was (Author: aechttpd): I had this error under CentOS 5 using the RPM packages provided by DataStax. The issue for me was '/etc/cassandra/conf/cassandra-env.sh' called jamm using the following: {noformat} cassandra-env.sh: JVM_OPTS="$JVM_OPTS -javaagent:$CASSANDRA_HOME/lib/jamm-0.2.5.jar" {noformat} However, $CASSANDRA_HOME isn't set anywhere. I fixed it by adding the following to '/usr/share/cassandra/cassandra.in.sh': {noformat} CASSANDRA_HOME=/usr/share/cassandra {noformat} > Getting Started instructions don't work in README.txt - wrong version of jamm, wrong path > ----------------------------------------------------------------------------------------- > > Key: CASSANDRA-3512 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3512 > Project: Cassandra > Issue Type: Bug > Components: Packaging > Environment: Ubuntu 11.04 > Reporter: David Allsopp > Assignee: Brandon Williams > Priority: Minor > Fix For: 2.0 > > > Download latest release from http://www.apache.org/dyn/closer.cgi?path=/cassandra/1.0.3/apache-cassandra-1.0.3-bin.tar.gz > Unpack the tarball. > Follow instructions in README.txt, concluding with: > {noformat} > dna@master:~/code/apache-cassandra-1.0.3$ bin/cassandra -f > Error opening zip file or JAR manifest missing : /lib/jamm-0.2.1.jar > Error occurred during initialization of VM > agent library failed to init: instrument > {noformat} > Firstly, the version of jamm packaged with Cassandra 1.0.3 is jamm-0.2.5, not jamm-0.2.1. > Both bin/cassandra.bat and conf/cassandra-env.sh reference jamm-0.2.5 so not sure where jamm-0.2.1 is being referenced from - nothing obvious using grep. > Secondly, /lib/jamm-0.2.1.jar is the wrong path - should be set relative to working directory, not filesystem root > (Incidentally, Cassandra v1.0.3 is still listed as unreleased on JIRA.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira