falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepak Barr (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-442) overwriting of PID while multiple falcon start
Date Sun, 17 Jan 2016 16:47:39 GMT

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

Deepak Barr commented on FALCON-442:

One possibility that can cause this issue - 

1. Run falcon-start
2. remove falcon.pid from $FALCON_HOME/logs directory
3. Run falcon-start again. This command will not be able to start to falcon server but will
create falcon.pid with new PID.
4. Now, if you do falcon-stop. It will try to stop the PID in falcon.pid resulting in "No
such process" error". 

Not sure if falcon.pid was removed ( step 2) before starting falcon again when samarth saw
this 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