cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Hanna (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-2169) user created with debian packaging is unable to increase memlock
Date Fri, 18 Feb 2011 16:21:38 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996493#comment-12996493
] 

Jeremy Hanna commented on CASSANDRA-2169:
-----------------------------------------

Paul: so is that something that would go in the /debian configuration as a change?  Would
you like me to try that in my test server and see if that resolves the problem?

> 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

        

Mime
View raw message