cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Eggleston (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13519) upgrade from 2.1.13 to 2.2.9
Date Mon, 15 May 2017 16:46:04 GMT

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

Blake Eggleston commented on CASSANDRA-13519:
---------------------------------------------

JNI wasn't able to find the .so it was looking for. Could you provide some basic info about
your hardware, operating system, and cassandra package (tarball, rpm, etc)?

Also, this question is probably more appropriate for the user list (user@cassandra.apache.org).

> upgrade from 2.1.13 to 2.2.9
> ----------------------------
>
>                 Key: CASSANDRA-13519
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13519
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Libraries
>         Environment: 2.2.9
>            Reporter: peng xiao
>
> after upgrading Cassandra from 2.1.13 to 2.2.9,we got the following info in system.log,Could
you please advise.
> INFO  [main] 2017-04-25 10:43:30,073 SigarLibrary.java:44 - Initializing SIGAR library
> INFO  [main] 2017-04-25 10:43:30,084 SigarLibrary.java:57 - Could not initialize SIGAR
library org.hyperic.sigar.Sigar.getFileSystemListNative()[Lorg/hyperic/sigar/FileSystem; 
> INFO  [main] 2017-04-25 10:43:30,084 SigarLibrary.java:185 - Sigar could not be initialized,
test for checking degraded mode omitted.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message