[
https://issues.apache.org/jira/browse/CASSANDRA-10212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417196#comment-15417196
]
Martin Schröder commented on CASSANDRA-10212:
---------------------------------------------
This actually leads to a non-starting cassandra when one adds the JMX-agent
from prometheus (which uses a port) to the JVM_OPTS in cassandra-env.sh - the
agent then gets started twice and the second start fails because the port is
already claimed by the first agent. And of course there is no output anywhere
when this fails.
> cassandra-env.sh may be sourced twice by debian init script
> -----------------------------------------------------------
>
> Key: CASSANDRA-10212
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10212
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
> Reporter: Enrico Canzonieri
> Assignee: Michael Shuler
> Priority: Minor
>
> It seems that when cassandra is run as a service using the init script the
> {{/etc/cassandra/cassandra-env.sh}} file is sourced twice.
> This file is sourced the first time in the
> [init|https://github.com/apache/cassandra/blob/trunk/debian/init] script. The
> init script then executes
> [{{/usr/sbin/cassandra}}|https://github.com/apache/cassandra/blob/trunk/bin/cassandra],
> the latter eventually does source {{cassandra-env.sh}} as
> {{$CASSANDRA_CONF/cassandra-env}}.
> CASSANDRA_CONF is finally defined in
> [{{cassandra.in.sh}}|https://github.com/apache/cassandra/blob/trunk/debian/cassandra.in.sh]
> as {{/etc/cassandra}}.
> I guess in this case the init script should not source {{cassandra-env}} at
> all.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
