[Orca-users] Segmentation Fault - coredump

[D.C.Lawie]

From: "D.C.Lawie" <duncanl at demon.net>

Hi,

I have been expanding my use of orca to include database monitoring.
Essentially, I have written an oracle equivalent of orcallator, which produces
files with a header line and data lines in the same format.  It is read by two
separate orca processes - one to produce database information, the other to
produce filesystem info.  This is like separating system statistics from disk
statistics, which I have also done.

Now, I have three databases:

rp01 - produces 62 fields per line, with a maximum line length of 717
characters
supp01 - produces 33 fields per line, with a maximum line length of 270
characters
uk01 - produces 66 fields per line, with a maximum line length of 780
characters

supp01 and uk01 work fine.  rp01 works fine on the database statistics, but it
causes orca to coredump on the tablespaces information.

I did some investigation and found the following further information.  If I
reduce the information on database rp01 to 55 fields, it loads OK and when new
information is to be added I get the following error.

/opt/orca/bin/orca: internal error: expecting RRD name
`orcora_rp01_TS.PIN_INDEX_15' but no data loaded from
`/var/orca/orcora/rp01/orcora-2000-01-01.00' at time Sat Jan  1 00:00:00 2000
(946684800).

More fields than that causes a core dump.

Less fields than that works fine.

here are the top two lines of the file
/var/orca/orcora/rp01/orcora-2000-01-01.00 (with a blank line in between for
display purposes)

timestamp locltime started BPrsrlTt bchr dchr memsrt shrdpfree shrdprel wtwl
imml l
cghr lcphr rdospc rdoalloc rbckcntsn recursv shrtblscn prsex chnd freelist
tsmax ts
avg dbsize datasize TS.PIN_DATA_01 TS.PIN_DATA_02 TS.PIN_DATA_03 TS.PIN_DATA_04
TS.
PIN_DATA_05 TS.PIN_DATA_06 TS.PIN_DATA_07 TS.PIN_DATA_08 TS.PIN_DATA_09
TS.PIN_DATA
_10 TS.PIN_DATA_11 TS.PIN_DATA_12 TS.PIN_DATA_13 TS.PIN_DATA_14 TS.PIN_DATA_15
TS.P
IN_DATA_16 TS.PIN_INDEX01 TS.PIN_INDEX02 TS.PIN_INDEX03 TS.PIN_INDEX04
TS.PIN_INDEX
05 TS.PIN_INDEX06 TS.PIN_INDEX07 TS.PIN_INDEX08 TS.PIN_INDEX09 TS.PIN_INDEX_10
TS.P
IN_INDEX_11 TS.PIN_INDEX_12 TS.PIN_INDEX_13 TS.PIN_INDEX_14 TS.PIN_INDEX_15
TS.PIN_
INDEX_16 TS.RBCK TS.SYSTEM TS.TEMP TS.TOOLS TS.USERS

946684800 00:00:00 31-12-1999_11:39:58 bbwbwwRw 99.98 98.34 100.00 88.25 0.33
99.99
 100.00 86.47 90.08 0.00 0.00 0.00 82.17 39.84 0.00 0.00 0.00 97.08 13.26
17408.39
1729.21 95.18 21.70 83.48 79.59 4.92 3.92 4.53 6.46 4.79 6.87 8.93 4.34 14.87
14.87
 97.08 13.39 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00
0.00 0.00 6.00 13.08 0.00 6.41 0.00

My tspaces.cfg file looks pretty standard at the top.  The plot sections are
like this, with a separate section for each TS indicated above.

plot {
title                   %g Tablespace Usage - PIN_DATA_03
source                  orcora
data                    TS.(PIN_DATA_03$)
legend                  PIN_DATA_03
line_type               area
y_legend                % Used
data_min                0
data_max                100
plot_min                0
plot_max                100
rigid_min_max           1
}


Any ideas would be appreciated.

Cheers,
Duncan.

--
D.C. Lawie
duncanl at demon.net
MIS - Demon Internet

"I have an asteroid named after me.  Isaac Asimov's got one
too. It's smaller and more eccentric." -- Arthur C. Clarke 1999



--------------------------- ONElist Sponsor ----------------------------

  Hey Freelancers:  Find your next project through JobSwarm!  
  You can even make money in your sleep by referring friends.
<a href=" http://clickme.onelist.com/ad/jobswarm1 ">Click Here</a>

------------------------------------------------------------------------