[Orca-users] Problem with Multiple Disk Run Percent Graphs showing and a quest ion

[O'Neill, Sean]

First, I'm running the most current ORCA/RRD configuration available with S= E
v3.2 on Solaris 8 system.

Long email but please read ... this is REALLY getting frustrating.

I'm asking this question hoping to get rid of these annoying multiple and usually incorrect Disk Run Percent graphs.  I've noticed the following= which
looking into this:

- I'm using SDS on my system and for a long while the MD devices were being=
graphed.  I stopped ORCA for a while doing something and restarted it = a
while later.  The MD devices weren't showing up anymore in the graphs.=   Only
the cXtXdX devices were.

- At midnight, the data files rolled over and the multiple Run Percent
graphs showed up.  This time the MD devices DID show up in one of the = graphs
but the data is wrong.

So I started poking around.

- When ORCA restarts it apparently puts a new "header" line in th= e
orca/orcallator/<hostname>/percol-<date> file.  By header = I mean:

timestamp locltime DNnsrkcmdit   uptime  usr%  sys%&nbs= p; wio% idle%  1runq ....
<and lots more>

It also does this when it rolls over to the next day at midnight and create= s
a new data file.

- I noticed that in the file for today that was created last night the MD devices are NOT showing at all in the headers.  Only the cXtXdX device= s are.

- I saw that the "headers" are mirrored in the
orca/rrd/orcallator/<hostname>/orca.state file used by RRD.  Sam= e problem
entries.  I noticed that most entires look this this:

/usr/local/orca/var/orca/orcallator/chivas/percol-2001-06-22.bz2 993272102<= BR> 995577819 8388687 80022 25799 993272102
USETHISFILE/usr/local/orca/var/orca/orcallator/chivas/percol-2001-06-21.bz2=

which I think means use the "headers" (USETHISFILE) found for thi= s entry.

So I'm pretty sure the problem isn't with RRD and the graphs.  Its the= data
being fed to RRD.

The last time the MD devices were showing up in the data correctly was in the percol-2001-07-18 data file.  I had stopped and restarted ORCA on = the
19th for something and that's when this problem came up.  I tried &quo= t;fixing"
this by deleting the percol-2001-07-19 data file completely.  ORCA rec= reated
the percol-2001-07-19 data file Did this but the problem was still.  O= nly in
this fashion:

- The percol-2001-07-19 and percol-2001-07-20 data files have NO references=
to MD devices anywhere in the headers yet a graph (one of several) is being=
generated with MD name references in it even though the data is crap.

So why isn't ORCA picking up my MD devices anymore ?  I assume this is= sue
isn't specific to MD devices.  This is probably happening for the othe= r
devices as well. 

I tried deleting the percol-2001-07-20 data file as well as the entry for 2001-07-20 from the orca.state file.  My MD devices still were not pic= ked
up.

Any ideas out there ??

..................................................
....... ..-=A0-.=A0..=A0-..-=A0.-.=A0..-=A0.-..=A0.=A0...=A0........
.--=A0..=A0-.=A0-..=A0---=A0.--=A0...=A0-..=A0.-.=A0---=A0---=A0.-..=A0...<= BR>
Sean O'Neill
Senior UNIX Systems Engineer / Project Leader
Global Services
Commerce One

1100 West Street
Laurel, MD 20707
301 939 1213 voice mail
301 953 2368 fax
301 526 1514 cell
sean.oneill at commerceone.com
www.commerceone.com

NOTICE: This e-mail message is intended for the use of the individual
or entity to which it is addressed, and may contain information that is
privileged, confidential and exempt from disclosure under applicable
law.  If the reader of this message is not the intended recipient, you=
are hereby notified that any dissemination, distribution or copying of
this communication is strictly prohibited.  If you have received this<= BR> communication in error, please notify us immediately by telephone and
return the original message to us at the above address via the e-mail.
Thank you.


o.com/info/terms/">Yahoo! Terms of Service.