invoke-rc.d: initscript statd, action "restart" failed.

Bug #451027 reported by Bryce Harrington
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nfs-utils (Ubuntu)
Invalid
Medium
Steve Langasek
Karmic
Invalid
Medium
Steve Langasek

Bug Description

After doing an update from an existing karmic installation (last updated 10-02), I found that apt failed trying to update nfs-common. I uninstalled it, and finished up the upgrade. Then I re-tried installing nfs-common from scratch, and it gave the same error it was giving before:

bryce@salisbury:~$ sudo apt-get install nfs-common
[sudo] password for bryce:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  libgssglue1 libnfsidmap2 librpcsecgss3 portmap
The following NEW packages will be installed:
  libgssglue1 libnfsidmap2 librpcsecgss3 nfs-common portmap
0 upgraded, 5 newly installed, 0 to remove and 90 not upgraded.
Need to get 84.3kB/333kB of archives.
After this operation, 1126kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://archive.ubuntu.com karmic/main libgssglue1 0.1-3 [23.6kB]
Get:2 http://archive.ubuntu.com karmic/main libnfsidmap2 0.21-2 [28.4kB]
Get:3 http://archive.ubuntu.com karmic/main librpcsecgss3 0.18-1 [32.4kB]
Fetched 84.3kB in 1s (43.2kB/s)
Preconfiguring packages ...
Selecting previously deselected package libgssglue1.
(Reading database ... 490205 files and directories currently installed.)
Unpacking libgssglue1 (from .../libgssglue1_0.1-3_i386.deb) ...
Selecting previously deselected package libnfsidmap2.
Unpacking libnfsidmap2 (from .../libnfsidmap2_0.21-2_i386.deb) ...
Selecting previously deselected package librpcsecgss3.
Unpacking librpcsecgss3 (from .../librpcsecgss3_0.18-1_i386.deb) ...
Selecting previously deselected package portmap.
Unpacking portmap (from .../portmap_6.0-10ubuntu2_i386.deb) ...
Selecting previously deselected package nfs-common.
Unpacking nfs-common (from .../nfs-common_1%3a1.2.0-2ubuntu7_i386.deb) ...
Processing triggers for man-db ...
Setting up libgssglue1 (0.1-3) ...

Setting up libnfsidmap2 (0.21-2) ...

Setting up librpcsecgss3 (0.18-1) ...

Setting up portmap (6.0-10ubuntu2) ...
portmap start/running, process 6036
There are RPC services which were registered with the portmapper
before the configuration was changed.
You need to manually restart them in order for the changes to take effect.
Current registered services:
------------------------------------------------
    100024 1 udp 45583 status
    100024 1 tcp 43643 status
------------------------------------------------

Setting up nfs-common (1:1.2.0-2ubuntu7) ...
 * Stopping NFS common utilities [ OK ]
 Removing any system startup links for /etc/init.d/nfs-common ...
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service statd restart

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the restart(8) utility, e.g. restart statd
statd start/running, process 6272
restart: Unknown instance:
invoke-rc.d: initscript statd, action "restart" failed.
dpkg: error processing nfs-common (--configure):
 subprocess installed post-installation script returned error exit status 127
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
 nfs-common
E: Sub-process /usr/bin/dpkg returned an error code (1)

Revision history for this message
Bryce Harrington (bryce) wrote :
Changed in nfs-utils (Ubuntu Karmic):
assignee: nobody → Steve Langasek (vorlon)
milestone: none → ubuntu-9.10
Revision history for this message
Steve Langasek (vorlon) wrote :

The code in upstart-job does this:

    elif [ -z "$PID" ] && [ "$COMMAND" = "restart" ]; then
        start "$JOB"
        exit 0
    fi
    $COMMAND "$JOB"

Given that, I can't make sense of your output - it seems to have called 'start statd', and then proceeded to call 'restart statd' afterwards instead of exiting?

For that matter, calling 'restart statd' after it's been started should work fine...

What version of upstart do you have installed?

What happens if you run 'sudo start statd' by hand?

Changed in nfs-utils (Ubuntu Karmic):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Steve Langasek (vorlon) wrote :

Closing, unreproducible with current packages. Please reopen if you can provide the requested information.

Changed in nfs-utils (Ubuntu Karmic):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.