falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pallavi Rao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-442) overwriting of PID while multiple falcon start
Date Mon, 18 Jan 2016 04:41:39 GMT

    [ https://issues.apache.org/jira/browse/FALCON-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15104161#comment-15104161

Pallavi Rao commented on FALCON-442:

If the PID file was explicitly removed, all bets are off. Anyway, looks like this was reported
against a much older version of Falcon and may have gotten fixed subsequently. Suggest we
close this JIRA for now and re-open with additional info, if anyone faces similar issue.

> overwriting of PID while multiple falcon start 
> -----------------------------------------------
>                 Key: FALCON-442
>                 URL: https://issues.apache.org/jira/browse/FALCON-442
>             Project: Falcon
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 0.4, 0.5
>         Environment: production 
>            Reporter: Samarth Gupta
>            Assignee: Praveen Adlakha
> if falcon-start command is run on a already running falcon server, it goes and updates
the PID that was stored during the previous falcon-star, however falcon keep running with
the original PID.  
> Due to this , when falcon-stop is run we get a missing process error, similar to below.

> {code}
> /usr/lib/falcon/falconServer/bin/service-stop.sh: line 36: kill: (19518) - No such process
> {code}

This message was sent by Atlassian JIRA

View raw message