[
https://issues.apache.org/jira/browse/CASSANDRA-13334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021830#comment-16021830
]
Andres March commented on CASSANDRA-13334:
------------------------------------------
The issue isn't that it doesn't start if there are other required settings.
It's that it doesn't print a useful error. When I changed the logging to debug
on everything, I was able to trace the error. Unfortunately, that was so long
ago that I don't remember the cause. If I revisit, I'll note the error and
submit a patch. The init script should fail with an error logged.
> 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: [email protected]
For additional commands, e-mail: [email protected]
