[
https://issues.apache.org/jira/browse/CASSANDRA-8594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278742#comment-14278742
]
Cyril Scetbon commented on CASSANDRA-8594:
------------------------------------------
[~JoshuaMcKenzie] you're right, the line you referenced creates the pid.
However, I just discovered that my debian script is using the foreground option
:
{code}
( nohup start-stop-daemon -S -c cassandra -a /usr/sbin/cassandra -p "$PIDFILE"
--umask "30" -- \
-f -p "$PIDFILE" -H "$heap_dump_f" -E "$error_log_f" >
$CASSANDRA_LOG_DIR/output.log 2>&1 || return 2 ) &
{code}
and that's why the pid is not created. I need to track why mine is using this
option and where it comes from. Thank you guys
> pidfile is never filled by cassandra
> ------------------------------------
>
> Key: CASSANDRA-8594
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8594
> Project: Cassandra
> Issue Type: Bug
> Reporter: Cyril Scetbon
> Assignee: Cyril Scetbon
> Fix For: 2.0.13
>
>
> The pid file is never filled by cassandra. there is only a File object that
> is created with [those
> lines|https://github.com/cscetbon/cassandra/blob/cassandra-2.0.10/src/java/org/apache/cassandra/service/CassandraDaemon.java#L498-L501]
> Here is a
> [fix|https://github.com/cscetbon/cassandra/commit/d0c5e0c9be00e48e6d0cd0de208c53274f1919c0.patch]
> that writes the current PID into the pidfile
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
