Project

General

Profile

Bug #18724

dynflow_executor creates wrong pid file

Added by Lars Wagner over 4 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Issue

On ubuntu 14.04 with foreman-tasks-0.8.2

service ruby-foreman-tasks start 

creates the following pid files:
[root@mysrv:~]↥ 10 # ls /usr/share/foreman/tmp/pids/
dynflow_executor_monitor.pid
dynflow_executor_num0.pid

The num0 is wrong.

The rc-Script looks for the right pid-files (outputted pid-files):

[root@mysrv:~]↥ 130 # service ruby-foreman-tasks status
dynflow_executor is not running.
/usr/share/foreman/tmp/pids/dynflow_executor.pid
dynflow_executor_monitor is  * foreman-tasks is running
running.
/usr/share/foreman/tmp/pids/dynflow_executor_monitor.pid

Workaround

Change line 121 in /etc/init.d/ruby-foreman-tasks to:

status_of_one $FOREMAN_PID_DIR/dynflow_executor_num0.pid

History

#1 Updated by Lars Wagner over 1 year ago

  • Status changed from New to Resolved

Close - as this problem has been solved a long time ago.

Also available in: Atom PDF