We're trying to track down a problem and need help
understanding what an error message means (and what
might be causing it...)

Background:  We have 11 identical Linux RH 8.0 boxes
(dual-cpu Athlons).  One of them exports a filesystem
via NFS to the other 10.

Running a specific program on each of the 10 machines
works sometimes and not others.  The machines on which
it fails changes, but once it fails it continues to
do so until we remount (unmount+mount, not with
"-o remount") the NFS directory.  After the remount
the program functions properly.

Here is the error message (split to fit):

jboc-03:18> runwip
   ../../../Bin/Linux/DHS/vsmWip:
   error while loading shared libraries:
   /opt/solis/devel/release/Lib/Linux/DHS/libprocess.so:
   unexpected PLTreloc type 0xec

Both the program (vsmWip) and the offending shared
library libprocess.so are located on the NFS-mounted FS.

*ANY* help is appreciated.  Thanks in advance!

This is fairly new behavior, though we're now using the
system more heavily than previously.

-Steve

> Both the program (vsmWip) and the offending shared
> library libprocess.so are located on the NFS-mounted FS.
>
> *ANY* help is appreciated.  Thanks in advance!

 Try upgrading to the latest versions of nfs-utils and the like.  If
you're still having problems, the NFS mailing list is usually very
helpful.

steve

In article <pan.2003.10.23.20.59.01.867593@noao.edu>, Steve Wampler wrote:
> 
> We're trying to track down a problem and need help
> understanding what an error message means (and what
> might be causing it...)
> 
> Background:  We have 11 identical Linux RH 8.0 boxes
> (dual-cpu Athlons).  One of them exports a filesystem
> via NFS to the other 10.
> 
> Running a specific program on each of the 10 machines
> works sometimes and not others.  The machines on which
> it fails changes, but once it fails it continues to
> do so until we remount (unmount+mount, not with
> "-o remount") the NFS directory.  After the remount
> the program functions properly.

I usually don't have that many machines trying to access an NFS export, 
but you might check one condition (if you haven't already):  the 
RedHat startup script for NFS in /etc/rc.d/init.d only starts 8 daemons; 
since it's first-come-first-served, that could be a problem with some of 
the machines.  

I've also run into problems using NFS where the network infrastructure is
a little bit flaky.  I was trying to do network installs of RH9 on several
machines (which employs NFS), and 2 on a particular chunk of the network
kept hanging during the install, whereas the machines elsewhere in the
room installed without a hitch.  I blamed in on flaky network cards, or
bad wiring.


-- 
Dave Brown  Austin, TX