linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anibal Monsalve Salazar <anibal@debian.org>
To: Steve Dickson <SteveD@redhat.com>, Kevin Coffman <kwc@umich.edu>
Cc: linux-nfs@vger.kernel.org, Michael Rasmussen <mir@datanom.net>,
	651032@bugs.debian.org
Subject: Re: Bug#651032: /usr/sbin/rpc.idmapd: rpc.idmapd referring to none existing library
Date: Mon, 5 Dec 2011 19:25:20 +1100	[thread overview]
Message-ID: <20111205082520.GA5890@debian.org> (raw)
In-Reply-To: <20111205071808.5626.67399.reportbug@sleipner.datanom.net>

Hello Steve and Kevin,

To fix Debian Bug#649491[1], I moved the .so files to /lib and applied
the following patch:

--- a/libnfsidmap.c	2010-12-09 04:07:53.000000000 +1100
+++ b/libnfsidmap.c	2011-12-05 11:23:46.000000000 +1100
@@ -61,7 +61,7 @@ static struct mapping_plugin **nfs4_plug
 static struct mapping_plugin **gss_plugins = NULL;
 
 #ifndef PATH_PLUGINS
-#define PATH_PLUGINS "/usr/lib/libnfsidmap"
+#define PATH_PLUGINS "/lib/libnfsidmap"
 #endif
 #define PLUGIN_INIT_FUNC "libnfsidmap_plugin_init"
 
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649491

As Michael reported, libnfsidmap is still looking for the plugins in
/usr/lib/libnfsidmap.

What do I need to change in libnfsidmap to make it find the plugins in
/lib/libnfsidmap?

Please see Michael's report below.

Cheers,

Anibal

As Michael has reported, libnfsidmap2 is still looking 
On Mon, Dec 05, 2011 at 08:18:08AM +0100, Michael Rasmussen wrote:
> Package: nfs-common
> Version: 1:1.2.5-2+b1
> Severity: grave
> File: /usr/sbin/rpc.idmapd
> Justification: renders package unusable
> 
> rpc.idmapd -v
> rpc.idmapd: libnfsidmap: using domain: midgaard
> 
> rpc.idmapd: libnfsidmap: Unable to load plugin:
> /usr/lib/libnfsidmap/nsswitch.so: cannot open shared object file: No
> such file or directory
> 
> rpc.idmapd: libnfsidmap: requested translation method, 'nsswitch', is
> not available
> 
> rpc.idmapd: Unable to create name to user id mappings.
> 
> rpc.idmapd is searching for libnfsidmap plugins in the wrong directory
> so bug #650904 must be reopen since the provided change made to
> libnfsidmap2 does not make any difference rpc.idmapd still uses
> /usr/lib/libnfsidmap.
> 
> 
> -- Package-specific info:
> -- rpcinfo --
>    program vers proto   port  service
>     100000    4   tcp    111  portmapper
>     100000    3   tcp    111  portmapper
>     100000    2   tcp    111  portmapper
>     100000    4   udp    111  portmapper
>     100000    3   udp    111  portmapper
>     100000    2   udp    111  portmapper
>     100007    2   udp    785  ypbind
>     100007    1   udp    785  ypbind
>     100007    2   tcp    786  ypbind
>     100007    1   tcp    786  ypbind
> -- /etc/default/nfs-common --
> NEED_STATD=no
> STATDOPTS=
> NEED_IDMAPD=yes
> NEED_GSSD=
> -- /etc/idmapd.conf --
> [General]
> Verbosity = 0
> Pipefs-Directory = /var/lib/nfs/rpc_pipefs
> Domain = midgaard 
> [Mapping]
> Nobody-User = nobody
> Nobody-Group = nogroup
> -- /etc/fstab --
> balder:/home	/home		nfs4	defaults,proto=tcp,retry=5,hard,intr,async,_netdev,rsize=32768,wsize=32768 0	0
> -- /proc/mounts --
> rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
> balder:/home/ /home nfs4 rw,relatime,vers=4,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.2.79,minorversion=0,local_lock=none,addr=192.168.2.2 0 0
> 
> -- System Information:
> Debian Release: wheezy/sid
>   APT prefers unstable
>   APT policy: (990, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
> Shell: /bin/sh linked to /bin/bash
> 
> Versions of packages nfs-common depends on:
> ii  adduser             3.113
> ii  initscripts         2.88dsf-13.13
> ii  libc6               2.13-21
> ii  libcap2             1:2.22-1
> ii  libcomerr2          1.42-1
> ii  libdevmapper1.02.1  2:1.02.67-2
> ii  libevent-2.0-5      2.0.16-stable-1
> ii  libgssapi-krb5-2    1.10+dfsg~alpha1-6
> ii  libgssglue1         0.3-3.1
> ii  libk5crypto3        1.10+dfsg~alpha1-6
> ii  libkeyutils1        1.5.2-2
> ii  libkrb5-3           1.10+dfsg~alpha1-6
> ii  libnfsidmap2        0.24-3
> ii  libtirpc1           0.2.2-5
> ii  libwrap0            7.6.q-21
> ii  lsb-base            3.2-28
> ii  rpcbind             0.2.0-6
> ii  ucf                 3.0025+nmu2
> 
> Versions of packages nfs-common recommends:
> ii  python  2.7.2-9
> 
> nfs-common suggests no packages.
> 
> -- no debconf information

       reply	other threads:[~2011-12-05  8:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20111205071808.5626.67399.reportbug@sleipner.datanom.net>
2011-12-05  8:25 ` Anibal Monsalve Salazar [this message]
2011-12-05 15:52   ` Bug#651032: /usr/sbin/rpc.idmapd: rpc.idmapd referring to none existing library Steve Dickson
2011-12-05 18:42     ` Anibal Monsalve Salazar
2011-12-05 20:20       ` Steve Dickson
2011-12-07 12:44         ` Steven Shiau
2011-12-07 14:35           ` Rares Aioanei

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=20111205082520.GA5890@debian.org \
    --to=anibal@debian.org \
    --cc=651032@bugs.debian.org \
    --cc=SteveD@redhat.com \
    --cc=kwc@umich.edu \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mir@datanom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).