Great! Thanks for the feedback gents.
Have a nice week.
From: Nate McCall
Sent: Tuesday, May 27, 2014 12:39 PM
To: Cassandra Users
I missed that - thanks Holger!
On Tue, May 27, 2014 at 10:14 AM, Holger Hoffstätte
wrote:
On Tue, 27 May 2014 09:26:41 -0500, Nate McC
I missed that - thanks Holger!
On Tue, May 27, 2014 at 10:14 AM, Holger Hoffstätte <
holger.hoffstae...@googlemail.com> wrote:
> On Tue, 27 May 2014 09:26:41 -0500, Nate McCall wrote:
>
> >> In the new setup /tmp was mounted as noexec. So it looks like JNA was
> >> putting the native library her
On Tue, 27 May 2014 09:26:41 -0500, Nate McCall wrote:
>> In the new setup /tmp was mounted as noexec. So it looks like JNA was
>> putting the native library here and then it was unable to execute it.
>>
>>
> If you wanted to keep /tmp noexec (not a bad idea depending on
> environment) you could a
>
>
> In the new setup /tmp was mounted as noexec. So it looks like JNA was
> putting the native library here and then it was unable to execute it.
>
If you wanted to keep /tmp noexec (not a bad idea depending on environment)
you could also append the following to cassandra-env.sh:
JVM_OPTS="$JVM
Figured this one out..
In the new setup /tmp was mounted as noexec. So it looks like JNA was
putting the native library here and then it was unable to execute it.
I hope this can help someone else.
On Mon, May 26, 2014 at 11:33 PM, David Daeschler wrote:
> Good evening list,
>
> I'm having a
Good evening list,
I'm having a rather confusing issue with 4 new nodes that I put up. JNA
doesn't seem to want to work in production even though it works on my test
VM that should have pretty much the same setup.
I have created a series of setup scripts to bring up new nodes. I am using
a tested
