SUMMARY: sudo: cannot open socket: Invalid argument

Multiple responses, but none of them hit the target.

Indeed the problem turned out to be related to the libsocket.so.1 in the 
/usr/local/lib directory.
There was no LD_LIBRARY_PATH defined so this must be one of the "default" 
searches.

When I removed this entry by renaming it, sudo began to work and mapped 
the socket library in /usr/lib.

I have no idea where the local version of the socket library came from.
I will leave things as they are and see if anyone complains.


Chris Ruhnke
IBM SMB
Mid-Range Server Support
----- Forwarded by Chris Ruhnke/St Louis/IBM on 05/04/2008 04:21 PM -----

Chris Ruhnke/St Louis/IBM 
05/02/2008 09:56 AM

To
sunmanagers
cc

Subject
Update: sudo: cannot open socket: Invalid argument






To all who have asked the obvious questions...

- Yes, the file ownership is root:root
- Yes, the setuid bit is on -- mod = ---s--x--x

The checksums between working server and the non-working server match.

Several folks made recommendations to check the load libraries and we may 
have something there!

NON-WORKING:

homer # ldd `which sudo`
        libpam.so.1 =>   /usr/lib/libpam.so.1
        libdl.so.1 =>    /usr/lib/libdl.so.1
        libsocket.so.1 =>        /usr/local/lib/libsocket.so.1   <---
        libsocket.so.1 (SISCD_2.3) =>    (version not found)     <---
        libnsl.so.1 =>   /usr/lib/libnsl.so.1
        libc.so.1 =>     /usr/lib/libc.so.1
        libmp.so.2 =>    /usr/lib/libmp.so.2

WORKING:

pollux# ldd `which sudo`
        libpam.so.1 =>   /usr/lib/libpam.so.1
        libdl.so.1 =>    /usr/lib/libdl.so.1
        libsocket.so.1 =>        /usr/lib/libsocket.so.1         <---
        libnsl.so.1 =>   /usr/lib/libnsl.so.1
        libc.so.1 =>     /usr/lib/libc.so.1
        libmp.so.2 =>    /usr/lib/libmp.so.2
        /usr/platform/SUNW,Ultra-Enterprise/lib/libc_psr.so.1

Note that the working server points the libsocket.so.1 library to the 
module in /use/lib while the failing server uses /use/local/lib.  I also 
have no idea where the (SISCD_2.3) module comes from on the failing 
server.

At least I have something to research now!

Will summarize when I resolve.


Chris Ruhnke
IBM SMB
Mid-Range Server Support


Original posting:

On Thu, 1 May 2008, Chris Ruhnke wrote:

 
This is an unusual one, for me at least...

Inherited server -- isn't that the was too many of these get started!

# uname -a
SunOS homer 5.6 Generic_105181-17 sun4m sparc SUNW,SPARCstation-10

Trying to run sudo and it doesn't start.  Displays the message:

# sudo -V
sudo: cannot open socket: Invalid argument

Have tried copying over a known good sudo image from another server
allegedly running the exact same patch level of Solaris 5.6 and get the
same results.

Have searched the sunmanagers archives with no hits.
Have Googled the web with no hits.

Anybody have an idea what the problem might be?
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers