[Bug 1142991] Re: nfs-common install fails with error "Job failed to start" E: Sub-process /usr/bin/dpkg returned an error code (1)

Tue Mar 5 03:13:41 UTC 2013

Oh, I see the problem; the howto you've linked to is garbage and is
*telling* you to break your upstart configuration by moving files around
inside of /etc/init.  I've removed this howto from help.ubuntu.com now.
Thanks for bringing it to my attention.

To get your system working again, just move the various 'disabled' files
under /etc/init back to their original names.

** Changed in: nfs-utils (Ubuntu)
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nfs-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1142991

Title:
  nfs-common install fails with error "Job failed to start" E: Sub-
  process /usr/bin/dpkg returned an error code (1)

Status in “nfs-utils” package in Ubuntu:
  Invalid

Bug description:
  Release 12.04 (precise) 64-bit, Kernel Linux 3.5.0-25-generic
  nfs-common (1:1.2.5-3ubuntu3.1)

  Can't get nfs-common installed on CLIENT new install of Precise 12.04.2
  Did copy some prior conf file from previous install: idmapd.conf (can't quite remember now)
  server had crashed on upgrade from 12.04.1->12.4.2, (or perhaps when the power company changed our meter and the ups got exhausted - yes should have had auto shutdown enabled). Since then, server rebuilt with fresh install from server iso of 12.4.2 and workng great.

  tried procedure from here https://help.ubuntu.com/community/NFSv4MinimalHowto
  installed the server with this procedure and working very well . A client laptop running 12.4.1 upgraded to 12.4.2 (so it is still using the 3.2 kernel and not the 3.5 kernel of fresh 12.4.2 installs connects fine to the networks shares, so at least that side is good.

  Goolged several bug reports wo success. nfs-common refuses to install.

  $sudo apt-get install nfs-common
  Output:
  ....
  Setting up nfs-common (1:1.2.5-3ubuntu3.1) ...
  start: Job failed to start
  invoke-rc.d: initscript statd, action "start" failed.
  dpkg: error processing nfs-common (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   nfs-common
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  -----

  Have purged and reinstalled with same results in various ways.

  verbose output trying:

  $sudo aptitude -vf install nfs-common
  The following NEW packages will be installed:
    nfs-common
  0 packages upgraded, 1 newly installed, 0 to remove and 7 not upgraded.
  Need to get 0 B/241 kB of archives. After unpacking 722 kB will be used.
  sh: 0: getcwd() failed: No such file or directory
  sh: 0: getcwd() failed: No such file or directory
  sh: 0: getcwd() failed: No such file or directory
  Selecting previously unselected package nfs-common.
  (Reading database ... 196167 files and directories currently installed.)
  Unpacking nfs-common (from .../nfs-common_1%3a1.2.5-3ubuntu3.1_amd64.deb) ...
  Processing triggers for ureadahead ...
  Processing triggers for man-db ...
  Setting up nfs-common (1:1.2.5-3ubuntu3.1) ...

  Creating config file /etc/idmapd.conf with new version

  Creating config file /etc/default/nfs-common with new version
  start: Job failed to start
  invoke-rc.d: initscript statd, action "start" failed.
  dpkg: error processing nfs-common (--configure):
   subprocess installed post-installation script returned error exit status 1
  No apport report written because MaxReports is reached already
                                                                Errors were encountered while processing:
   nfs-common
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  A package failed to install. Trying to recover:
  sh: 0: getcwd() failed: No such file or directory
  Setting up nfs-common (1:1.2.5-3ubuntu3.1) ...
  sh: 0: getcwd() failed: No such file or directory
  shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
  sh: 0: getcwd() failed: No such file or directory
  sh: 0: getcwd() failed: No such file or directory
  shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
  shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
  sh: 0: getcwd() failed: No such file or directory
  sh: 0: getcwd() failed: No such file or directory
  shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
  sh: 0: getcwd() failed: No such file or directory
  sh: 0: getcwd() failed: No such file or directory
  start: Job failed to start
  invoke-rc.d: initscript statd, action "start" failed.
  dpkg: error processing nfs-common (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   nfs-common

  Current status: 0 broken [+0], 7 updates [+0], 0 new [+0].

  -----

  One of the bug reports asked for this:

  sudo cat /var/log/upstart/statd.log
  UPSTART_EVENTS = local-filesystems started
  portmap-wait stop/waiting
  UPSTART_EVENTS =
  start: Unknown job: portmap-wait
  UPSTART_EVENTS =
  start: Unknown job: portmap-wait
  UPSTART_EVENTS =
  start: Unknown job: portmap-wait
  UPSTART_EVENTS =
  start: Unknown job: portmap-wait
  UPSTART_EVENTS =
  start: Unknown job: portmap-wait
  UPSTART_EVENTS =
  start: Unknown job: portmap-wait
  UPSTART_EVENTS =
  start: Unknown job: portmap-wait
  UPSTART_EVENTS =
  start: Unknown job: portmap-wait
  UPSTART_EVENTS =
  start: Unknown job: portmap-wait
  UPSTART_EVENTS =
  start: Unknown job: portmap-wait
  UPSTART_EVENTS =
  start: Unknown job: portmap-wait
  UPSTART_EVENTS =
  start: Unknown job: portmap-wait
  UPSTART_EVENTS =
  start: Unknown job: portmap-wait

  ----
  so I looked here:
  $ /etc/init.d ]$ ls -als stat*
  0 lrwxrwxrwx 1 root root 21 Oct 10 08:17 statd -> /lib/init/upstart-job
  0 lrwxrwxrwx 1 root root 21 Oct 10 08:17 statd-mounting -> /lib/init/upstart-job

  Well I, I don't know how to troubleshoot from those links.
  Looks like it wants but is not getting 'portmap'

  ------

  Tried installing portmap which pointed me to rpcbind. Per the HowTo
  referenced at top of this post, these are not really needed for nfs4.
  I wonder if modifying the CLIENT script to ignore portmap will fix
  this as the patch on the server side which seems to be working fine.

  I have looked for broken packages in synaptic etc.

  Any help appreaciated. I suspect I need to delete some left over files
  and perhaps reinstall some missed dependencies but can't figure this
  out. Been using nfs4 for several years now and other than the nobody /
  nogroup problem with different uid for users it performs very well.
  This is clearly just the client side nfs-common refusing to install.

  Otherwise this machine is working great and has a fairly complex setup
  with virtualbox, crossover linux running msoffice and windows virtual
  machines. Would be a real pain to have to reinstall just to get nfs-
  common running so it can connect to the nfs4 backup shares!!

  cheers and thanks abunch for reading this far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1142991/+subscriptions