Bug 488013

Summary: ldirectord leaves checker children behind when stopping
Product: Red Hat Enterprise Linux 5 Reporter: Amos Shapira <amos.shapira>
Component: ipvsadmAssignee: Marek Grac <mgrac>
Status: CLOSED NOTABUG QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 5.2CC: cluster-maint
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-03-02 12:44:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch for ldirectord none

Description Amos Shapira 2009-03-02 07:02:17 UTC
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):
heartbeat-ldirectod-2.1.3-3

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 12:44:15 UTC
ldirectord is a product of Novell/SuSe :)