Bug 488013 - ldirectord leaves checker children behind when stopping
ldirectord leaves checker children behind when stopping
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: ipvsadm (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Marek Grac
Cluster QE
Depends On:
  Show dependency treegraph
Reported: 2009-03-02 02:02 EST by Amos Shapira
Modified: 2009-04-16 18:57 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-03-02 07:44:15 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch for ldirectord (564 bytes, patch)
2009-03-02 02:02 EST, Amos Shapira
no flags Details | Diff

  None (edit)
Description Amos Shapira 2009-03-02 02:02:17 EST
Created attachment 333689 [details]
patch for ldirectord

Description of problem:
We noticed that whenever the ldirectord node is switch from "primary" to "secondary", it leaves behind fork(2)'ed children which keep probing the real server, loading the real servers.

Version-Release number of selected component (if applicable):

How reproducible:
Steps to Reproduce:
1. create a hearbeat cluster with ldirectord.
2. configure ldirectord to monitor real servers via tcp (e.g. apache)
3. force take-over between the primary and the secondary heartbeat nodes

Actual results:
ldirectord child processes are left behind, with init (process 1) as a parent.

Expected results:
child processes should exit when the ldirectord is stopped by heartbeat

Additional info:
Attached is a simple patch. I'm not 100% it's the correct way to do it but it seems to work for us.
I use CentOS 5.2 on x86_64 xen DomU.
Comment 1 Marek Grac 2009-03-02 07:44:15 EST
ldirectord is a product of Novell/SuSe :)

Note You need to log in before you can comment on or make changes to this bug.