[jira] [Created] (OODT-765) Stale cas.workflow.pid PID files should be removed or set to blank

["Sabarish Venkatraman (JIRA)" <ji...@apache.org>]

Sabarish Venkatraman created OODT-765:
-----------------------------------------

             Summary: Stale cas.workflow.pid PID files should be removed or set to blank
                 Key: OODT-765
                 URL: https://issues.apache.org/jira/browse/OODT-765
             Project: OODT
          Issue Type: Improvement
          Components: file manager, resource manager, workflow manager
    Affects Versions: 0.7
         Environment: Ubuntu 14.04 LTS - 32 bit
            Reporter: Sabarish Venkatraman
            Priority: Minor


$OODT_HOME/filemgr/run - Contains PID of filemanager
$OODT_HOME/resmgr/run - Contains PID of resourcemanager
$OODT_HOME/workflow/run - Contains PID of workflowmanager

The PIDs are stored in cas.filemgr.pid when these managers are started.

Sometimes, some of these managers might not launch fully due to some internal exceptions, after a PID had been written to these files.

During the subsequent launch, if a PID is already present in the file, it fails to launch the filemgr/workflow manager/resource mgr.

Sample filemgr launch issue:
root@ubuntu:/home/user/Desktop/project2/oodt-deploy/filemgr/bin# ./filemgr start
PID file (/home/user/Desktop/project2/oodt-deploy/filemgr/run/cas.filemgr.pid) found. Is File Manager still running? Start aborted.

The stale process ids stored in the files should be handled.

Fix:
Invalidate the contents of the file by setting it to blank. (or)
Deleting the file upon process termination or during manager launch failure.

Temporary fix:
Delete the cas.workflow.pid file manually and then start the appropriate managers.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)