[Orca-users] Re: Orcallator dumping core

[Patrick Aland]

Ok, I'm running 
se - Version 3.1 (pre-fcs) (10:39 AM 03/31/99) for sparcv9 SunOS 5.7
I'm using the orcallator.se that came with the .26 tar

After running se in debug mode twice it appears to be dieing during one of the filesystem checks, 
Run 1:
if (last<120> == <0>)
if (fgets(buf<tophat:/export/home1/kharman>, sizeof(buf<tophat:/export/home1/kharman>), input<4296373264>) == <(nil)>)
strcpy(strchr(buf<tophat:/export/home1/abaker\t/home/abaker\tnfs\t>, <10>), <>)

Run 2:
if (last<120> == <0>)
if (fgets(buf<tophat:/export/home2/jpim>, sizeof(buf<tophat:/export/home2/jpim>), input<4296373264>) == <(nil)>)
strcpy(strchr(buf<tophat:/export/home1/mdemurga\t/home/mdemurga\tnfs\tdev=313c5>, <10>), <>)

Those are the last 3 lines of output from the two runs before if segfaulted.

Running it through truss we get:
statvfs("/var/log", 0x10019E300)                = 0
statvfs("/var/news", 0x10019E300)               = 0
statvfs("/var/mail", 0x10019E300)               = 0
statvfs("/export", 0x10019E300)                 = 0
read(9, 0x1007595C4, 8192)                      = 0
    Incurred fault #6, FLTBOUNDS  %pc = 0xFFFFFFFF7EB40070
      siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
    Received signal #11, SIGSEGV [default]
      siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
        *** process killed ***

As I said in my original post the timing where completely different for all three.
Run 1 went almostand hour, Run 2 about 3 minutes, Run 3 about 25.

As far as PCP goes I don't believe it has the ability to monitor solaris simply because it uses the /proc filesystem. It doesn however have a plugin architecture to write new namespaces (some have been written to monitor Cisco equip, orcale db's, etc) so it might be possible to extend it. I have found that I can't get all the stats from it that se can get and unfortunately a kernel patch is required to get stats on a partition level basis.

--Patrick


On Wed, Jan 24, 2001 at 02:55:41PM -0800, Blair Zajac wrote:
> First, which version of SE and orcallator.se are you using?  To track
> this down, I'd do two things.  Run it with the -d SE flag and then
> under truss (probably separately since there will be a lot of output):
> 
> se -d -DWATCH_OS orcallator.se 5
> truss se -DWATCH_OS orcallator.se 5
> 
> Let's see what is causing the failure.
> 
> I haven't heard of PCP but it looks interesting.  Could it be
> packaged so that Orca would have an OS independent data collector?
> This may be similar to libgtop which I was hoping would provide
> an OS independent data collector but there's been no work on.
> 
> Regards,
> Blair
> 

-- 
------------------------------------------------------------
 Patrick Aland                          paland at stetson.edu
 Network Administrator                  Voice: 904.822.7217
 Stetson University                     Fax: 904.822.7367
------------------------------------------------------------