Bug 60163

Summary: "bad load average returned" when using ruptime or rup
Product: [Retired] Red Hat Linux Reporter: Johnray Fuller <jrfuller>
Component: piranhaAssignee: Phil Copeland <copeland>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3   
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: 2002-05-01 22:13:42 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:

Description Johnray Fuller 2002-02-21 00:50:20 UTC 
Description of Problem:

When users configure piranha to use rup or ruptime for load balanciing, they get
the following message every X seconds:

"bad load average returned: ha1           up      6:10,     1 user,   load 0.00,
0.02, 0.00 localhost     up      6:12,     3 users,  load 0.00, 0."

If bad load average means the machine is overloaded, it is wrong. If it means it
can't read the values returned, it is worse than wrong, it's dumb.

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

piranha-0.6.0-15

How Reproducible:

Every time...

Steps to Reproduce:
1. start rwhod on *both* the lvs routers and the real servers. 
2. tail -f var/log/messages, select ruptime in the virtual server tab, and     
   restart pulse
3. what the mystical messages scroll across your screen.

Actual Results:

/var/log/messages returns this:

"bad load average returned: ha1           up      6:10,     1 user,   load 0.00,
0.02, 0.00 localhost     up      6:12,     3 users,  load 0.00, 0."


Expected Results:

It should be returning the stats or something instead of indicating a problem.

Additional Information:
	
I have yet to test "uptime" You probably should though since these seem to be
broken.
Comment 1 Johnray Fuller 2002-05-01 22:13:38 UTC 
Is this fixed ???

Please close if it is...

J
Comment 2 Phil Copeland 2002-05-02 06:25:05 UTC 
Sorry, missed that one.
Tim/Jay won't do a respin to pull it in so it'll have to be an errata item (done
as errata already)

Phil
=--=
Comment 3 Phil Copeland 2002-05-02 06:27:08 UTC 
*** Bug 60165 has been marked as a duplicate of this bug. ***