ld.so.1: ls: fatal: relocation error: file /lib/nss_winbind.s o.1: symbol socket: referenced symbol not found

[Thomas, Daniel J.]

OK,
I found the part in the Makefile where it links winbind stuff.
I just learned the ldd command.  Previously an ldd on /lib/libnss_winbind.so
there were no links defined.
Now I get the following:

# ldd libnss_winbind.so
        libsocket.so.1 =>        /usr/lib/libsocket.so.1
        libnsl.so.1 =>   /usr/lib/libnsl.so.1
        libc.so.1 =>     /usr/lib/libc.so.1
        libdl.so.1 =>    /usr/lib/libdl.so.1
        libmp.so.2 =>    /usr/lib/libmp.so.2
        /usr/platform/SUNW,Ultra-1/lib/libc_psr.so.1

Is this the way it should look?

If I do an "ls -l" on a PC file in my samba share from the Unix end, now
rather then giving an error, I get the following:

# pwd
/apps/temp                            << This is my samba share
# ls -l
total 0

After show "total 0" the system just hangs there.  I did a tail on the
system log and on /usr/local/samba/var/log.winbind
Neither had any errors till I did "Control + C" to stop it.  The output in
the log.winbindd file is always the same:

[2002/02/21 13:59:26, 10] nsswitch/winbindd.c:(531)    << Appears after I
execute the ls -l
  client_write: wrote -1 bytes.
[2002/02/21 13:59:26, 3] nsswitch/winbindd.c:(539)     << Appears after I
CTRL + C
  write failed on sock 17, pid 5514: Broken pipe

After this problem, I did a "chown root" on the PC file in one window and
watched the log.winbindd file using a "tail -f".  No problems.  I ran a "ls
-l" and this time the log file was flooded with messages while the console I
used to "ls -l" on just hung there.

Did I link the file incorrectly?  Here is the line I edited:

nsswitch/libnss_winbind.so: $(WINBIND_NSS_PICOBJS)
        @echo "Linking $@"
        @$(SHLD) -h $@ -G -o $@ $(WINBIND_NSS_PICOBJS) -lsocket

Originally Read:

nsswitch/libnss_winbind.so: $(WINBIND_NSS_PICOBJS)
        @echo "Linking $@"
        @$(SHLD) -h $@ -G -o $@ $(WINBIND_NSS_PICOBJS)

After I made this change, I did a "make uninstall"  and a "make clean".
Then I ran "make" and "make install" again.

-Dan



-----Original Message-----
From: Mike Gerdts [mailto:Michael.Gerdts at alcatel.com]
Sent: Thursday, February 21, 2002 12:29 PM
To: Thomas, Daniel J.
Cc: 'samba-technical at samba.org'; 'samba-technical at thewrittenword.com'
Subject: RE: ld.so.1: ls: fatal: relocation error: file
/lib/nss_winbind.s o.1: symbol socket: referenced symbol not found


The -lsocket argument is used with ld(1) not ls(1).  This would mean
that -lsocket is missing in the Makefile that is used for creating
nss_winbind.so.1.

MIke

On Thu, 2002-02-21 at 09:00, Thomas, Daniel J. wrote:
> I'm having the same ls -l problems.  Can I confirm the following:
> 
> The Makefile should read:
> WINBIND_NSS_OBJ = nsswitch/winbind_nss.o nsswitch/wb_common.o
> nsswitch/winbind_nss_solaris.o
> 
> (Mine does already)
> 
> Then I recreate the Symbolic link for /lib/nss_winbind.so.1 and add the
> -lsocket option when creating the symbolic link?
> 
> -Dan
> 
> 
> -----Original Message-----
> From: Albert Chin [mailto:samba-technical at thewrittenword.com]
> Sent: Wednesday, February 20, 2002 10:27 AM
> To: samba-technical at samba.org
> Subject: Re: ld.so.1: ls: fatal: relocation error: file
> /lib/nss_winbind.so.1: symbol socket: referenced symbol not found
> 
> 
> On Wed, Feb 20, 2002 at 09:58:34AM -0500, David Edward Shapiro wrote:
> > When we run ls -la now after installing samba 3.0 with winbind support,
we
> > get the following error:
> > 
> > ld.so.1: ls: fatal: relocation error: file /lib/nss_winbind.so.1: symbol
> > socket: referenced symbol not found
> > 
> > 
> > Originally winbind was not working, but I changed the following in the
> > Makefile:
> > 
> > 
> > WINBIND_NSS_OBJ = nsswitch/winbind_nss.o nsswitch/wb_common.o
> > reads:
> >  
> > WINBIND_NSS_OBJ = nsswitch/winbind_nss.o nsswitch/wb_common.o
> > nsswitch/winbind_nss_solaris.o
> 
> Relink nss_winbind.so.1 and add -lsocket to the link line. This will
> resolve the problem above.
> 
> -- 
> albert chin (china at thewrittenword.com)