We're just running the NT client, I have enough trouble getting the NT admins to just install that, let alone anything else. It probably is the memory size that's causing problems. Here's a sample of the return from the cpu test:

Tue Jul 19 14:44:37 CDT 2005 [ANANKE] up: 83 days, 1 users, 40 procs, load=1%, PhysicalMem: 3840MB(23%)

Memory Statistics Total Physical memory: 4025925632 bytes (3.75GB) Available Physical memory: 3102130176 bytes (2.89GB) Total PageFile size: 4294967295 bytes (4.00GB) Available PageFile size: 4294967295 bytes (4.00GB) Total Virtual memory size: 2147352576 bytes (2.00GB) Available Virtual memory size: 2119045120 bytes (1.97GB)

Most active processes 00.81% tomcat5 (0x190 [400]) 00.03% System (0x4 [4]) 00.02% winlogon (0x2ac [684]) 00.02% Rtvscan (0x8a8 [2216]) 00.00% VxSvc (0x918 [2328]) 00.00% svchost (0x444 [1092]) 00.00% StarbaseServer (0x13d0 [5072]) 00.00% sqlservr (0x608 [1544]) 00.00% csrss (0x294 [660])

Thanks, Larry Barber

On Tue, 2005-07-19 at 14:42 -0500, henrik at hswn.dk wrote:

On Tue, Jul 19, 2005 at 03:28:29PM -0400, Larry.Barber at usda.gov wrote:

...

I just noticed that all the memory trending graphs for Windows machines are broken. They just show zero's all across the board. Is this a known problem, or is something broken in my setup?

Do you have the bb-memory extension installed on your Windows boxes, or just the BBNT client ?

If you dont know - is there a "memory" column for these boxes, or
only the "cpu" column ? bb-memory generates a "memory" column, the standard BBNT client does not.

I suspect it's the BBNT client that is feeding your memory graphs. It has some problems with large-memory systems, but it could also be a bug in Hobbit. Please send me the output from the "cpu" status on one of these boxes.

Regards, Henrik

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk