[jira] [Commented] (CASSANDRA-3512) Getting Started instructions don't work in README.txt - wrong version of jamm, wrong path

2013-05-22 Thread Dave Brosius (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13664752#comment-13664752
 ] 

Dave Brosius commented on CASSANDRA-3512:
-

i don't see anything wrong on trunk here.

cassandra.in.sh does

if [ x$CASSANDRA_HOME = x ]; then
CASSANDRA_HOME=`dirname $0`/..
fi

which works correctly whether you have it explicitly set (EXPORTED) or not.



 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: Dave Brosius
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


[jira] [Commented] (CASSANDRA-3512) Getting Started instructions don't work in README.txt - wrong version of jamm, wrong path

2013-03-28 Thread Eugene (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616636#comment-13616636
 ] 

Eugene commented on CASSANDRA-3512:
---

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


[jira] [Commented] (CASSANDRA-3512) Getting Started instructions don't work in README.txt - wrong version of jamm, wrong path

2011-11-21 Thread David Allsopp (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154278#comment-13154278
 ] 

David Allsopp commented on CASSANDRA-3512:
--

I think the problem is that bin/cassandra.bat is detecting a cassandra.in.sh 
from a previous install of Cassandra. Setting CASSANDRA_INCLUDE to point 
explicitly to bin/cassandra.in.sh fixes the problem.

 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
Affects Versions: 1.0.3
 Environment: Ubuntu 11.04
Reporter: David Allsopp
Priority: Minor

 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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira