SUMMARY: Weird 'collect' problem

From: Jonathan Williams (jonathw@shubertorg.com)
Date: Tue Nov 12 2002 - 09:54:45 EST


Ok...I received a bunch of emails, all pretty much saying the same thing:

It is a known issue, and is corrected in Patch Kit 5 for 5.1 (and in pk 3 for
5.1a)

Once I install this patch, the version of collect will be:
Imperial:/>collect -V
Collector Version = 2.0.2, Collect Datafile Version = 15, Compiled: Apr 10 2002
Imperial:/>

Thanks to all for the replies.

Jonathan Williams
Unix Systems Administrator
The Shubert Organization, Inc.
----- Original Message -----
From: "Jonathan Williams" <jonathw@shubertorg.com>
To: <tru64-unix-managers@ornl.gov>
Sent: Monday, November 11, 2002 4:26 PM
Subject: Weird 'collect' problem

> Ok. I have a box (ES40, Tru64 5.1, patch 3) on which I want to run "collect"
on
> a continual basis. It was running the other day for about 3 hours, when all
of
> a sudden, the "collect" process jumped up and started chewing up 198.2 % CPU
> usage. The database running on that system didn't care for this at all, so I
> killed the collect process. Then I started it up again a bit later, and then
> about 5 hours later, it did the same thing again. I got the 198.2% from the
> "top" program, as well as the output from a ps -ef|grep collect.
>
> The version of collect that I'm running came with the OS--so I would think it
> should work:
>
> broadway:/>collect -V
> Collector Version = 2.00, Collect Datafile Version = 14, Compiled: Dec 1 2000
> broadway:/>
>
> And the exact command I am running (that someone from this list sent to me):
>
> collect -ol -i60,120 -f /var/adm/collect.dated/collect -H d0:5,3m -W 1h -M
10,15
>
> So that's it. Is this a known problem with a (hopefully) known solution? TIA
>
>
> Jonathan Williams
> Unix Systems Administrator
> The Shubert Organization, Inc.
>
>



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:59 EDT