Here it is, Robert, thanks!
https://issues.apache.org/jira/browse/CASSANDRA-9884
On Thu, Jul 23, 2015 at 2:13 PM, Robert Coli wrote:
> On Thu, Jul 23, 2015 at 12:40 PM, Carlos Scheidecker
> wrote:
>
>> After updating to Cassandra 2.2.0 from 2.1.6 I am having SSL issues:
>&
0]
at
org.apache.cassandra.net.OutboundTcpConnection.run(OutboundTcpConnection.java:218)
~[apache-cassandra-2.2.0.jar:2.2.0]
On Thu, Jul 23, 2015 at 2:13 PM, Robert Coli wrote:
> On Thu, Jul 23, 2015 at 12:40 PM, Carlos Scheidecker
> wrote:
>
>> After updating to Cassandra 2.2.0 from 2.1.6 I am having SSL issues:
Hello all,
After updating to Cassandra 2.2.0 from 2.1.6 I am having SSL issues:
My JVM is java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
Ubuntu 14.04.2 LTS is on all nodes, they are the same.
Below i
Hello all,
After updating to Cassandra 2.2.0 from 2.1.6 I am having SSL issues:
My JVM is java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
Ubuntu 14.04.2 LTS is on all nodes, they are the same.
Below i
s clear that you have an incorrect server_encryption_options:
> cipher_suites: configuration.
>
> --
> Kind regards,
> Michael
>
> On 07/22/2015 06:33 PM, Carlos Scheidecker wrote:
>
>> Thanks for the reply, Michael!
>>
>> Yes, I did followed the upgrade nodes.
AC1
192.168.1.34=DC1:RAC1
# default for unknown nodes
default=DC1:RAC1
On Wed, Jul 22, 2015 at 5:23 PM, Michael Shuler
wrote:
> On 07/22/2015 04:45 PM, Carlos Scheidecker wrote:
>
>> I have a 4 node Cassandra system running on 4 Ubuntu boxes. After
>> updating to Cassandra 2.
All,
I have a 4 node Cassandra system running on 4 Ubuntu boxes. After updating
to Cassandra 2.2.0 and keeping the same cassandra.yaml file, the nodes
cannot see each other.
When I do a nodetool status it only reports as being up the machine where I
had issue the command.
In other words, all the
All,
I have a 4 node Cassandra system running on 4 Ubuntu boxes. After updating
to Cassandra 2.2.0 and keeping the same cassandra.yaml file, the nodes
cannot see each other.
When I do a nodetool status it only reports as being up the machine where I
had issue the command.
In other words, all the
why I sent the email.
Nonetheless, here is the answer to it in case someone got stuck on the
issue.
On Sat, Sep 20, 2014 at 9:28 PM, Carlos Scheidecker
wrote:
> Hello all,
>
> I have the following table:
>
> CREATE TABLE userprincipal (
> userid timeuuid,
&g
Hello all,
I have the following table:
CREATE TABLE userprincipal (
userid timeuuid,
username varchar,
hashedpassword blob,
authorities set,
accountnonexpired boolean,
accountnonlocked boolean,
credentialsnonexpired boolean,
enabled boolean,
PRIMARY KEY(username)
);
Now, I have
commit/420c68511417e917925898e8c0637c9df3e317b0
>
>
> On Fri, Jul 11, 2014 at 10:49 PM, Carlos Scheidecker
> wrote:
>
>> Mark,
>>
>> Sure!
>>
>> Actually it might be a package problem. Not installing Cassandra by hand
>> as I need to test it acro
andra/blob/trunk/bin/cassandra.in.sh
>
> I am unsure why you are seeing jamm-0.2.5.jar in your cassandra.in.sh
> file if you have taken down a fresh 2.1.0-rc, can you give any further
> information?
>
>
> Mark
>
>
> On Fri, Jul 11, 2014 at 9:49 PM, Carlos Scheidecker
Hello all,
Probably not here that I should submit it, but I have been testing
Cassandra 2.1.0 for quite a while.
I have tried to subscribe to the dev list as well.
Even now on rc3, there is still a small bug on cassandra.in.sh used, among
others, for nodetool settings.
The error is that it is s
a certificate issue, debugging it I was able to find it.
The longer you do things, the longer you are prone to errors.
cheers
On Thu, Jun 19, 2014 at 3:20 PM, Carlos Scheidecker
wrote:
> Hello,
>
> I am using Cassandra 2.1.0-rc1 and trying to set up internode encryption.
>
&
Hello,
I am using Cassandra 2.1.0-rc1 and trying to set up internode encryption.
Here's how I have generated the certificates and keystores:
keytool -genkeypair -v -keyalg RSA -keysize 1024 -alias node1 -keystore
node1.keystore -storepass 'mypassword' -dname 'CN=Development' -keypass
'mypassword
15 matches
Mail list logo
