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
Created attachment 73945 [details] Patch assigning default load_monitor (rup) after initialization and after getopt stuff
Created attachment 103366 [details] change default load command to none
"rup" isn't really a good default since it will cause this problem if things aren't set up just right.
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
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