cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Petrov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13334) Cassandra fails to start with LOCAL_JMX set to false
Date Tue, 21 Mar 2017 14:44:41 GMT

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

Alex Petrov commented on CASSANDRA-13334:
-----------------------------------------

Cassandra requires proper security if you enable non-local JMX connection, you'll have to
provide a {{jmxremote.passwd}}. You can find more information for example [here|https://docs.datastax.com/en/cassandra/3.0/cassandra/configuration/secureJmxAuthentication.html]
(I just picked the first google search result that was relevant, there're other guides online
as well).

> Cassandra fails to start with LOCAL_JMX set to false
> ----------------------------------------------------
>
>                 Key: CASSANDRA-13334
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13334
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Lifecycle
>         Environment: cassandra 3.0.9
> ubuntu 16.04
> ec2
>            Reporter: Andres March
>             Fix For: 3.0.x
>
>
> There seems to be some changes lately with CASSANDRA-11540 and CASSANDRA-11725 that changes
how remote jmx set up works.  
> Just setting LOCAL_JMX=false causes cassandra to fail to start on ubuntu in ec2.  Worse
yet the initd script says it has started ok and there are no logs whatsoever about an error.
> This is reproducible 100% of the time.  Changing various settings like the port, jmx
remote hostname, etc... didn't change anything.  I would attach some logs but there aren't
any.



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

Mime
View raw message