Tremendous! I already suspected it to be a JNA issue but didn't know how to
solve it. I'll try this in my setup; I am experimenting what configuration
to use anyways...
Thanks a lot!
On Mon, Jul 31, 2017 at 5:19 PM, Jeff Jirsa wrote:
> Sigh, I've tried to reply to this three times and none are i
Sigh, I've tried to reply to this three times and none are in the archives, so
I don't think they're making it through. Apologies if this is the fourth time
someone's seen it:
The problem is JNA jar that was upgraded recently and bumped the glibc
requirement
https://issues.apache.org/jira/bro
Thanks Ryan, I couldn't find that version but tried with the 3.0.14
version, to no avail. I ended up configuring the VM's in my cloud with
RHEL7 and that includes glib2_17...
Best regards,
Piet
On Fri, Jul 28, 2017 at 6:29 PM, ruijian.lee wrote:
> Hi Piet,
>
> I have also encountered this situat
Hi Piet,I have also encountered this situation, when I installed Cassandra 3.11.0 on RHEL . It seems complain of low GLIBC version. Then I use an older version of Cassandra 3.9.0. It works.
Thanks.RyanOn 07/28/2017 22:31，piet molenaar wrote：
Hi, I've installed Cassandra on a Ce
Hi, I've installed Cassandra on a CentOS cluster of VM's
When starting up Cassandra gives OK but when actually checking the nodetool
status this gives a connection error, and when checking Cassandra is in
fact not running at all.
The log shows problems:
ERROR [main] 2017-07-28 14:03:56,958 Native
