All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Wampler <swampler@noao.edu>
To: nfs@lists.sourceforge.net
Subject: Help understanding error message?
Date: Thu, 23 Oct 2003 14:59:03 -0700	[thread overview]
Message-ID: <3F984F27.1010806@noao.edu> (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  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2003-10-23 23:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-23 21:59 Steve Wampler [this message]
2003-10-28  1:43 ` Help understanding error message? Neil Brown
2003-10-28 13:54   ` Steve Wampler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F984F27.1010806@noao.edu \
    --to=swampler@noao.edu \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.