You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "David Allsopp (Created) (JIRA)" <ji...@apache.org> on 2011/11/21 17:16:52 UTC
[jira] [Created] (CASSANDRA-3512) Getting Started instructions
don't work in README.txt - wrong version of jamm, wrong path
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
[jira] [Assigned] (CASSANDRA-3512) Getting Started instructions
don't work in README.txt - wrong version of jamm, wrong path
Posted by "Jonathan Ellis (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reassigned CASSANDRA-3512:
-----------------------------------------
Assignee: Eric Evans
Right. That's by design. Here's the relevant part of bin/cassandra:
{noformat}
# If an include wasn't specified in the environment, then search for one...
if [ "x$CASSANDRA_INCLUDE" = "x" ]; then
# Locations (in order) to use when searching for an include file.
for include in /usr/share/cassandra/cassandra.in.sh \
/usr/local/share/cassandra/cassandra.in.sh \
/opt/cassandra/cassandra.in.sh \
"$HOME/.cassandra.in.sh" \
"`dirname $0`/cassandra.in.sh"; do
if [ -r "$include" ]; then
. "$include"
break
fi
done
# ...otherwise, source the specified include.
elif [ -r "$CASSANDRA_INCLUDE" ]; then
. "$CASSANDRA_INCLUDE"
fi
{noformat}
However, my experience matches yours, that virtually everyone when running bin/cassandra manually expects it to use the files in bin/ and conf/ rather than "global" package-installed ones. (Assigning to Eric for comment since he wrote this.)
> 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
> Assignee: Eric Evans
> 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
[jira] [Commented] (CASSANDRA-3512) Getting Started instructions
don't work in README.txt - wrong version of jamm, wrong path
Posted by "David Allsopp (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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