You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Andres March (JIRA)" <ji...@apache.org> on 2017/05/23 20:45:04 UTC
[jira] [Updated] (CASSANDRA-13334) Cassandra fails to start with
LOCAL_JMX set to false
[ https://issues.apache.org/jira/browse/CASSANDRA-13334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andres March updated CASSANDRA-13334:
-------------------------------------
Reproduced In: 3.9 (was: 3.0.9)
Fix Version/s: (was: 3.0.x)
3.11.0
> 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.11.0
>
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org