[Orca-users] Orcallator problem on Solaris 10 domain
J S
js.tech.mailer at gmail.com
Mon Nov 27 13:58:07 PST 2006
/opt/RICHPse/orcallator/orcallator.se
#define MAX_RAWDISKS 1024
RawDisk RAW_disk[MAX_RAWDISKS];
int RAW_disk_map=0;
int RAW_disk_count=0;
double RAW_disk_lastupdate;
On 11/20/06, David Michaels <dragon at raytheon.com> wrote:
>
> Looks like there's an array that needs its size increased. I remember
> seeing a similar error back in 0.27 on Solaris 8 when I had more disks
> than MAX_RAWDISKS. I don't see a MAX_TAPES equivalent, so it must be using
> the RAWDISKS setting.
>
> Mine is set to 1024 in orcallator.se -- what's yours set to?
>
>
> J S wrote:
>
>
> I should mentioned that a backup server that I'm upgrading orca-0.27 to
> r529 snapshot is getting a new segfault error using the method I describe
> below. It fails while statting /dev/rmt devices.
> truss /opt/RICHPse/bin/se -DWATCH_OS -I/usr/local/lib/SE/3.4
> /usr/local/lib/orcallator.se
>
> <...>
> ctl(4, KSTAT_IOC_READ, "st4,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st9,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st5,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st6,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st7,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st10,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st0,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st11,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st1,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st12,err") = 1117
> readlink("/dev/rmt/13", "
> ../../devices/pci at 9,600000/fibre-channel at 2/fp at 0,0/st at w2002006045170724,2:",
> 256) = 73
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st8,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st4,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st9,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st5,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st6,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st7,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st10,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st0,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st11,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st1,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st12,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st2,err") = 1117
> ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1117
> ioctl(4, KSTAT_IOC_READ, "st13,err") = 1117
> Incurred fault #6, FLTBOUNDS %pc = 0xFFFFFFFF7DF00C38
> siginfo: SIGSEGV SEGV_MAPERR addr=0xFFFFFFFF7EE06000
> Received signal #11, SIGSEGV [default]
> siginfo: SIGSEGV SEGV_MAPERR addr=0xFFFFFFFF7EE06000
>
>
>
> On 11/3/06, J S <js.tech.mailer at gmail.com> wrote:
> >
> >
> > I'm having success using the following method.
> >
> > Install Sun Engineer Toolkit (RICHPse) 3.4+
> >
> > Copy /export/admin/orca/diskinfo.se.Sol10.patched to
> > /opt/RICHPse/include/diskinfo.se
> > Copy /export/admin/orca/orcallator.se.SE.Sol10.patched to
> > /opt/RICHPse/orcallator/orcallator.se
> > chgrp sys /opt/RICHPse/bin/se.sparcv9
> >
> >
> > Install SUNWspro into /opt
> >
> > Ensure the path order, and definitely add pod2man in your path.
> > export PATH=$
> > PATH:/opt/SUNWspro/bin:/usr/ccs/bin:/usr/sfw/bin:/usr/perl5/5.8.4/bin
> >
> > Copy orca-snapshot-r529.tar.bz2 or above into /export/install (install
> > dir)
> >
> > ./configure --with-html-dir=/usr/local/orca
> >
> > make
> > make install
> > make orcallator_run_at_boot
> >
> > test the startup by running /usr/local/bin/start_orcallator
> >
> > if it starts without segfaulting, you're fine.
> >
> >
> >
> > =======================================================
> >
> > Changes to /opt/RICHPse/include/diskinfo.se
> >
> > for (ld = readdir(dirp); ld != 0; ld = readdir(dirp)) {
> > // grow the array if needed
> > if (count == GLOBAL_diskinfo_size) {
> > GLOBAL_diskinfo_size += 4;
> > GLOBAL_disk_info = renew GLOBAL_disk_info[GLOBAL_diskinfo_size];
> >
> > }
> > // 09-12-2005 Carl Hack to stop segmentation faults - must be a bug
> > in readdir -
> > if (ld > 18446744071543217903) {
> > continue;
> > }
> > // get the segmentation fault here when ld is >
> > 18446744071543217903
> > // jsutch 20060805
> >
> > dp = *((dirent_t *) ld);
> > dp = *((dirent_t *) ld);
> > =============================================================
> > Changes to /opt/RICHPse/orcallator/orcallator.se
> >
> > // Enable the raw disk measuring code.
> > // This is commented out to get out of the FLTBOUNDS overflow
> > //#define USE_RAWDISK 1
> >
> > =============================================================
> >
> > On 11/2/06, Paul Porcelli <Paul.Porcelli at scottishwater.co.uk > wrote:
> > >
> > > Hi Adrian,
> > > I'm a little confused by all the solutions put forward to the mailing
> > > list.
> > >
> > > Are you saying that the solution presented below by Peter Shattuck is
> > > not valid, or that his suggestions are in the latest build ?
> > >
> > > Many thanks.
> > > Paul
> > >
> > >
> > > Adrian Cockroft writes:
> > >
> > > > This should be a FAQ - the "stable release" is not stable and does
> > > not
> > > work. Use the latest build.
> > > >
> > > > Adrian
> > >
> > >
> > > -----Original Message-----
> > > From: orca-users-bounces+acockcroft= ebay.com at orcaware.com on
> > > behalf
> > > of Peter Shattuck
> > > Sent: Tue 10/31/2006 7:05 AM
> > > To: buzatu at unicc.org; orca-users at orcaware.com
> > > Subject: Re: [Orca-users] Orcallator problem on Solaris 10 domain
> > >
> > > Paul,
> > >
> > > in your /opt/RICHPse/orcallator/orcallator.se file do you have the
> > > following
> > > line commented out.
> > >
> > > // Enable the raw disk measuring code.
> > > //#define USE_RAWDISK 1
> > >
> > > If not then do so, also make sure your /opt/RICHPse/bin/se.sparcv9
> > > file
> > > is
> > > group owned by sys like so:
> > >
> > > -rwxr-xr-x 1 root sys 316792 Jan 5 2005 se.sparcv9
> > >
> > >
> > > If these changes are already implemented on your system and you are
> > > getting
> > > these errors then please disregard.
> > >
> > > V/R
> > > Peter Shattuck
> > >
> > >
> > >
> > >
> > >
> > >
> > > >From: Daniel Buzatu <buzatu at unicc.org>
> > > >To: orca-users at orcaware.com
> > > >Subject: Re: [Orca-users] Orcallator problem on Solaris 10 domain
> > > >Date: Sun, 29 Oct 2006 16:12:02 +0000 (UTC)
> > > >
> > > >
> > > >
> > > >Paul Porcelli <Paul.Porcelli <at> scottishwater.co.uk> writes:
> > > >
> > > > >
> > > > > Running the stable release of Orca on a SAN attached Solaris 10
> > > domain.
> > > > > When I try to start orcallator I get a segmentation fault.
> > > > > Last part of the truss output shows:
> > > > >
> > > > > 17644: ioctl(4, KSTAT_IOC_READ, "sd0,err") = 21121
> > > > > 17644: ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 21121
> > > >...
> > > > > 17644: Incurred fault #6, FLTBOUNDS %pc = 0xFFFFFFFF7DF00D48
> > >
> > > > > 17644: siginfo: SIGSEGV SEGV_MAPERR addr=0xFFFFFFFF7EE06000
> > > > > 17644: Received signal #11, SIGSEGV [default]
> > > > > 17644: siginfo: SIGSEGV SEGV_MAPERR addr=0xFFFFFFFF7EE06000
> > >
> > > > > # /opt/RICHPse/bin/se -DWATCH_OS -DWATCH_WORKLOAD
> > > > > -I/opt/RICHPse/include/ /usr/local/lib/orcallator.se
> > > > > Segmentation Fault
> > > > >
> > > > > N.B. I have the Orca running successfully on a non SAN attached
> > > S10
> > > > > T2000
> > > > >
> > > > > Thanks for any advice/help.
> > > > >
> > > > > Paul
> > > > >
> > > > > Scottish Water
> > > > > www.scottishwater.co.uk
> > > > > www.scottishwatersolutions.co.uk
> > > > > postmaster <at> scottishwater.co.uk
> > > > >
> > > >
> > > >
> > > >Paul, unfortunately I don't have a solution, but I do have exactly
> > > the
> > > same
> > > >issue as you. Should you find an answer, could you please let me
> > > know;
> > > and
> > > >of
> > > >course, I will do the same.
> > > >
> > > >Thanks,
> > > >Daniel
> > > >
> > > >
> > > >_______________________________________________
> > > >Orca-users mailing list
> > > >Orca-users at orcaware.com
> > > > http://www.orcaware.com/mailman/listinfo/orca-users
> > > P
> > >
> > > _________________________________________________________________
> > > Use your PC to make calls at very low rates
> > > https://voiceoam.pcs.v2s.live.com/partnerredirect.aspx
> > >
> > > _______________________________________________
> > > Orca-users mailing list
> > > Orca-users at orcaware.com
> > > http://www.orcaware.com/mailman/listinfo/orca-users
> > > Privileged/Confidential information may be contained in this Email and
> > > any files transmitted
> > > with it. If you are not the intended recipient you should not retain,
> > > copy or use this Email
> > > for any purpose or disclose all or part of its contents to any person.
> > > If you have received
> > > this Email in error please notify the postmaster and sender
> > > immediately and delete this
> > > Email from your system.
> > >
> > > Opinions, conclusions and other information in this message that do
> > > not relate to the
> > > official business of Scottish Water ("SW") and / or Scottish Water
> > > Solutions Ltd ("SWS")
> > > shall be understood as neither given nor endorsed by them. The
> > > contents of Emails sent and
> > > received by SW and SWS are monitored.
> > >
> > > WARNING: Although SW and SWS have taken reasonable precautions to
> > > ensure no viruses or other
> > > malicious software are present, SW and SWS cannot accept
> > > responsibility for any loss or
> > > damage arising from the use of this Email or attachments however
> > > caused. The recipient
> > > should therefore check this Email and any attachments for the presence
> > > of viruses or other
> > > malicious software.
> > >
> > > Scottish Water
> > > www.scottishwater.co.uk
> > > www.scottishwatersolutions.co.uk
> > > postmaster at scottishwater.co.uk
> > >
> > > _______________________________________________
> > > Orca-users mailing list
> > > Orca-users at orcaware.com
> > > http://www.orcaware.com/mailman/listinfo/orca-users
> > >
> >
> >
> ------------------------------
>
> _______________________________________________
> Orca-users mailing listOrca-users at orcaware.comhttp://www.orcaware.com/mailman/listinfo/orca-users
>
>
> --
>
> --Dragon
> "draco nemo omnibus horis sapit"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/orca-users/attachments/20061127/96b63b5d/attachment-0002.html>
More information about the Orca-users
mailing list