You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Jason Pell <ja...@pellcorp.com> on 2010/11/26 05:02:08 UTC
Issues getting JNA to work correctly under centos 5.5 using cassandra
0.7.0-rc1 and JNA 2.7.3
Hi,
I have set the memlock limit to unlimited in /etc/security/limits.conf
[developr@localhost apache-cassandra-0.7.0-rc1]$ ulimit -l
0
Running as a non root user gets me a Unknown mlockall error 1
[developr@localhost apache-cassandra-0.7.0-rc1]$ bin/cassandra
[developr@localhost apache-cassandra-0.7.0-rc1]$ INFO 14:52:47,777
Heap size: 1060569088/1061617664
WARN 14:52:47,884 Unknown mlockall error 1
If I run as root user
[developr@localhost apache-cassandra-0.7.0-rc1]$ sudo bin/cassandra
[developr@localhost apache-cassandra-0.7.0-rc1]$ INFO 14:53:43,776
Heap size: 1060569088/1061617664
INFO 14:53:52,510 JNA mlockall successful
I am running linux
Linux localhost.localdomain 2.6.18-194.17.4.el5 #1 SMP Mon Oct 25
15:51:07 EDT 2010 i686 i686 i386 GNU/Linux
Java
[developr@localhost apache-cassandra-0.7.0-rc1]$ java -version
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) Client VM (build 17.1-b03, mixed mode)
What else can I provide to determine this issue, or is my centos
kernel just not capable?? Perhaps only more recent kernels are
supported outside of root?
Re: Issues getting JNA to work correctly under centos 5.5 using
cassandra 0.7.0-rc1 and JNA 2.7.3
Posted by ja...@gmail.com.
Hi,
Thanks for that your suggestions worked a treat. I created a new
cassandra user and set the value to unlimited
and I get the desired log:
INFO 08:49:50,204 JNA mlockall successful
On Tue, Nov 30, 2010 at 7:56 AM, Jason Pell <ja...@gmail.com> wrote:
> Awesome thanks will make the changes
>
> So is the man page inaccurate? Or is jna doing something wrong?
>
> Sent from my iPhone
>
> On Nov 30, 2010, at 7:28, Nate McCall <na...@riptano.com> wrote:
>
>> Ok, I was able to reproduce this with "0" as the value. Changing it to
>> "unlimited" will make this go away. A closer reading of the
>> limits.conf man page seems to leave some ambiguity when taken with the
>> examples:
>> "All items support the values -1, unlimited or infinity indicating no
>> limit, except for priority and nice."
>>
>> I would recommend tightening this to a specific user. The line I ended
>> up with for the "cassandra" user was:
>>
>> cassandra - memlock unlimited
>>
>> You probably want to add a line for nofile in there at ~ 16384 as well
>> while your there as that can be an issue depending on load.
>>
>>
>>
>> On Mon, Nov 29, 2010 at 1:59 PM, Jason Pell <ja...@pellcorp.com> wrote:
>>> * - memlock 0
>>>
>>>
>>> On Tue, Nov 30, 2010 at 4:40 AM, Nate McCall <na...@riptano.com> wrote:
>>>> What does the current line(s) in limits.conf look like?
>>>>
>>>> On Mon, Nov 29, 2010 at 2:01 AM, <ja...@gmail.com> wrote:
>>>>> I checked and /etc/security/limits.conf on redhat supports zero (0) to
>>>>> mean unlimited. Here is the sample from the man page. Notice the
>>>>> soft core entry.
>>>>>
>>>>> EXAMPLES
>>>>> These are some example lines which might be specified in
>>>>> /etc/security/limits.conf.
>>>>>
>>>>> * soft core 0
>>>>> * hard rss 10000
>>>>> @student hard nproc 20
>>>>> @faculty soft nproc 20
>>>>> @faculty hard nproc 50
>>>>> ftp hard nproc 0
>>>>> @student - maxlogins 4
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Nov 29, 2010 at 6:51 AM, Jason Pell <ja...@gmail.com> wrote:
>>>>>> Ok that's a good point i will check - I am not sure.
>>>>>>
>>>>>> Sent from my iPhone
>>>>>> On Nov 29, 2010, at 5:53, Tyler Hobbs <ty...@riptano.com> wrote:
>>>>>>
>>>>>> I'm not familiar with ulimit on RedHat systems, but are you sure you
>>>>>> have ulimit set correctly? Did you set it to '0' or 'unlimited'? I ask
>>>>>> because on a Debian system, I get this:
>>>>>>
>>>>>> thobbs@~ $ ulimit -l
>>>>>> unlimited
>>>>>>
>>>>>> Where you said that you got back '0'.
>>>>>>
>>>>>> - Tyler
>>>>>>
>>>>>> On Sun, Nov 28, 2010 at 1:15 AM, Jason Pell <ja...@pellcorp.com> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have selinux disabled via /etc/sysconfig/selinux already. But I did
>>>>>>> as you suggested anyway, even restarted the whole machine again too
>>>>>>> and still no difference. Do you know if there is a way to discover
>>>>>>> exactly what this error means?
>>>>>>>
>>>>>>> THanks
>>>>>>> Jason
>>>>>>>
>>>>>>> On Sat, Nov 27, 2010 at 3:59 AM, Nate McCall <na...@riptano.com> wrote:
>>>>>>>> This might be an issue with selinux. You can try this quickly to
>>>>>>>> temporarily disable selinux enforcement:
>>>>>>>> /usr/sbin/setenforce 0 (as root)
>>>>>>>>
>>>>>>>> and then start cassandra as your user.
>>>>>>>>
>>>>>>>> On Fri, Nov 26, 2010 at 1:00 AM, Jason Pell <ja...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>> I restarted the box :-) so it's well and truly set
>>>>>>>>>
>>>>>>>>> Sent from my iPhone
>>>>>>>>> On Nov 26, 2010, at 17:57, Brandon Williams <dr...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> On Thu, Nov 25, 2010 at 10:02 PM, Jason Pell <ja...@pellcorp.com>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I have set the memlock limit to unlimited in /etc/security/limits.conf
>>>>>>>>>>
>>>>>>>>>> [developr@localhost apache-cassandra-0.7.0-rc1]$ ulimit -l
>>>>>>>>>> 0
>>>>>>>>>>
>>>>>>>>>> Running as a non root user gets me a Unknown mlockall error 1
>>>>>>>>>
>>>>>>>>> Have you tried logging out and back in after changing limits.conf?
>>>>>>>>> -Brandon
>>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>
Re: Issues getting JNA to work correctly under centos 5.5 using cassandra 0.7.0-rc1 and JNA 2.7.3
Posted by Jason Pell <ja...@gmail.com>.
Awesome thanks will make the changes
So is the man page inaccurate? Or is jna doing something wrong?
Sent from my iPhone
On Nov 30, 2010, at 7:28, Nate McCall <na...@riptano.com> wrote:
> Ok, I was able to reproduce this with "0" as the value. Changing it to
> "unlimited" will make this go away. A closer reading of the
> limits.conf man page seems to leave some ambiguity when taken with the
> examples:
> "All items support the values -1, unlimited or infinity indicating no
> limit, except for priority and nice."
>
> I would recommend tightening this to a specific user. The line I ended
> up with for the "cassandra" user was:
>
> cassandra - memlock unlimited
>
> You probably want to add a line for nofile in there at ~ 16384 as well
> while your there as that can be an issue depending on load.
>
>
>
> On Mon, Nov 29, 2010 at 1:59 PM, Jason Pell <ja...@pellcorp.com> wrote:
>> * - memlock 0
>>
>>
>> On Tue, Nov 30, 2010 at 4:40 AM, Nate McCall <na...@riptano.com> wrote:
>>> What does the current line(s) in limits.conf look like?
>>>
>>> On Mon, Nov 29, 2010 at 2:01 AM, <ja...@gmail.com> wrote:
>>>> I checked and /etc/security/limits.conf on redhat supports zero (0) to
>>>> mean unlimited. Here is the sample from the man page. Notice the
>>>> soft core entry.
>>>>
>>>> EXAMPLES
>>>> These are some example lines which might be specified in
>>>> /etc/security/limits.conf.
>>>>
>>>> * soft core 0
>>>> * hard rss 10000
>>>> @student hard nproc 20
>>>> @faculty soft nproc 20
>>>> @faculty hard nproc 50
>>>> ftp hard nproc 0
>>>> @student - maxlogins 4
>>>>
>>>>
>>>>
>>>> On Mon, Nov 29, 2010 at 6:51 AM, Jason Pell <ja...@gmail.com> wrote:
>>>>> Ok that's a good point i will check - I am not sure.
>>>>>
>>>>> Sent from my iPhone
>>>>> On Nov 29, 2010, at 5:53, Tyler Hobbs <ty...@riptano.com> wrote:
>>>>>
>>>>> I'm not familiar with ulimit on RedHat systems, but are you sure you
>>>>> have ulimit set correctly? Did you set it to '0' or 'unlimited'? I ask
>>>>> because on a Debian system, I get this:
>>>>>
>>>>> thobbs@~ $ ulimit -l
>>>>> unlimited
>>>>>
>>>>> Where you said that you got back '0'.
>>>>>
>>>>> - Tyler
>>>>>
>>>>> On Sun, Nov 28, 2010 at 1:15 AM, Jason Pell <ja...@pellcorp.com> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I have selinux disabled via /etc/sysconfig/selinux already. But I did
>>>>>> as you suggested anyway, even restarted the whole machine again too
>>>>>> and still no difference. Do you know if there is a way to discover
>>>>>> exactly what this error means?
>>>>>>
>>>>>> THanks
>>>>>> Jason
>>>>>>
>>>>>> On Sat, Nov 27, 2010 at 3:59 AM, Nate McCall <na...@riptano.com> wrote:
>>>>>>> This might be an issue with selinux. You can try this quickly to
>>>>>>> temporarily disable selinux enforcement:
>>>>>>> /usr/sbin/setenforce 0 (as root)
>>>>>>>
>>>>>>> and then start cassandra as your user.
>>>>>>>
>>>>>>> On Fri, Nov 26, 2010 at 1:00 AM, Jason Pell <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>> I restarted the box :-) so it's well and truly set
>>>>>>>>
>>>>>>>> Sent from my iPhone
>>>>>>>> On Nov 26, 2010, at 17:57, Brandon Williams <dr...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> On Thu, Nov 25, 2010 at 10:02 PM, Jason Pell <ja...@pellcorp.com>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I have set the memlock limit to unlimited in /etc/security/limits.conf
>>>>>>>>>
>>>>>>>>> [developr@localhost apache-cassandra-0.7.0-rc1]$ ulimit -l
>>>>>>>>> 0
>>>>>>>>>
>>>>>>>>> Running as a non root user gets me a Unknown mlockall error 1
>>>>>>>>
>>>>>>>> Have you tried logging out and back in after changing limits.conf?
>>>>>>>> -Brandon
>>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
Re: Issues getting JNA to work correctly under centos 5.5 using
cassandra 0.7.0-rc1 and JNA 2.7.3
Posted by Nate McCall <na...@riptano.com>.
Ok, I was able to reproduce this with "0" as the value. Changing it to
"unlimited" will make this go away. A closer reading of the
limits.conf man page seems to leave some ambiguity when taken with the
examples:
"All items support the values -1, unlimited or infinity indicating no
limit, except for priority and nice."
I would recommend tightening this to a specific user. The line I ended
up with for the "cassandra" user was:
cassandra - memlock unlimited
You probably want to add a line for nofile in there at ~ 16384 as well
while your there as that can be an issue depending on load.
On Mon, Nov 29, 2010 at 1:59 PM, Jason Pell <ja...@pellcorp.com> wrote:
> * - memlock 0
>
>
> On Tue, Nov 30, 2010 at 4:40 AM, Nate McCall <na...@riptano.com> wrote:
>> What does the current line(s) in limits.conf look like?
>>
>> On Mon, Nov 29, 2010 at 2:01 AM, <ja...@gmail.com> wrote:
>>> I checked and /etc/security/limits.conf on redhat supports zero (0) to
>>> mean unlimited. Here is the sample from the man page. Notice the
>>> soft core entry.
>>>
>>> EXAMPLES
>>> These are some example lines which might be specified in
>>> /etc/security/limits.conf.
>>>
>>> * soft core 0
>>> * hard rss 10000
>>> @student hard nproc 20
>>> @faculty soft nproc 20
>>> @faculty hard nproc 50
>>> ftp hard nproc 0
>>> @student - maxlogins 4
>>>
>>>
>>>
>>> On Mon, Nov 29, 2010 at 6:51 AM, Jason Pell <ja...@gmail.com> wrote:
>>>> Ok that's a good point i will check - I am not sure.
>>>>
>>>> Sent from my iPhone
>>>> On Nov 29, 2010, at 5:53, Tyler Hobbs <ty...@riptano.com> wrote:
>>>>
>>>> I'm not familiar with ulimit on RedHat systems, but are you sure you
>>>> have ulimit set correctly? Did you set it to '0' or 'unlimited'? I ask
>>>> because on a Debian system, I get this:
>>>>
>>>> thobbs@~ $ ulimit -l
>>>> unlimited
>>>>
>>>> Where you said that you got back '0'.
>>>>
>>>> - Tyler
>>>>
>>>> On Sun, Nov 28, 2010 at 1:15 AM, Jason Pell <ja...@pellcorp.com> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I have selinux disabled via /etc/sysconfig/selinux already. But I did
>>>>> as you suggested anyway, even restarted the whole machine again too
>>>>> and still no difference. Do you know if there is a way to discover
>>>>> exactly what this error means?
>>>>>
>>>>> THanks
>>>>> Jason
>>>>>
>>>>> On Sat, Nov 27, 2010 at 3:59 AM, Nate McCall <na...@riptano.com> wrote:
>>>>> > This might be an issue with selinux. You can try this quickly to
>>>>> > temporarily disable selinux enforcement:
>>>>> > /usr/sbin/setenforce 0 (as root)
>>>>> >
>>>>> > and then start cassandra as your user.
>>>>> >
>>>>> > On Fri, Nov 26, 2010 at 1:00 AM, Jason Pell <ja...@gmail.com>
>>>>> > wrote:
>>>>> >> I restarted the box :-) so it's well and truly set
>>>>> >>
>>>>> >> Sent from my iPhone
>>>>> >> On Nov 26, 2010, at 17:57, Brandon Williams <dr...@gmail.com> wrote:
>>>>> >>
>>>>> >> On Thu, Nov 25, 2010 at 10:02 PM, Jason Pell <ja...@pellcorp.com>
>>>>> >> wrote:
>>>>> >>>
>>>>> >>> Hi,
>>>>> >>>
>>>>> >>> I have set the memlock limit to unlimited in /etc/security/limits.conf
>>>>> >>>
>>>>> >>> [developr@localhost apache-cassandra-0.7.0-rc1]$ ulimit -l
>>>>> >>> 0
>>>>> >>>
>>>>> >>> Running as a non root user gets me a Unknown mlockall error 1
>>>>> >>
>>>>> >> Have you tried logging out and back in after changing limits.conf?
>>>>> >> -Brandon
>>>>> >
>>>>
>>>>
>>>
>>
>
Re: Issues getting JNA to work correctly under centos 5.5 using
cassandra 0.7.0-rc1 and JNA 2.7.3
Posted by Jason Pell <ja...@pellcorp.com>.
* - memlock 0
On Tue, Nov 30, 2010 at 4:40 AM, Nate McCall <na...@riptano.com> wrote:
> What does the current line(s) in limits.conf look like?
>
> On Mon, Nov 29, 2010 at 2:01 AM, <ja...@gmail.com> wrote:
>> I checked and /etc/security/limits.conf on redhat supports zero (0) to
>> mean unlimited. Here is the sample from the man page. Notice the
>> soft core entry.
>>
>> EXAMPLES
>> These are some example lines which might be specified in
>> /etc/security/limits.conf.
>>
>> * soft core 0
>> * hard rss 10000
>> @student hard nproc 20
>> @faculty soft nproc 20
>> @faculty hard nproc 50
>> ftp hard nproc 0
>> @student - maxlogins 4
>>
>>
>>
>> On Mon, Nov 29, 2010 at 6:51 AM, Jason Pell <ja...@gmail.com> wrote:
>>> Ok that's a good point i will check - I am not sure.
>>>
>>> Sent from my iPhone
>>> On Nov 29, 2010, at 5:53, Tyler Hobbs <ty...@riptano.com> wrote:
>>>
>>> I'm not familiar with ulimit on RedHat systems, but are you sure you
>>> have ulimit set correctly? Did you set it to '0' or 'unlimited'? I ask
>>> because on a Debian system, I get this:
>>>
>>> thobbs@~ $ ulimit -l
>>> unlimited
>>>
>>> Where you said that you got back '0'.
>>>
>>> - Tyler
>>>
>>> On Sun, Nov 28, 2010 at 1:15 AM, Jason Pell <ja...@pellcorp.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I have selinux disabled via /etc/sysconfig/selinux already. But I did
>>>> as you suggested anyway, even restarted the whole machine again too
>>>> and still no difference. Do you know if there is a way to discover
>>>> exactly what this error means?
>>>>
>>>> THanks
>>>> Jason
>>>>
>>>> On Sat, Nov 27, 2010 at 3:59 AM, Nate McCall <na...@riptano.com> wrote:
>>>> > This might be an issue with selinux. You can try this quickly to
>>>> > temporarily disable selinux enforcement:
>>>> > /usr/sbin/setenforce 0 (as root)
>>>> >
>>>> > and then start cassandra as your user.
>>>> >
>>>> > On Fri, Nov 26, 2010 at 1:00 AM, Jason Pell <ja...@gmail.com>
>>>> > wrote:
>>>> >> I restarted the box :-) so it's well and truly set
>>>> >>
>>>> >> Sent from my iPhone
>>>> >> On Nov 26, 2010, at 17:57, Brandon Williams <dr...@gmail.com> wrote:
>>>> >>
>>>> >> On Thu, Nov 25, 2010 at 10:02 PM, Jason Pell <ja...@pellcorp.com>
>>>> >> wrote:
>>>> >>>
>>>> >>> Hi,
>>>> >>>
>>>> >>> I have set the memlock limit to unlimited in /etc/security/limits.conf
>>>> >>>
>>>> >>> [developr@localhost apache-cassandra-0.7.0-rc1]$ ulimit -l
>>>> >>> 0
>>>> >>>
>>>> >>> Running as a non root user gets me a Unknown mlockall error 1
>>>> >>
>>>> >> Have you tried logging out and back in after changing limits.conf?
>>>> >> -Brandon
>>>> >
>>>
>>>
>>
>
Re: Issues getting JNA to work correctly under centos 5.5 using
cassandra 0.7.0-rc1 and JNA 2.7.3
Posted by Nate McCall <na...@riptano.com>.
What does the current line(s) in limits.conf look like?
On Mon, Nov 29, 2010 at 2:01 AM, <ja...@gmail.com> wrote:
> I checked and /etc/security/limits.conf on redhat supports zero (0) to
> mean unlimited. Here is the sample from the man page. Notice the
> soft core entry.
>
> EXAMPLES
> These are some example lines which might be specified in
> /etc/security/limits.conf.
>
> * soft core 0
> * hard rss 10000
> @student hard nproc 20
> @faculty soft nproc 20
> @faculty hard nproc 50
> ftp hard nproc 0
> @student - maxlogins 4
>
>
>
> On Mon, Nov 29, 2010 at 6:51 AM, Jason Pell <ja...@gmail.com> wrote:
>> Ok that's a good point i will check - I am not sure.
>>
>> Sent from my iPhone
>> On Nov 29, 2010, at 5:53, Tyler Hobbs <ty...@riptano.com> wrote:
>>
>> I'm not familiar with ulimit on RedHat systems, but are you sure you
>> have ulimit set correctly? Did you set it to '0' or 'unlimited'? I ask
>> because on a Debian system, I get this:
>>
>> thobbs@~ $ ulimit -l
>> unlimited
>>
>> Where you said that you got back '0'.
>>
>> - Tyler
>>
>> On Sun, Nov 28, 2010 at 1:15 AM, Jason Pell <ja...@pellcorp.com> wrote:
>>>
>>> Hi,
>>>
>>> I have selinux disabled via /etc/sysconfig/selinux already. But I did
>>> as you suggested anyway, even restarted the whole machine again too
>>> and still no difference. Do you know if there is a way to discover
>>> exactly what this error means?
>>>
>>> THanks
>>> Jason
>>>
>>> On Sat, Nov 27, 2010 at 3:59 AM, Nate McCall <na...@riptano.com> wrote:
>>> > This might be an issue with selinux. You can try this quickly to
>>> > temporarily disable selinux enforcement:
>>> > /usr/sbin/setenforce 0 (as root)
>>> >
>>> > and then start cassandra as your user.
>>> >
>>> > On Fri, Nov 26, 2010 at 1:00 AM, Jason Pell <ja...@gmail.com>
>>> > wrote:
>>> >> I restarted the box :-) so it's well and truly set
>>> >>
>>> >> Sent from my iPhone
>>> >> On Nov 26, 2010, at 17:57, Brandon Williams <dr...@gmail.com> wrote:
>>> >>
>>> >> On Thu, Nov 25, 2010 at 10:02 PM, Jason Pell <ja...@pellcorp.com>
>>> >> wrote:
>>> >>>
>>> >>> Hi,
>>> >>>
>>> >>> I have set the memlock limit to unlimited in /etc/security/limits.conf
>>> >>>
>>> >>> [developr@localhost apache-cassandra-0.7.0-rc1]$ ulimit -l
>>> >>> 0
>>> >>>
>>> >>> Running as a non root user gets me a Unknown mlockall error 1
>>> >>
>>> >> Have you tried logging out and back in after changing limits.conf?
>>> >> -Brandon
>>> >
>>
>>
>
Re: Issues getting JNA to work correctly under centos 5.5 using
cassandra 0.7.0-rc1 and JNA 2.7.3
Posted by ja...@gmail.com.
I checked and /etc/security/limits.conf on redhat supports zero (0) to
mean unlimited. Here is the sample from the man page. Notice the
soft core entry.
EXAMPLES
These are some example lines which might be specified in
/etc/security/limits.conf.
* soft core 0
* hard rss 10000
@student hard nproc 20
@faculty soft nproc 20
@faculty hard nproc 50
ftp hard nproc 0
@student - maxlogins 4
On Mon, Nov 29, 2010 at 6:51 AM, Jason Pell <ja...@gmail.com> wrote:
> Ok that's a good point i will check - I am not sure.
>
> Sent from my iPhone
> On Nov 29, 2010, at 5:53, Tyler Hobbs <ty...@riptano.com> wrote:
>
> I'm not familiar with ulimit on RedHat systems, but are you sure you
> have ulimit set correctly? Did you set it to '0' or 'unlimited'? I ask
> because on a Debian system, I get this:
>
> thobbs@~ $ ulimit -l
> unlimited
>
> Where you said that you got back '0'.
>
> - Tyler
>
> On Sun, Nov 28, 2010 at 1:15 AM, Jason Pell <ja...@pellcorp.com> wrote:
>>
>> Hi,
>>
>> I have selinux disabled via /etc/sysconfig/selinux already. But I did
>> as you suggested anyway, even restarted the whole machine again too
>> and still no difference. Do you know if there is a way to discover
>> exactly what this error means?
>>
>> THanks
>> Jason
>>
>> On Sat, Nov 27, 2010 at 3:59 AM, Nate McCall <na...@riptano.com> wrote:
>> > This might be an issue with selinux. You can try this quickly to
>> > temporarily disable selinux enforcement:
>> > /usr/sbin/setenforce 0 (as root)
>> >
>> > and then start cassandra as your user.
>> >
>> > On Fri, Nov 26, 2010 at 1:00 AM, Jason Pell <ja...@gmail.com>
>> > wrote:
>> >> I restarted the box :-) so it's well and truly set
>> >>
>> >> Sent from my iPhone
>> >> On Nov 26, 2010, at 17:57, Brandon Williams <dr...@gmail.com> wrote:
>> >>
>> >> On Thu, Nov 25, 2010 at 10:02 PM, Jason Pell <ja...@pellcorp.com>
>> >> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> I have set the memlock limit to unlimited in /etc/security/limits.conf
>> >>>
>> >>> [developr@localhost apache-cassandra-0.7.0-rc1]$ ulimit -l
>> >>> 0
>> >>>
>> >>> Running as a non root user gets me a Unknown mlockall error 1
>> >>
>> >> Have you tried logging out and back in after changing limits.conf?
>> >> -Brandon
>> >
>
>
Re: Issues getting JNA to work correctly under centos 5.5 using cassandra 0.7.0-rc1 and JNA 2.7.3
Posted by Jason Pell <ja...@gmail.com>.
Ok that's a good point i will check - I am not sure.
Sent from my iPhone
On Nov 29, 2010, at 5:53, Tyler Hobbs <ty...@riptano.com> wrote:
> I'm not familiar with ulimit on RedHat systems, but are you sure you
> have ulimit set correctly? Did you set it to '0' or 'unlimited'? I ask
> because on a Debian system, I get this:
>
> thobbs@~ $ ulimit -l
> unlimited
>
> Where you said that you got back '0'.
>
> - Tyler
>
> On Sun, Nov 28, 2010 at 1:15 AM, Jason Pell <ja...@pellcorp.com> wrote:
> Hi,
>
> I have selinux disabled via /etc/sysconfig/selinux already. But I did
> as you suggested anyway, even restarted the whole machine again too
> and still no difference. Do you know if there is a way to discover
> exactly what this error means?
>
> THanks
> Jason
>
> On Sat, Nov 27, 2010 at 3:59 AM, Nate McCall <na...@riptano.com> wrote:
> > This might be an issue with selinux. You can try this quickly to
> > temporarily disable selinux enforcement:
> > /usr/sbin/setenforce 0 (as root)
> >
> > and then start cassandra as your user.
> >
> > On Fri, Nov 26, 2010 at 1:00 AM, Jason Pell <ja...@gmail.com> wrote:
> >> I restarted the box :-) so it's well and truly set
> >>
> >> Sent from my iPhone
> >> On Nov 26, 2010, at 17:57, Brandon Williams <dr...@gmail.com> wrote:
> >>
> >> On Thu, Nov 25, 2010 at 10:02 PM, Jason Pell <ja...@pellcorp.com> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I have set the memlock limit to unlimited in /etc/security/limits.conf
> >>>
> >>> [developr@localhost apache-cassandra-0.7.0-rc1]$ ulimit -l
> >>> 0
> >>>
> >>> Running as a non root user gets me a Unknown mlockall error 1
> >>
> >> Have you tried logging out and back in after changing limits.conf?
> >> -Brandon
> >
>
Re: Issues getting JNA to work correctly under centos 5.5 using
cassandra 0.7.0-rc1 and JNA 2.7.3
Posted by Tyler Hobbs <ty...@riptano.com>.
I'm not familiar with ulimit on RedHat systems, but are you sure you
have ulimit set correctly? Did you set it to '0' or 'unlimited'? I ask
because on a Debian system, I get this:
thobbs@~ $ ulimit -l
unlimited
Where you said that you got back '0'.
- Tyler
On Sun, Nov 28, 2010 at 1:15 AM, Jason Pell <ja...@pellcorp.com> wrote:
> Hi,
>
> I have selinux disabled via /etc/sysconfig/selinux already. But I did
> as you suggested anyway, even restarted the whole machine again too
> and still no difference. Do you know if there is a way to discover
> exactly what this error means?
>
> THanks
> Jason
>
> On Sat, Nov 27, 2010 at 3:59 AM, Nate McCall <na...@riptano.com> wrote:
> > This might be an issue with selinux. You can try this quickly to
> > temporarily disable selinux enforcement:
> > /usr/sbin/setenforce 0 (as root)
> >
> > and then start cassandra as your user.
> >
> > On Fri, Nov 26, 2010 at 1:00 AM, Jason Pell <ja...@gmail.com>
> wrote:
> >> I restarted the box :-) so it's well and truly set
> >>
> >> Sent from my iPhone
> >> On Nov 26, 2010, at 17:57, Brandon Williams <dr...@gmail.com> wrote:
> >>
> >> On Thu, Nov 25, 2010 at 10:02 PM, Jason Pell <ja...@pellcorp.com>
> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I have set the memlock limit to unlimited in /etc/security/limits.conf
> >>>
> >>> [developr@localhost apache-cassandra-0.7.0-rc1]$ ulimit -l
> >>> 0
> >>>
> >>> Running as a non root user gets me a Unknown mlockall error 1
> >>
> >> Have you tried logging out and back in after changing limits.conf?
> >> -Brandon
> >
>
Re: Issues getting JNA to work correctly under centos 5.5 using
cassandra 0.7.0-rc1 and JNA 2.7.3
Posted by Jason Pell <ja...@pellcorp.com>.
Hi,
I have selinux disabled via /etc/sysconfig/selinux already. But I did
as you suggested anyway, even restarted the whole machine again too
and still no difference. Do you know if there is a way to discover
exactly what this error means?
THanks
Jason
On Sat, Nov 27, 2010 at 3:59 AM, Nate McCall <na...@riptano.com> wrote:
> This might be an issue with selinux. You can try this quickly to
> temporarily disable selinux enforcement:
> /usr/sbin/setenforce 0 (as root)
>
> and then start cassandra as your user.
>
> On Fri, Nov 26, 2010 at 1:00 AM, Jason Pell <ja...@gmail.com> wrote:
>> I restarted the box :-) so it's well and truly set
>>
>> Sent from my iPhone
>> On Nov 26, 2010, at 17:57, Brandon Williams <dr...@gmail.com> wrote:
>>
>> On Thu, Nov 25, 2010 at 10:02 PM, Jason Pell <ja...@pellcorp.com> wrote:
>>>
>>> Hi,
>>>
>>> I have set the memlock limit to unlimited in /etc/security/limits.conf
>>>
>>> [developr@localhost apache-cassandra-0.7.0-rc1]$ ulimit -l
>>> 0
>>>
>>> Running as a non root user gets me a Unknown mlockall error 1
>>
>> Have you tried logging out and back in after changing limits.conf?
>> -Brandon
>
Re: Issues getting JNA to work correctly under centos 5.5 using
cassandra 0.7.0-rc1 and JNA 2.7.3
Posted by Nate McCall <na...@riptano.com>.
This might be an issue with selinux. You can try this quickly to
temporarily disable selinux enforcement:
/usr/sbin/setenforce 0 (as root)
and then start cassandra as your user.
On Fri, Nov 26, 2010 at 1:00 AM, Jason Pell <ja...@gmail.com> wrote:
> I restarted the box :-) so it's well and truly set
>
> Sent from my iPhone
> On Nov 26, 2010, at 17:57, Brandon Williams <dr...@gmail.com> wrote:
>
> On Thu, Nov 25, 2010 at 10:02 PM, Jason Pell <ja...@pellcorp.com> wrote:
>>
>> Hi,
>>
>> I have set the memlock limit to unlimited in /etc/security/limits.conf
>>
>> [developr@localhost apache-cassandra-0.7.0-rc1]$ ulimit -l
>> 0
>>
>> Running as a non root user gets me a Unknown mlockall error 1
>
> Have you tried logging out and back in after changing limits.conf?
> -Brandon
Re: Issues getting JNA to work correctly under centos 5.5 using cassandra 0.7.0-rc1 and JNA 2.7.3
Posted by Jason Pell <ja...@gmail.com>.
I restarted the box :-) so it's well and truly set
Sent from my iPhone
On Nov 26, 2010, at 17:57, Brandon Williams <dr...@gmail.com> wrote:
> On Thu, Nov 25, 2010 at 10:02 PM, Jason Pell <ja...@pellcorp.com> wrote:
> Hi,
>
> I have set the memlock limit to unlimited in /etc/security/limits.conf
>
> [developr@localhost apache-cassandra-0.7.0-rc1]$ ulimit -l
> 0
>
> Running as a non root user gets me a Unknown mlockall error 1
>
> Have you tried logging out and back in after changing limits.conf?
>
> -Brandon
Re: Issues getting JNA to work correctly under centos 5.5 using
cassandra 0.7.0-rc1 and JNA 2.7.3
Posted by Brandon Williams <dr...@gmail.com>.
On Thu, Nov 25, 2010 at 10:02 PM, Jason Pell <ja...@pellcorp.com> wrote:
> Hi,
>
> I have set the memlock limit to unlimited in /etc/security/limits.conf
>
> [developr@localhost apache-cassandra-0.7.0-rc1]$ ulimit -l
> 0
>
> Running as a non root user gets me a Unknown mlockall error 1
>
Have you tried logging out and back in after changing limits.conf?
-Brandon