[Orca-users] Re: Orca & filename length
Blair Zajac
bzajac at geostaff.com
Wed Jul 28 11:29:21 PDT 1999
Chris,
I looked through your files and have the following comments.
1) It doesn't look like you gave me all of the output from orca
from the beginning, where it says Orca Version .... Could you
send that also. This will let me see the problem with the
undefined values on line 533. Line 533 does not seem to be
anything special
push(@options, "$line_type:average$i#$color:$legend");
. If you want, you can put the following code just before or after
that line
my $tmp = "$line_type";
$tmp = "$i";
$tmp = "$color";
$tmp = "$legend";
Then the undefined value warning will be printed again and we
can get a handle on which value is undefined.
2) You have a machine with a large number of Ethernet ports and the
way Orca is doing its naming of files may be causing problems since
each port gets 36 characters in the name:
/usr/local/var/docroot/uscaapp03/orcallator_uscaapp03_qfe0NoCP_per_s,orcallator_
uscaapp03_qfe1NoCP_per_s,orcallator_uscaapp03_qfe2NoCP_per_s,orcallator_uscaapp0
3_qfe3NoCP_per_s,orcallator_uscaapp03_qfe4NoCP_per_s,orcallator_uscaapp03_qfe5No
CP_per_s,orcallator_uscaapp03_qfe6NoCP_per_s,orcallator_uscaapp03_qfe7NoCP_per_s
-daily.gif
. With the number of ports you have, this creates rather lengthy
filenames. Maybe there's also an issue with 2.6 being better than
2.5.1 here. I'll have to do some thinking on shorting these names
to improve caching of the names and not running into this problem.
Blair
Chris Dietzler wrote:
>
> Blair,
> I am getting the same errors. Attached is the output from Orca. I am
> also sending the Orca file. Can you figure out what the first lines from the
> orcaout.txt mean?
>
> Thanks,
>
> Chris Dietzler
> Production Engineer
> Ingram Micro
> (714) 382-2659, pager (714) 359-5189
> mailto:chris.dietzler at ingrammicro.com
>
> -----Original Message-----
> From: Blair Zajac [mailto:bzajac at geostaff.com]
> Sent: Wednesday, July 28, 1999 8:53 AM
> To: Mike DuFresne
> Cc: orca-help at onelist.com
> Subject: Re: [orca-help] orca & filename length
>
> Helo Mike,
>
> Things may have gotten fixed after more data was collected by
> orcallator.se. It takes anywhere from 2.5 to 7.5 minutes for
> it to deliver its first measurement to the data files.
>
> I've never seen the 'cannot open mtime for <file>' message before.
> How many characters long is the filename in question? When you
> run Orca with the -v option, where does it generate this message?
>
> Thanks,
> Blair
>
> Mike DuFresne wrote:
> >
> > From: Mike DuFresne <xdufresn at raytheon.com>
> >
> > I have been trying to get orca to play nice on four apparently identical
> > servers (OS wise). But I have been running into various _different_
> > problems with each installation. As I am relatively new to system
> > administration, and I am not a programmer, I am sure I'm missing
> > something somewhere.
> >
> > Three of the servers are UE4500s running 2.5.1. The fourth is an Ultra1.
> > I have installed and patched SE 3.0 on all of the boxes. I have also
> > compiled and installed perl-5.005.03 for each box.
> >
> > On one of the boxes, I was getting the error that 'find_files' from
> > orcallator.cfg was sans data. If I changed the cfg file to add the
> > server name, it seemed to find the files, but none of the data was
> > readable by Netscape.
> > ie: all broken gifs. Suprisingly enough, after diddling around for a
> > bit, I replaced the server name with the original (.*) and it started
> > working.
> >
> > Two of the UE4500s are getting 'cannot open mtime for <file>: filename
> > too long errors. I haven't been able to fix that.
> >
> > For what its worth, I have had SE/Orca working flawlessly on an Ultra5
> > and an Ultra2 with 2.6.
> >
> > I'd appreciate any assistence,
> >
> > Best Regards
> >
> > Mike DuFresne
> >
> > --------------------------- ONElist Sponsor ----------------------------
> >
> > Having difficulty getting "in synch" with list members?
> > http://www.onelist.com
> > Try ONElist's Shared Calendar to organize events, meetings and more!
> >
> > ------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------
> Name: orcaoutput.txt
> orcaoutput.txt Type: Plain Text (text/plain)
> Encoding: quoted-printable
>
> Name: orca
> orca Type: unspecified type (application/octet-stream)
> Encoding: quoted-printable
>
> Name: orca.cfg
> orca.cfg Type: unspecified type (application/octet-stream)
> Encoding: quoted-printable
More information about the Orca-users
mailing list