i tried my configuration which is working but i am with ubuntu and cassandra 1.0.3 and i am running cassandra under user cassandra. i did not try it with 1.0.5 because i was not able to work with this version and i am waiting to 1.0.6
On Sun, Dec 11, 2011 at 7:50 PM, Caleb Rackliffe <ca...@steelhouse.com>wrote: > I changed the value in limit.conf as you suggested, and that seems to have > no effect. Were you thinking that the OS wasn't respecting the "unlimited"? > > > * > Caleb Rackliffe | Software Developer > M 949.981.0159 | ca...@steelhouse.com > ** > * > > From: Michael Vaknine <micha...@citypath.com> > Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org> > Date: Sun, 11 Dec 2011 05:15:32 -0500 > To: "user@cassandra.apache.org" <user@cassandra.apache.org> > Subject: RE: Cannot Start Cassandra 1.0.5 with JNA on the CLASSPATH > > Try **** > > root - MEMLOCK 14155776**** > > on /etc/security/limits.conf**** > > ** ** > > Michael**** > > ** ** > > *From:* Caleb Rackliffe [mailto:ca...@steelhouse.com<ca...@steelhouse.com>] > > *Sent:* Sunday, December 11, 2011 11:24 AM > *To:* user@cassandra.apache.org > *Subject:* Cannot Start Cassandra 1.0.5 with JNA on the CLASSPATH**** > > ** ** > > Hi All,**** > > ** ** > > I'm trying to start up Cassandra 1.0.5 on a Cent OS 6 machine. I > installed JNA through yum and made a symbolic link to jna.jar in my > Cassandra lib directory. When I run "bin/cassandra -f", I get the > following:**** > > ** ** > > INFO 09:14:31,552 Logging initialized**** > > INFO 09:14:31,555 JVM vendor/version: Java HotSpot(TM) 64-Bit Server > VM/1.6.0_29**** > > INFO 09:14:31,555 Heap size: 3405774848/3405774848**** > > INFO 09:14:31,555 Classpath: > bin/../conf:bin/../build/classes/main:bin/../build/classes/thrift:bin/../lib/antlr-3.2.jar:bin/../lib/apache-cassandra-1.0.5.jar:bin/../lib/apache-cassandra-clientutil-1.0.5.jar:bin/../lib/apache-cassandra-thrift-1.0.5.jar:bin/../lib/avro-1.4.0-fixes.jar:bin/../lib/avro-1.4.0-sources-fixes.jar:bin/../lib/commons-cli-1.1.jar:bin/../lib/commons-codec-1.2.jar:bin/../lib/commons-lang-2.4.jar:bin/../lib/compress-lzf-0.8.4.jar:bin/../lib/concurrentlinkedhashmap-lru-1.2.jar:bin/../lib/guava-r08.jar:bin/../lib/high-scale-lib-1.1.2.jar:bin/../lib/jackson-core-asl-1.4.0.jar:bin/../lib/jackson-mapper-asl-1.4.0.jar:bin/../lib/jamm-0.2.5.jar:bin/../lib/jline-0.9.94.jar:bin/../lib/jna.jar:bin/../lib/json-simple-1.1.jar:bin/../lib/libthrift-0.6.jar:bin/../lib/log4j-1.2.16.jar:bin/../lib/servlet-api-2.5-20081211.jar:bin/../lib/slf4j-api-1.6.1.jar:bin/../lib/slf4j-log4j12-1.6.1.jar:bin/../lib/snakeyaml-1.6.jar:bin/../lib/snappy-java-1.0.4.1.jar:bin/../lib/jamm-0.2.5.jar > **** > > Killed**** > > ** ** > > If I remove the symlink to JNA, it starts up just fine.**** > > ** ** > > Also, I do have entries in my limits.conf for JNA:**** > > ** ** > > root soft memlock unlimited**** > > root hard memlock unlimited**** > > ** ** > > Has anyone else seen this behavior?**** > > ** ** > > Thanks,**** > > ** ** > > *Caleb Rackliffe | Software Developer ***** > > M 949.981.0159 | ca...@steelhouse.com**** > > **** >
