cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6101) Debian init script broken
Date Thu, 03 Oct 2013 15:01:52 GMT


Eric Evans commented on CASSANDRA-6101:

bq. Not really important, but status isn't working with this patch..

I'm not seeing that [~pieterc]; Which patch are you referring to, [6101.txt|]
or [6101-classpatch.patch|]?

I wouldn't be surprised at this point to find there are more bugs with this, but only [6101.txt|]
should have had any impact on this, and it is definitely a change for the better.

When you see this error, does a PID file exist at {{/var/run/cassandra/}}?  If
so, what are the contents of the file?  Is Cassandra running, and if so, what is its PID (hint:
try {{pgrep -f CassandraDaemon}})?

Could you attach the output of {{sh -x /etc/init.d/cassandra status}}?

> Debian init script broken
> -------------------------
>                 Key: CASSANDRA-6101
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Anton Winter
>            Assignee: Eric Evans
>            Priority: Minor
>         Attachments: 6101-classpath.patch, 6101.txt
> The debian init script released in 2.0.1 contains 2 issues:
> # The pidfile directory is not created if it doesn't already exist.
> # Classpath not exported to the start-stop-daemon.
> These lead to the init script not picking up jna.jar, or anything from the debian EXTRA_CLASSPATH
environment variable, and the init script not being able to stop/restart Cassandra.

This message was sent by Atlassian JIRA

View raw message