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 <ruijian....@gmail.com> wrote:

> 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.
> Ryan
> On 07/28/2017 22:31,piet molenaar<piet....@gmail.com> <piet....@gmail.com>
> wrote:
>
> 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 NativeLibraryLinux.java:62 - Failed
> to link the C library against JNA. Native methods will be unavailable.
> java.lang.UnsatisfiedLinkError: /tmp/jna-3506402/jna7194809249311751737.tmp:
> /lib64/libc.so.6: version `GLIBC_2.14' not found (required by
> /tmp/jna-3506402/jna7194809249311751737.tmp)
>
> The same happened with the binary. Looking the library up in the CentOS
> community this is till EOL of series 6.X restricted to version glibc_2.12
>
> Any ideas how to circumvent this or should I use an older version of
> Cassandra?
>
> Regards,
> Piet
>
>
> --
> Piet Molenaar
> piet....@gmail.com
> Department of Oncogenomics, M1-131
> Academic Medical Center
> University of Amsterdam
> Meibergdreef 9
> 1105 AZ Amsterdam
> the Netherlands
>
> tel (+31) 20-5666592 <+31%2020%20566%206592>
> fax (+31) 20-6918626 <+31%2020%20691%208626>
>
>


-- 
Piet Molenaar
piet....@gmail.com
Department of Oncogenomics, M1-131
Academic Medical Center
University of Amsterdam
Meibergdreef 9
1105 AZ Amsterdam
the Netherlands

tel (+31) 20-5666592
fax (+31) 20-6918626

Reply via email to