[
https://issues.apache.org/jira/browse/CASSANDRA-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995524#comment-12995524
]
Jeremy Hanna edited comment on CASSANDRA-2169 at 2/16/11 9:18 PM:
------------------------------------------------------------------
Based on a suggestion from jake and brandon, I added {quote}session required
pam_limits.so{quote} to /etc/pam.d/common-session and rebooted. That made it
so the memlock value was set correctly. However, for some reason, using
/etc/init.d/cassandra still gives the memory locking error. I su to the
cassandra user and run {quote}/usr/sbin/cassandra -f{quote} and it is able to
lock the memory.
For the pam setting, see
http://posidev.com/blog/2009/06/04/set-ulimit-parameters-on-ubuntu/
was (Author: jeromatron):
Based on a suggestion from jake and brandon, I added {quote}session
required pam_limits.so{quote} to /etc/pam.d/common-session and rebooted. That
made it so the memlock value was set correctly. However, for some reason,
using /etc/init.d/cassandra still gives the memory locking error. I su to the
cassandra user and run {quote}/usr/sbin/cassandra -f{quote} and it is able to
lock the memory.
> user created with debian packaging is unable to increase memlock
> ----------------------------------------------------------------
>
> Key: CASSANDRA-2169
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2169
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
> Reporter: Jeremy Hanna
> Priority: Minor
>
> To reproduce:
> - Install a fresh copy of ubuntu 10.04.
> - Install sun's java6 jdk.
> - Install libjna-java 3.2.7 into /usr/share/java.
> - Install cassandra 0.7.0 from the apache debian packages.
> - Start cassandra using /etc/init.d/cassandra
> In the output.log there will be the following error:
> {quote}
> Unable to lock JVM memory (ENOMEM). This can result in part of the JVM being
> swapped out, especially with mmapped I/O enabled. Increase RLIMIT_MEMLOCK or
> run Cassandra as root.
> {quote}
> This shouldn't be as the debian package creates
> /etc/security/limits.d/cassandra.conf and sets the cassandra user's memlock
> limit to 'unlimited'.
> I tried a variety of things including making the memlock unlimited for all
> users in /etc/security/limits.conf. I was able to run cassandra using root
> with jna symbolically linked into /usr/share/cassandra from /usr/share/java,
> but I could never get the init.d script to work and get beyond that error.
> Based on all the trial and error, I think it might have to do with the
> cassandra user itself, but my debian/ubuntu fu isn't as good as others'.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
