Bug 73074

Summary: nanny crashing when no load_monitor specified
Product: [Retired] Red Hat Linux Reporter: Sébastien BONNET <sbt>
Component: piranhaAssignee: Mike McLean <mikem>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: lhh
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-11-12 21:38:54 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:
Bug Depends On:    
Bug Blocks: 131576    
Attachments:
Description Flags
Patch assigning default load_monitor (rup) after initialization and after getopt stuff
none
change default load command to none none

Description Sébastien BONNET 2002-08-30 12:47:03 UTC 
Description of Problem:
nanny crashes just after the initialization when the config file does not 
specify any load_monitor.

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

How Reproducible:
Anytime. Edit your lvs.cf file and remove all load_monitor.
Watch out nanny processes (or logs) and noticed than nannies are spawned very 
often.

Actual Results:
As nanny crashes, lvs/fos thinks the realserver is down and thus takes 
inappropriate mesures.

Expected Results:
nanny should stay alive
Comment 1 Sébastien BONNET 2002-08-30 12:50:35 UTC 
Created attachment 73945 [details]
Patch assigning default load_monitor (rup) after initialization and after getopt stuff
Comment 4 Mike McLean 2004-09-01 19:56:05 UTC 
Created attachment 103366 [details]
change default load command to none
Comment 5 Mike McLean 2004-09-01 20:00:42 UTC 
"rup" isn't really a good default since it will cause this problem if
things aren't set up just right.
Comment 8 John Flanagan 2004-12-13 21:23:54 UTC 
An errata has been issued which should help the problem 
described in this bug report. This report is therefore being 
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, 
please follow the link below. You may reopen this bug report 
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2004-469.html
Comment 9 John Flanagan 2004-12-21 01:26:14 UTC 
An advisory has been issued which should help the problem 
described in this bug report. This report is therefore being 
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, 
please follow the link below. You may reopen this bug report 
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2004-470.html