You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcos Dione (JIRA)" <ji...@apache.org> on 2012/06/26 11:53:44 UTC
[jira] [Created] (CASSANDRA-4376) fails to run and/or log a message
when JMX access files do not exist
Marcos Dione created CASSANDRA-4376:
---------------------------------------
Summary: fails to run and/or log a message when JMX access files do not exist
Key: CASSANDRA-4376
URL: https://issues.apache.org/jira/browse/CASSANDRA-4376
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.1.1
Reporter: Marcos Dione
Priority: Minor
You can specify in the cassandra-evn.sh file the settings for JMX access such as:
JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.access.file=/etc/cassandra/jmx_acc"
JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.password.file=/etc/cassandra/jmx_pwd"
If any of those files doesn't exist, cassandra fails to run (most possibly a good course of action) but doesn't log anything in the system.log, leaving the admin wondering what's wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CASSANDRA-4376) fails to run and/or log a
message when JMX access files do not exist
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-4376.
---------------------------------------
Resolution: Not A Problem
the output log is stdout/stderr from before log4j is initialized, and/or libraries that don't use log4j
> fails to run and/or log a message when JMX access files do not exist
> --------------------------------------------------------------------
>
> Key: CASSANDRA-4376
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4376
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.1
> Reporter: Marcos Dione
> Priority: Minor
>
> You can specify in the cassandra-evn.sh file the settings for JMX access such as:
> JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.access.file=/etc/cassandra/jmx_acc"
> JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.password.file=/etc/cassandra/jmx_pwd"
> If any of those files doesn't exist, cassandra fails to run (most possibly a good course of action) but doesn't log anything in the system.log, leaving the admin wondering what's wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4376) fails to run and/or log a
message when JMX access files do not exist
Posted by "Marcos Dione (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401274#comment-13401274 ]
Marcos Dione commented on CASSANDRA-4376:
-----------------------------------------
In fact the error is logged in the output log:
Error: Password file not found: /etc/cassandra/jmx_pwd
Service exit with a return value of 1
is there a reason there are two logs?
> fails to run and/or log a message when JMX access files do not exist
> --------------------------------------------------------------------
>
> Key: CASSANDRA-4376
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4376
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.1
> Reporter: Marcos Dione
> Priority: Minor
>
> You can specify in the cassandra-evn.sh file the settings for JMX access such as:
> JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.access.file=/etc/cassandra/jmx_acc"
> JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.password.file=/etc/cassandra/jmx_pwd"
> If any of those files doesn't exist, cassandra fails to run (most possibly a good course of action) but doesn't log anything in the system.log, leaving the admin wondering what's wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira