[Orca-users] SUMMARY: oracalltor on Solaris 9

[Kenneth Modrego]

Hey !

Changing the orcallator.se to  Version 1.37 worked perfectly, which make 
no sense cos I was using the one included on the SE Toolkit package.. and 
it should've worked, it said in the doc that was spcial for Solaris 9 :p

10 July 2002

This release is primarily for supporting Solaris 9. Significant, however,
is that it no longer supports Solaris 2.6 or any x86 release. Since the
remaining systems, Solaris 7 through 9 are all 64 bit OS releases, the
only binaries shipped with SE 3.3 are ELF-64 binaries. If you're running
your system in 32 bit mode and need ELF-32 binaries, you need to use SE 
3.2.1.

thanks for your help. the debug wasn't necessary.

Best regards,

Kenneth Modrego
UNIX Systems Administrator
Europe & Africa Region
Toyota Financial Services (UK) PLC
Tel:  +44 (0)1737 365509
Fax: +44 (0)1737 365520
mailto:kenneth.modrego at toyota-fs.com

leo.mccoy at kbm1.com 
18/11/2004 16:59

To
kenneth.modrego at toyota-fs.com
cc

Subject
RE: [Orca-users] oracalltor on Solaris 9






First, you should at least download orcallator.se v1.37 from 
http://www.orcaware.com/orca/pub/orcallator.se-1.37.txt and use it.
 
Then try creating a debug version of the start_orcallator script by 
inserting a "-d" in the SE startup line at thus:
 
# diff start_orcallator start_orcallator.debug
106c106
< nohup $SE $SE_PATCHES -DWATCH_OS $WATCH_WEB $libdir/orcallator.se &
---
> nohup $SE -d $SE_PATCHES -DWATCH_OS $WATCH_WEB $libdir/orcallator.se
 
Then run your new "debug mode" script and see if SE complains about 
anything. 
If you're starting orcallator directly and not using the Orca scripts, 
then just insert the "-d" as the first option to se.
That's a start on troubleshooting your problem...
-----Original Message-----
From: orca-users-bounces+leo.mccoy=kbm1.com at orcaware.com 
[mailto:orca-users-bounces+leo.mccoy=kbm1.com at orcaware.com]
Sent: Thursday, November 18, 2004 8:30 AM
To: orca-users at orcaware.com
Subject: [Orca-users] oracalltor on Solaris 9


Hi gents, 

I'm trying to run orcallator on a Solaris 9 64 bits to collect data for 
Orca (different server, Solaris 8), but I always get a Segmentation fault, 

all the other servers within my configuration are Solaris 8 using 
oracalltor.se Version 1.28. I've tried that version on my Solaris 9 box 
and it comes up with and error: 

"orcallator.se", line 845: error: argument type mismatch: arg #2: stat 
"orcallator.se", line 835: error: argument type mismatch: arg #2: stat 
"orcallator.se", line 2173: fatal: Errors detected.  Exiting. 

Then I upgraded to orcallator's Version 1.34 and I get the segmentation 
Fault. 

[ukbhu032t] [/opt/RICHPse/orcallator] # ../bin/se   -DWATCH_CPU 
orcallator.se 10 
Segmentation Fault 
[ukbhu032t] [/opt/RICHPse/orcallator] # uname -a 
SunOS ukbhu032t 5.9 Generic_117171-07 sun4u sparc SUNW,Netra-T12 
[ukbhu032t] [/opt/RICHPse/orcallator] # isainfo -k 
sparcv9 
[ukbhu032t] [/opt/RICHPse/orcallator] # ../bin/se   -DWATCH_CPU 
orcallator.se 10 
Segmentation Fault 
[ukbhu032t] [/opt/RICHPse/orcallator] # pkginfo -l RICHPse | grep VERSION 
   VERSION:  3.3.1 (10:06 PM 08/14/03) 
[ukbhu032t] [/opt/RICHPse/orcallator] # head -20 orcallator.se | grep 
Version 
// Version 1.34:   Jul 14, 2002 Support for SE version 3.3.  Break 
[ukbhu032t] [/opt/RICHPse/orcallator] # 
 
The rest of the examples work perfectly ( the ones I've tried ) 

[ukbhu032t] [/opt/RICHPse/examples] # ../bin/se cpus.se 
cpu:  0 state: on-line clock: 1200 MHz 
cpu:  1 state: on-line clock: 1200 MHz 
cpu:  2 state: on-line clock: 1200 MHz 
cpu:  3 state: on-line clock: 1200 MHz 
cpu:  8 state: on-line clock: 1200 MHz 
cpu:  9 state: on-line clock: 1200 MHz 
cpu: 10 state: on-line clock: 1200 MHz 
cpu: 11 state: on-line clock: 1200 MHz 
cpu: 16 state: on-line clock: 1200 MHz 
cpu: 17 state: on-line clock: 1200 MHz 
cpu: 18 state: on-line clock: 1200 MHz 
cpu: 19 state: on-line clock: 1200 MHz 

I've been reading the SE toolkit docs but there isn't much about 
orcallator. 

Any help would be highly appreciated 

TIA 

Best regards,

Kenneth Modrego
UNIX Systems Administrator
Europe & Africa Region
Toyota Financial Services (UK) PLC
Tel:  +44 (0)1737 365509
Fax: +44 (0)1737 365520
mailto:kenneth.modrego at toyota-fs.com 
This correspondence is for the intended recipient only. It may contain 
confidential or legally privileged information or both. No confidentiality 
or privilege is waived or lost by any mistransmission or unauthorised 
alteration during transmission. If you are not the intended recipient, any 
disclosure, copying, distribution or any action taken or omitted to be 
taken in reliance on it, is prohibited and may be unlawful. If you receive 
this correspondence in error, please immediately delete it from your 
system and notify the sender. Any views expressed in this message are 
those of the individual sender, except where the sender expressly, and 
with authority, states them to be the views of Toyota. This message has 
been checked for viruses but the recipient is strongly advised to rescan 
the message before opening any attachments or attached executable files. 

This correspondence is for the intended recipient only. It may contain 
confidential or legally privileged information or both. No 
confidentiality or privilege is waived or lost by any mistransmission 
or unauthorised alteration during transmission. 

If you are not the intended recipient, any disclosure, copying, 
distribution or any action taken or omitted to be taken in reliance on 
it, is prohibited and may be unlawful. If you receive this 
correspondence in error, please immediately delete it from your system 
and notify the sender. 

Any views expressed in this message are those of the individual sender, 
except where the sender expressly, and with authority, states them to 
be the views of Toyota. 

This message has been checked for viruses but the recipient is strongly 
advised to rescan the message before opening any attachments or 
attached executable files. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/orca-users/attachments/20041118/41dceb79/attachment.html>