package nfs-common 1:1.2.5-3ubuntu3 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

FWIW: I ran into this when running "do-release-upgrade" on a server that had NFS installed and configured

Hi Muharem,

On Wed, Jul 11, 2012 at 12:30:31PM -0000, Muharem Hrnjadovic wrote:
> $ sudo apt-get install --reinstall nfs-common
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages were automatically installed and are no longer required:
> xfonts-encodings linux-headers-3.0.0-22 libapt-inst1.3 xfonts-utils
> libxfont1 libept1 libvtk5.6 libvpx0 linux-headers-3.0.0-22-server
> libapt-pkg4.11 x-ttcidfont-conf libfontenc1 libjpeg62 libnl3 defoma
> libllvm2.9
> Use 'apt-get autoremove' to remove them.
> 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
> 2 not fully installed or removed.
> After this operation, 0 B of additional disk space will be used.
> Setting up nfs-common (1:1.2.5-3ubuntu3) ...
> rmdir: failed to remove `/var/lib/nfs/rpc_pipefs'
> dpkg: error processing nfs-common (--configure):
> subprocess installed post-installation script returned error exit status 1
> dpkg: dependency problems prevent configuration of nfs-kernel-server:
> nfs-kernel-server depends on nfs-common (= 1:1.2.5-3ubuntu3); however:
> Package nfs-common is not configured yet.
> dpkg: error processing nfs-kernel-server (--configure):
> dependency problems - leaving unconfigured
> No apport report written because the error message indicates it's a follow-up error from a previous failure.
> Errors were encountered while processing:
> nfs-common
> nfs-kernel-server
> E: Sub-process /usr/bin/dpkg returned an error code (1)

The latest version of nfs-common in precise does:

   rmdir --ignore-fail-on-non-empty /var/lib/nfs/rpc_pipefs

So the question is, why is rmdir failing? Is this directory a mount point?
If so, why was stopping idmapd and gssd not sufficient to trigger
unmounting?

On 07/11/2012 08:31 PM, Steve Langasek wrote:
> Hi Muharem,
>
> On Wed, Jul 11, 2012 at 12:30:31PM -0000, Muharem Hrnjadovic wrote:
>> $ sudo apt-get install --reinstall nfs-common
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> The following packages were automatically installed and are no longer required:
>> xfonts-encodings linux-headers-3.0.0-22 libapt-inst1.3 xfonts-utils
>> libxfont1 libept1 libvtk5.6 libvpx0 linux-headers-3.0.0-22-server
>> libapt-pkg4.11 x-ttcidfont-conf libfontenc1 libjpeg62 libnl3 defoma
>> libllvm2.9
>> Use 'apt-get autoremove' to remove them.
>> 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
>> 2 not fully installed or removed.
>> After this operation, 0 B of additional disk space will be used.
>> Setting up nfs-common (1:1.2.5-3ubuntu3) ...
>> rmdir: failed to remove `/var/lib/nfs/rpc_pipefs'
>> dpkg: error processing nfs-common (--configure):
>> subprocess installed post-installation script returned error exit status 1
>> dpkg: dependency problems prevent configuration of nfs-kernel-server:
>> nfs-kernel-server depends on nfs-common (= 1:1.2.5-3ubuntu3); however:
>> Package nfs-common is not configured yet.
>> dpkg: error processing nfs-kernel-server (--configure):
>> dependency problems - leaving unconfigured
>> No apport report written because the error message indicates it's a follow-up error from a previous failure.
>> Errors were encountered while processing:
>> nfs-common
>> nfs-kernel-server
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> The latest version of nfs-common in precise does:
>
> rmdir --ignore-fail-on-non-empty /var/lib/nfs/rpc_pipefs
>
> So the question is, why is rmdir failing? Is this directory a mount point?
> If so, why was stopping idmapd and gssd not sufficient to trigger
> unmounting?
Hello Steve,

that directory was not a mount point. Unfortunately I did not have the
time to look at its content. I did a

    apt-get remove --purge nfs-common

followed by

    apt-get install nfs-common nfs-kernel-server

and that fixed the issue.

On 07/12/2012 07:12 AM, Muharem Hrnjadovic wrote:
> On 07/11/2012 08:31 PM, Steve Langasek wrote:
>> Hi Muharem,
>>
>> On Wed, Jul 11, 2012 at 12:30:31PM -0000, Muharem Hrnjadovic wrote:
>>> $ sudo apt-get install --reinstall nfs-common
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> The following packages were automatically installed and are no longer required:
>>> xfonts-encodings linux-headers-3.0.0-22 libapt-inst1.3 xfonts-utils
>>> libxfont1 libept1 libvtk5.6 libvpx0 linux-headers-3.0.0-22-server
>>> libapt-pkg4.11 x-ttcidfont-conf libfontenc1 libjpeg62 libnl3 defoma
>>> libllvm2.9
>>> Use 'apt-get autoremove' to remove them.
>>> 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
>>> 2 not fully installed or removed.
>>> After this operation, 0 B of additional disk space will be used.
>>> Setting up nfs-common (1:1.2.5-3ubuntu3) ...
>>> rmdir: failed to remove `/var/lib/nfs/rpc_pipefs'
>>> dpkg: error processing nfs-common (--configure):
>>> subprocess installed post-installation script returned error exit status 1
>>> dpkg: dependency problems prevent configuration of nfs-kernel-server:
>>> nfs-kernel-server depends on nfs-common (= 1:1.2.5-3ubuntu3); however:
>>> Package nfs-common is not configured yet.
>>> dpkg: error processing nfs-kernel-server (--configure):
>>> dependency problems - leaving unconfigured
>>> No apport report written because the error message indicates it's a follow-up error from a previous failure.
>>> Errors were encountered while processing:
>>> nfs-common
>>> nfs-kernel-server
>>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>
>> The latest version of nfs-common in precise does:
>>
>> rmdir --ignore-fail-on-non-empty /var/lib/nfs/rpc_pipefs
>>
>> So the question is, why is rmdir failing? Is this directory a mount point?
>> If so, why was stopping idmapd and gssd not sufficient to trigger
>> unmounting?
> Hello Steve,
>
> that directory was not a mount point. Unfortunately I did not have the
> time to look at its content. I did a
>
> apt-get remove --purge nfs-common
>
> followed by
>
> apt-get install nfs-common nfs-kernel-server
>
> and that fixed the issue.
Hmm .. I had another look at the machine:

    $ mount
    ...
    rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw)
    rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)

It appears /var/lib/nfs/rpc_pipefs was a mount point indeed.

Best regards/Mit freundlichen Grüßen

--
Muharem Hrnjadovic <email address hidden>
Public key id : B2BBFCFC
Key fingerprint : A5A3 CC67 2B87 D641 103F 5602 219F 6B60 B2BB FCFC