[Re: 20010622: Solaris 8 problems]

Hi Bryan,

I have spoken with our sys admin and have a better picture of what's
going on.  I few things I told you on Friday are inaccurate.

When I first described the situation to him he said, "Oh, I know exactly
what he did."  He says that Sun is now distributing the OS in two ways. 
The "new" way requires only one disk, but does not install all the
required pieces, and also removes old stuff, such as ucblib.  I don't
understand it - I guess that's a feature, not a bug.  Anyway, he advises
people to use the old installation method, the one that requires two
disks.  

From where you are, having already upgraded your system, you need only
to install from the second disk.

From that disk, get the package SUNWscpu.  That will have the ucblib
stuff in it.  And, if you have a 64b machine, then you need to also get
the SUNWscpux package to run in 64b mode.  (The 'x' refers to 64b
mode.)  To see if you have a 64b machine do 'isainfo -kv'.

We determined that SUNWscpu was the package to get by looking on our
machine to see which package librpcsoc was in:  

> (anne) wcfields:/home/anne 14 % grep librpcsoc /var/sadm/install/contents
> /usr/share/man/sman3lib/librpcsoc.3lib f none 0444 bin bin 5888 7026 
> 944774795 SUNWman
> /usr/ucblib/librpcsoc.so=./librpcsoc.so.1 s none SUNWscpu
> /usr/ucblib/librpcsoc.so.1 f none 0755 root bin 36016 11324 947118627 SUNWscpu
> /usr/ucblib/sparcv9/librpcsoc.so=./librpcsoc.so.1 s none SUNWscpux
> /usr/ucblib/sparcv9/librpcsoc.so.1 f none 0755 root bin 40056 20118 947118628 
> SUNWscpux

Here's information about the package once it was installed.  Looks like
it is inded for compatibility with SunOS 4.x:

(anne) wcfields:/home/anne 16 % pkginfo -l SUNWscpu 
   PKGINST:  SUNWscpu
      NAME:  Source Compatibility, (Usr)
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  11.8.0,REV=2000.01.08.18.12
   BASEDIR:  /
    VENDOR:  Sun Microsystems, Inc.
      DESC:  utilities for user interface and source build compatibility
with SunOS 4.x
    PSTAMP:  humbolt20000108182655
  INSTDATE:  Mar 28 2000 08:38
   HOTLINE:  Please contact your local service provider
    STATUS:  completely installed
     FILES:    122 installed pathnames
                 8 shared pathnames
                 1 linked files
                 9 directories
                58 executables
                 1 setuid/setgid executables
              1337 blocks used (approx)

Packages are installed in /var/sadm/pkg.  

Hope this helps.

Anne
-- 
***************************************************
Anne Wilson                     UCAR Unidata Program            
address@hidden                 P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************



-------- Original Message --------
Subject: Re: 20010622: Solaris 8 problems
Date: Fri, 22 Jun 2001 16:19:56 -0600
From: Anne Wilson <address@hidden>
Organization: UCAR
To: "Bryan G. White" <address@hidden>
CC: address@hidden, address@hidden
References: <address@hidden>

Unidata Support wrote:
> 
> ------- Forwarded Message
> 
> >cc: address@hidden
> >From: "Bryan G. White" <address@hidden>
> >Subject: Re: New Minor Version of LDM Available
> >Organization: University of Utah
> >Keywords: 200106221840.f5MIeF113807 LDM Sun Solaris 8
> 
> I'm having trouble running ldm on the lastest revision of Solaris 8,
> the 04/01 release.
> 
> At least what I can find, I hate Sun docs, there is no longer /usr/ucblib
> or /usr/ucb directories.  I believe ldm wanted the /usr/ucblib/librpcsoc.so
> library.  Well, I copied a version of librpcsoc.so from an older release
> of Solaris 8 that I had.
> 
> Ever since the updrage to the new Solaris release, I can't seem to keep
> ldm alive.  It runs for a few hours, but dies.
> 
> Do you think there might be a correlation between the library and ldm
> dying?  Have you heard of any problems with ldm on any newer revision
> of Solaris 8?
> 
> ldm 5.1.3.  Ultra 10.
> 
> Bryan
> 

Hi Bryan,

I've not heard of problems related to Solaris 8 in particular.  There
could well be a correlation between the LDM dying and your use of the
older librpcsoc.so.  Maybe that library depends on other libraries so
that grabbing that file alone won't work.

Did you upgrade from an older version of Solaris 8 to a newer version? 
And, please do a 'uname -a' on your machine and show me what it reports.

We have run an LDM on our Solaris 8 machine, wcfields.  However, I'm not
sure if it's the same version as you now have.  Here's what we've got: 
> (anne) wcfields:/usr/ucblib 15 % uname -a
> SunOS wcfields.unidata.ucar.edu 5.8 Generic_108528-08 sun4u sparc SUNW,Ultra-2
 
We have had no problems with this machine.  But it does have ucblib
installed.  Here's info about our version:

> (anne) wcfields:/home/anne 16 % ls -l /usr/ucblib/librpcsoc*
> lrwxrwxrwx   1 root     root          16 Mar 15  1999 
> /usr/ucblib/librpcsoc.so -> ./librpcsoc.so.1*
> -rwxr-xr-x   1 root     bin        36016 Jan  5  2000 
> /usr/ucblib/librpcsoc.so.1*

Our sys admin knows what packages we need and installs them whenever he
upgrades.  He is not here today, otherwise I would ask him about what
came with the distribution and what was optional.  I will ask him about
this on Monday and let you know what I find out.

There is an extra complication.  Under Solaris there is a package named
"SUNWscpux" that is necessary for the LDM.  (It seems to be for SunOS
4.x rpc compatibilty.)   On our Solaris 8 it's in
/var/sadm/pkg/SUNWscpux.  Perhaps this package came as part of the
default Solaris 7 distribution as we've seen no evidence of sites
lacking it.  Perhaps it has become optional in Solaris 8.  I'll ask our
sys admin about this also.

I recommend that you install the correct ucb package from your
distribution disk.  I'm guessing it's called the 'BSD Compatibility'
package, or something like that.  And, if you don't have SUNWscpux
install that too.  Then, I would also recommend rebuilding the LDM to
ensure that everything's consistent.  Be sure to start with 'configure',
as it checks to see what libraries are available.

Sorry - I wish I could have given you an easier solution!  I hope this
helps.  Please let me know what happens.

Anne
-- 
***************************************************
Anne Wilson                     UCAR Unidata Program            
address@hidden                 P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************