[Orca-users] RE: Orca Startup Problem
alegrand at wallace.com
alegrand at wallace.com
Mon Oct 8 05:16:52 PDT 2001
Bruce,
The Raw Disk code is failing because it does not know who to
recognize you
disk drives. I coded it against a Sparc system using scsi disks. It is
also
having problems recognizing ATA disks in Ultra 5 & Ultra 10 systems. If
you
would run the followin attached code then I will be able to fix it.
Alan
-----Original Message-----
From: Phillip B. Bruce [mailto:pbbruce at mindspring.com]
Sent: Monday, October 08, 2001 1:30 AM
To: orca-users at yahoogroups.com
Cc: alegrand at wallace.com
Subject: Re: [orca-users] Orca Startup Problem
Blair Zajac wrote:
> I think you'll need to work with Alan LeGrand alegrand at wallace dot
> com, who
> wrote the new RAWDISK code, to track this one down.
>
> Best,
> Blair
>
> "Phillip B. Bruce" wrote:
> >
> > Blair Zajac wrote:
> >
> > > I've seen orcallator.se core dump when there is a bad device
> filename
> > > or
> > > filesystem on the system. Next try
> > >
> > > se -d -DWATCH_OS orcallator.se 5
> > >
> > > and save the output. Take a look and see if there's anything that
>
> > > looks
> > > like it would cause a core dump. Send the last couple pages of
> lines
> > > along.
> > >
> > > Blair
> > >
> > > "Phillip B. Bruce" wrote:
> > > >
> > > > Blair Zajac wrote:
> > > >
> > > > > Phillip,
> > > > >
> > > > > Can you email the complete output from running
> start_orcallator?
> > > > >
> > > > > After you do this, try running
> > > > >
> > > > > se -DWATCH_OS orcallator.se 5
> > > > >
> > > > > and see if there's any output. If not, then there's a problem
>
> > > with
> > > > > your
> > > > > installation of SE or a particular issue with orcallator.se on
>
> > > your
> > > > > system.
> > > > > Which OS and hardware are you using?
> > > > >
> > > > > Just ignore orca.state, touching it or doing anything with it
> > > won't
> > > > > fix the
> > > > > issue, it'll just make a warning message go away. There's
> nothing
> > > in
> > > > > there
> > > > > that'll cause Orca to find the files it needs to load.
> > > > >
> > > > > Blair
> > > > >
> > > > > "Phillip B. Bruce" wrote:
> > > > > >
> > > > > > Blair Zajac wrote:
> > > > > >
> > > > > > > Can you put the complete list of commands and error
> messages
> > > from
> > > > > > > running
> > > > > > > start_orcallator? There's not enough information there to
>
> > > work
> > > > > off
> > > > > > > of.
> > > > > > >
> > > > > > > Several questions:
> > > > > > >
> > > > > > > Are you running orcallator as root?
> > > > > > >
> > > > > > > Is /opt a NFS mounted filesystem on this system?
> > > > > > >
> > > > > > > Blair
> > > > > > >
> > > > > > > "Phillip B. Bruce" wrote:
> > > > > > > > Blair,
> > > > > > > >
> > > > > > > > This is what I did so far.
> > > > > > > >
> > > > > > > > 1. stop_orcallator
> > > > > > > >
> > > > > > > > 2. start_orcalltor
> > > > > > > > ./orcallator_running
> > > > > > > >
> > > > > > > > 3. Now in /opt/orca/var/orca/orcallator
> > > > > > > > ./orcallator_running: okieland/percol-2001-10-07 does
> not
> > > exist
> > > > > > > >
> > > > > > > > Keep in mind that I'm so frustrated that I removed
> > > everything
> > > > > from
> > > > > > > the
> > > > > > > > 2.6 version and re-installed.
> > > > > > > > I had to manually do a touch orca.state to get
> orcallator up
> > > but
> > > > >
> > > > > > > still
> > > > > > > > keep running into this problem.
> > > > > > > >
> > > > > > > > This is what OS I'm running which is 2.8
> > > > > > > > uname -a
> > > > > > > > SunOS okieland 5.8 Generic_108529-10 i86pc i386 i86pc
> > > > > > > >
> > > > > > > > #more /etc/release
> > > > > > > > Solaris 8 10/00 s28x_u2wos_11
> INTEL
> > > > > > > > Copyright 2000 Sun Microsystems, Inc. All
> Rights
> > >
> > > > > > > Reserved.
> > > > > > > > Assembled 28 August 2000
> > > > > > > >
> > > > > > > > Now any further suggestion would be appreciated.
> > > > > >
> > > > > >
> > > > > > Blair,
> > > > > >
> > > > > > Orcallator is running as root.
> > > > > > No NFS services.
> > > > > >
> > > > > > This is a standalone system that orca is running on
> what
> > > else
> > > > > do
> > > > > > you need to
> > > > > > know.
> > > > > >
> > > > > > orca -o -v lib/orcallator.cfg
> > > > > > Orca version 0.264 using RRDs version 1.000331 at Sun Oct 7
>
> > > > > 19:17:37
> > > > > > 2001.
> > > > > > /opt/orca/bin/orca: warning: cannot open state file
> > > > > > `/opt/orca/var/orca/rrd/orcallator/orca.state' for reading:
> No
> > > such
> > > > > file
> > > > > > or directory
> > > > > > Creating orca.gif.
> > > > > > Creating rrdtool.gif.
> > > > > > Finding files and setting up data structures at Sun Oct 7
> > > 19:17:37
> > > > > > 2001.
> > > > > > /opt/orca/bin/orca: warning: no files found for `find_files'
> for
> > >
> > > > > `group
> > > > > > orcallator' in `lib/orcallator.cfg'.
> > > > > > RSS VSZ %MEM TIME USER PID COMMAND
> > > > > > 3876 4748 1.6 0:01 root 1263 /usr/bin/perl
> > > > > > Current running time is 0:00 minutes.
> > > > > > /opt/orca/bin/orca: no data files found. Make sure
> `find_files'
> > >
> > > > > > parameter is set properly.
> > > > > >
> > > > > > Again unless I do the following:
> > > > > >
> > > > > > # touch orca.state
> > > > > >
> > > > > > The find_files for group orcallator with no data files
> found. I
> > > have
> > > > >
> > > > > > everything configured correctly.
> > > > > > As I have repeatedly stated that I've have removed and
> started
> > > all
> > > > > over
> > > > > > again and again on this.
> > > > > >
> > > > > > So far I'm not all that impressed at least not with
> installation
> > > and
> > > > >
> > > > > > configuration. Compiling was not
> > > > > > an issue and worked just fine. Also SETOOLS installations
> > > requires
> > > > > that
> > > > > > SEPATH be set. Your only neededing
> > > > > > it for accuracy so the perl can pick up the path in case
> MORONS
> > > who
> > > > > > cannot understand the purpose of environment
> > > > > > variables or even the use LD_LIBRARY_PATH variables. Which
> is a
> > > good
> > > > >
> > > > > > thing to do but a little more work on
> > > > > > your part could have prevented that also.
> > > > > >
> > > > > > You have a good program and I was impressed when 2.6 was
> > > installed
> > > > > and
> > > > > > only had a small issue. It seems like
> > > > > > that is all falling apart since then.
> > > >
> > > >
> > > > Blair,
> > > >
> > > > nice try that didn't work either:
> > > >
> > > > # se -DWATCH_OS ./orcallator.se 5
> > > > Segmentation Fault
> > > >
> > > > So what is next.
> > > >
> >
> > Blair,
> >
> > I did the following:
> >
> > # ls
> > orcallator.se orcallator.se-1.28b7.txt
> orcallator.se.org
> > orcallator.se-1.27.txt orcallator.se-1.29.txt se_debug.txt
> > # se -DWATCH_OS orcallator.se 5
> > Segmentation Fault
> > # ls
> > orcallator.se orcallator.se-1.28b7.txt
> orcallator.se.org
> > orcallator.se-1.27.txt orcallator.se-1.29.txt se_debug.txt
> > # cp orcallator.se-1.29.txt orcallator.se
> > # se orcallator.se 5
> > timestamp locltime DNnsrkcmdit uptime
> > 1002519335 22:35:35 wwwwwwwwwww 54284
> > 1002519340 22:35:40 wwwwwwwwwww 54289
> > ^C#
> >
> > # pwd
> > /opt/RICHPse/orcallator
> >
> > As you see the above is in this directory. If I use the -DWATCH_OS
> it
> > causes the segmentation
> > default. If I don't then it seems to work ok. This tells me the
> problem
> > is how the WATCH_OS
> > is being used.
> >
> > One other thing the orcallator.se.org is what I had as the orginal
> from
> > the SETools Web Site.
> > The orcallator.se-1.29.txt was based on what you had sent me
> tonight. It
> > doesn't matter which
> > one I use. They both seemed to have this problem.
> >
> > The problem seems to be in the USE_RAWDISK routines. I can
> sucessfully
> > use the following:
> >
> > # se -DWATCH_DISK orcallator.se 5
> > timestamp locltime DNnsrkcmdit uptime disk_runp_c0d0
> disk_runp_c0d1
> > disk_runp_c1d0 disk_runp_c1t1d0 disk_runp_fd0 disk_peak disk_mean
> > disk_rd/s disk_wr/s disk_rK/s disk_wK/s
> > 1002520195 22:49:55 wwwwwwwwwww 55144 0.00000
> > 0.00000 0.00000 0.00000 0.00000 0.000
>
> > 0.000 0.0 0.0 0.0 0.0
> > 1002520200 22:50:00 wBwwwwwwwww 55149 0.00000
> > 0.00000 0.00000 0.00000 0.00000 0.000
>
> > 0.000 0.0 0.0 0.0 0.0
> > 1002520205 22:50:05 wwwwwwwwwww 55154 0.00000
> > 0.00000 0.00000 0.00000 0.00000 0.000
>
> > 0.000 0.0 0.0 0.0 0.0
> > ^C# se -DUSE_RAWDISK orcallator.se 5
> > Segmentation Fault
> > #
> >
> > As you see orcallator.se is working to some extent. I figure my
> putting
> > a 0 on USE_RAWDISK will solve the
> > problem for now. I like to know what RAW disk it is looking for or
> if
> > using /dev/rdsk devices besides
> > swap space?
> >
>
> Yahoo! Groups Sponsor
[Image]
>
Alan,
It looks like the RAWDISK code you writen for orcallator has a
problem. I have
3 hard disk in my system which is an Intel system running Solaris
2.8.
I'm running 3.2.1 of SETools. I think you need to put another
condition statement
in your code so it won't crash.
Below is what is happening:
if (RAW_disk_map<1> == <1>)
raw_disk_map()
for(i = <0>
; i<0> < RAW_disk_count<5>; i++)
i = <0>
strcpy(long_name<>, GLOBAL_disk_info[0].long_name<(nil)>)
if (long_name[0]<c> == <99> && strchr(long_name<c0d0>, <115>) ==
<(nil)>)
strcpy(short_name<>, GLOBAL_disk_info[0].short_name<(nil)>)
for(j = <0>
; j<0> < RAW_disk_count<5>; j++)
j = <0>
if (strcmp(RAW_disk[0].short_name[0]<c>, short_name<cmdk0>) == <0>)
strcpy(RAW_disk[0].long_name[0]<c>, long_name<c0d0>)
break;
i++;
strcpy(long_name<c0d0>, GLOBAL_disk_info[1].long_name<(nil)>)
if (long_name[0]<c> == <99> && strchr(long_name<c0d1>, <115>) ==
<(nil)>)
strcpy(short_name<cmdk0>, GLOBAL_disk_info[1].short_name<(nil)>)
for(j = <0>
; j<0> < RAW_disk_count<5>; j++)
j = <0>
if (strcmp(RAW_disk[0].short_name[0]<c>, short_name<cmdk1>) == <0>)
j++;
if (strcmp(RAW_disk[1].short_name[1]<m>, short_name<cmdk1>) == <0>)
strcpy(RAW_disk[1].long_name[1]<0>, long_name<c0d1>)
break;
i++;
strcpy(long_name<c0d1>, GLOBAL_disk_info[2].long_name<(nil)>)
if (long_name[0]<c> == <99> && strchr(long_name<c1t1d0>, <115>) ==
<(nil)>)
strcpy(short_name<cmdk1>, GLOBAL_disk_info[2].short_name<(nil)>)
for(j = <0>
; j<1> < RAW_disk_count<5>; j++)
j = <0>
if (strcmp(RAW_disk[0].short_name[0]<c>, short_name<sd0>) == <0>)
j++;
if (strcmp(RAW_disk[1].short_name[1]<m>, short_name<sd0>) == <0>)
j++;
if (strcmp(RAW_disk[2].short_name[2]<d>, short_name<sd0>) == <0>)
j++;
if (strcmp(RAW_disk[3].short_name[3]<k>, short_name<sd0>) == <0>)
strcpy(RAW_disk[3].long_name[3]<0>, long_name<c1t1d0>)
break;
i++;
strcpy(long_name<c1t1d0>, GLOBAL_disk_info[3].long_name<(nil)>)
if (long_name[0]<c> == <99> && strchr(long_name<c1d0>, <115>) ==
<(nil)>)
strcpy(short_name<sd0>, GLOBAL_disk_info[3].short_name<(nil)>)
for(j = <0>
; j<3> < RAW_disk_count<5>; j++)
j = <0>
if (strcmp(RAW_disk[0].short_name[0]<c>, short_name<cmdk2>) == <0>)
j++;
if (strcmp(RAW_disk[1].short_name[1]<m>, short_name<cmdk2>) == <0>)
j++;
if (strcmp(RAW_disk[2].short_name[2]<d>, short_name<cmdk2>) == <0>)
strcpy(RAW_disk[2].long_name[2]<d>, long_name<c1d0>)
break;
i++;
strcpy(long_name<c1d0>, GLOBAL_disk_info[4].long_name<(nil)>)
Segmentation Fault
As you see you found 3 of disk ok but your code crashes cause it thinks
there is a forth.
This is not a good way to be doing this. I'll give this some thought
tomorrow and hopefully
code this for better.
That is why it is crashing right now.
--
************************************************************
*** Phillip B. Bruce ***
*** http://pbbruce.home.mindspring.com ***
*** pbbruce at mindspring.com ***
*** ***
*** "Have you ever noticed? Anybody going slower than ***
*** you is an idiot, and anyone going faster than you ***
*** is a maniac." - George Carlin ***
************************************************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: disks.se
Type: application/octet-stream
Size: 17578 bytes
Desc: not available
URL: </pipermail/orca-users/attachments/20011008/749c03cf/attachment.obj>
More information about the Orca-users
mailing list