Help understanding error message?

DISCUSSION Steve Wampler 2 participants 3 messages Oct 23, 2003 – Oct 28, 2003

Subsystems (2)

NFS client NFS server

lore

Share & tools

lore

Steve Wampler

author

2003-10-23 23:29 UTC #0 lore raw

System(s): 11 identical 2-cpu Althon boxes

           RH 8.0, kernel 2.4.18-24.8.0/smp
           nfs-utils-1.0.1-2

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 (and to 5 other [different] Linux boxes as well).

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.

I couldn't find a reference to 'unexpected PLTreloc' in mailing list archive search.

[Also, I've just discovered that ldd gives a segmentation fault:

->ldd vsmWip
/usr/bin/ldd: line 1: 15403 Segmentation fault
LD_TRACE_LOADED_OBJECTS=1 LD_WARN= LD_BIND_NOW= LD_LIBRARY_VERSION=$verify_out LD_VERBOSE= "$file"
->

if LD_LIBRARY_PATH is set to include the library directory on the NFS mount. (Without that directory, ldd [correctly] simply identifies the shared libraries as missing. ldd works properly in either case after a remount of the NFS mount.]

*ANY* help is appreciated. Thanks in advance!

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

-Steve

-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

Neil Brown

2003-10-28 01:59 UTC #1 lore raw

Quoted 14 lines · On Thursday October 23, [email protected] wrote:

System(s): 11 identical 2-cpu Althon boxes
            RH 8.0, kernel 2.4.18-24.8.0/smp
            nfs-utils-1.0.1-2
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 (and to 5 other [different] Linux boxes as well).

Quoted 6 lines

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.

You aren't using "soft" mounts are you? Please tell me you aren't.

Quoted 24 lines

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.
I couldn't find a reference to 'unexpected PLTreloc' in mailing list archive search.
[Also, I've just discovered that ldd gives a segmentation fault:
->ldd vsmWip
/usr/bin/ldd: line 1: 15403 Segmentation fault
LD_TRACE_LOADED_OBJECTS=1 LD_WARN= LD_BIND_NOW= LD_LIBRARY_VERSION=$verify_out LD_VERBOSE= "$file"
->

Quoted 6 lines

if LD_LIBRARY_PATH is set to include the library directory on the NFS mount. (Without that directory, ldd [correctly] simply identifies the shared libraries as missing. ldd works properly in either case after a remount of the NFS mount.]

I don't understand why you say "[correctly]".

Can you copy the library file to /tmp when it is working, and then copy again when it is failing, and do a
cmp -l
of the two files?

NeilBrown

Steve Wampler

author

2003-10-28 13:58 UTC #2 lore raw

Quoted 2 lines · Neil Brown

You aren't using "soft" mounts are you? Please tell me you aren't.

You're right, we're not.

Quoted 9 lines

Quoted 9 lines
[Also, I've just discovered that ldd gives a segmentation fault:
->ldd vsmWip
/usr/bin/ldd: line 1: 15403 Segmentation fault
LD_TRACE_LOADED_OBJECTS=1 LD_WARN= LD_BIND_NOW= LD_LIBRARY_VERSION=$verify_out LD_VERBOSE= "$file"
->

Quoted 8 lines

Quoted 6 lines
if LD_LIBRARY_PATH is set to include the library directory on the NFS mount. (Without that directory, ldd [correctly] simply identifies the shared libraries as missing. ldd works properly in either case after a remount of the NFS mount.]
I don't understand why you say "[correctly]".

Because not finding the shared libraries is the proper behavior when LD_LIBRARY_PATH doesn't include the library dir (as apposed to ldd seg-faulting when LD_LIBRARY_PATH does include the library dir).

Quoted 4 lines

Can you copy the library file to /tmp when it is working, and then copy again when it is failing, and do a
cmp -l
of the two files?

Thanks Neil - that's an excellent suggestion! I'll see what the produces.

Signature · 13 lines

Steve Wampler -- [email protected]
Quantum materiae materietur marmota monax si marmota
                    monax materiam possit materiari?


-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist  -  [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs