You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Alexander Lorenz-Alten (Reopened) (JIRA)" <ji...@apache.org> on 2012/03/07 19:44:58 UTC
[jira] [Reopened] (FLUME-864) Can not start a master again after a
crash of the host
[ https://issues.apache.org/jira/browse/FLUME-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Lorenz-Alten reopened FLUME-864:
------------------------------------------
> Can not start a master again after a crash of the host
> ------------------------------------------------------
>
> Key: FLUME-864
> URL: https://issues.apache.org/jira/browse/FLUME-864
> Project: Flume
> Issue Type: Bug
> Affects Versions: v0.9.3
> Environment: Linux
> Reporter: Fabrice Larcher
> Priority: Minor
>
> I am using the version v0.9.3-cdh3u0.
> When the service 'flume-master' is not stopped gracefully (crash of the host), the file /tmp/flumemaster.pid do not get deleted. Then, it is not possible to start the master service if this file is not deleted manually.
> The related check takes place in the file ${FLUME_HOME}/bin/flume at line 248 using the variable $MASTERPID that contains the path to the considered PID file.
> Perhaps this issue can be related to FLUME-191 and FLUME-387.
--
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