[Orca-users] orcallator segfaults

Tony Howat t.howat at arts.ac.uk
Wed Aug 25 06:16:19 PDT 2004


orcallator is segfaulting when I try to start it on a Solaris 9 R280R 
connected to a FC SAN....

/opt/RICHPse/bin/se -DWATCH_OS -DWATCH_WEB -d /usr/local/lib/orcallator.se

[lots of debug]
if (strncmp(first_name<sd6>, 51Dd0<md103>, first_len<3>) == <0>)
if (strcmp(RAW_disk[3].short_name[3]<5>, 51Dd0<md103>) == <0>)
j++;
strcpy(51Dd0<md103>, GLOBAL_disk_info[43].short_name<md102>)
if (j<43> > <0>)
if (strncmp(first_name<sd6>, 51Dd0<md102>, first_len<3>) == <0>)
if (strcmp(RAW_disk[3].short_name[3]<5>, 51Dd0<md102>) == <0>)
j++;
strcpy(51Dd0<md102>, GLOBAL_disk_info[44].short_name<(nil)>)
Segmentation Fault

I saw a posting 
http://www.orcaware.com/pipermail/orca-users/2003-December/003482.html

that seems to report my problem. Ed claims that the problem is long/odd 
device names, citing his fiber devices with their WWNs embedded in them. 
This system also has FC devices connected, and has /dev/dsk containing 
things like :

  ../../devices/pci at 8,700000/SUNW,qlc at 2/fp at 0,0/ssd at w200800a0b813180d,3:a
lrwxrwxrwx   1 root     root          70 Jul 26 13:16 
c3t200800A0B813180Dd3s1 ->

and:

../../devices/scsi_vhci/ssd at g600a0b80001323b80000000040f2051d:b
lrwxrwxrwx   1 root     root          63 Jul 29 10:13 
c5t600A0B80001323B80000000

Has this problem been corrected?

I am using orca 0.27

-- 
Tony Howat
UNIX Network Administrator
University Of The Arts London




More information about the Orca-users mailing list