package autofs 5.0.8-1ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1633994 reported by Irfan
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
autofs (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  keyutils libnfsidmap2 libtirpc1 nfs-common rpcbind
Suggested packages:
  open-iscsi watchdog
The following NEW packages will be installed:
  autofs keyutils libnfsidmap2 libtirpc1 nfs-common rpcbind
0 upgraded, 6 newly installed, 0 to remove and 342 not upgraded.
Need to get 687 kB of archives.
After this operation, 3,341 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://in.archive.ubuntu.com/ubuntu/ vivid/main libnfsidmap2 amd64 0.25-5 [32.2 kB]
Get:2 http://in.archive.ubuntu.com/ubuntu/ vivid-updates/main autofs amd64 5.0.8-1ubuntu3.2 [307 kB]
Get:3 http://in.archive.ubuntu.com/ubuntu/ vivid/main libtirpc1 amd64 0.2.5-1 [75.6 kB]
Get:4 http://in.archive.ubuntu.com/ubuntu/ vivid/main keyutils amd64 1.5.9-5ubuntu1 [47.9 kB]
Get:5 http://in.archive.ubuntu.com/ubuntu/ vivid-updates/main rpcbind amd64 0.2.1-6ubuntu3.1 [38.5 kB]
Get:6 http://in.archive.ubuntu.com/ubuntu/ vivid-updates/main nfs-common amd64 1:1.2.8-9ubuntu8.1 [186 kB]
Fetched 687 kB in 5s (127 kB/s)
Selecting previously unselected package libnfsidmap2:amd64.
(Reading database ... 170994 files and directories currently installed.)
Preparing to unpack .../libnfsidmap2_0.25-5_amd64.deb ...
Unpacking libnfsidmap2:amd64 (0.25-5) ...
Selecting previously unselected package autofs.
Preparing to unpack .../autofs_5.0.8-1ubuntu3.2_amd64.deb ...
Unpacking autofs (5.0.8-1ubuntu3.2) ...
Selecting previously unselected package libtirpc1:amd64.
Preparing to unpack .../libtirpc1_0.2.5-1_amd64.deb ...
Unpacking libtirpc1:amd64 (0.2.5-1) ...
Selecting previously unselected package keyutils.
Preparing to unpack .../keyutils_1.5.9-5ubuntu1_amd64.deb ...
Unpacking keyutils (1.5.9-5ubuntu1) ...
Selecting previously unselected package rpcbind.
Preparing to unpack .../rpcbind_0.2.1-6ubuntu3.1_amd64.deb ...
Unpacking rpcbind (0.2.1-6ubuntu3.1) ...
Selecting previously unselected package nfs-common.
Preparing to unpack .../nfs-common_1%3a1.2.8-9ubuntu8.1_amd64.deb ...
Unpacking nfs-common (1:1.2.8-9ubuntu8.1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for systemd (219-7ubuntu3) ...
Setting up libnfsidmap2:amd64 (0.25-5) ...
Setting up autofs (5.0.8-1ubuntu3.2) ...

Creating config file /etc/auto.master with new version

Creating config file /etc/auto.net with new version

Creating config file /etc/auto.misc with new version

Creating config file /etc/auto.smb with new version

Creating config file /etc/default/autofs with new version
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Job for autofs.service failed. See "systemctl status autofs.service" and "journalctl -xe" for details.
invoke-rc.d: initscript autofs, action "start" failed.
dpkg: error processing package autofs (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up libtirpc1:amd64 (0.2.5-1) ...
Setting up keyutils (1.5.9-5ubuntu1) ...
Setting up rpcbind (0.2.1-6ubuntu3.1) ...
Setting up nfs-common (1:1.2.8-9ubuntu8.1) ...

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

Creating config file /etc/default/nfs-common with new version
Adding system user `statd' (UID 120) ...
Adding new user `statd' (UID 120) with group `nogroup' ...
Not creating home directory `/var/lib/nfs'.
invoke-rc.d: gssd.service doesn't exist but the upstart job does. Nothing to start or stop until a systemd or init job is present.
invoke-rc.d: idmapd.service doesn't exist but the upstart job does. Nothing to start or stop until a systemd or init job is present.
nfs-utils.service is a disabled or a static unit, not starting it.
Processing triggers for libc-bin (2.21-0ubuntu4) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (219-7ubuntu3) ...
Errors were encountered while processing:
 autofs
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: autofs 5.0.8-1ubuntu3.2
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: hid_generic usbhid hid psmouse pata_acpi i915 fjes atl1c video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
Date: Mon Oct 17 11:36:56 2016
DuplicateSignature: package:autofs:5.0.8-1ubuntu3.2:subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2016-10-17 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt 1.0.9.7ubuntu4
SourcePackage: autofs
Title: package autofs 5.0.8-1ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Irfan (irfan.gwb) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Joshua Powers (powersj) wrote :

From log:

Job for autofs.service failed. See "systemctl status autofs.service" and "journalctl -xe" for details.
invoke-rc.d: initscript autofs, action "start" failed.
dpkg: error processing package autofs (--configure):
 subprocess installed post-installation script returned error exit status 1

Revision history for this message
Joshua Powers (powersj) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Can you please provide the output of "systemctl status autofs.service" and "journalctl -xe" to help further triage this issue?

Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Changed in autofs (Ubuntu):
status: New → Incomplete
Revision history for this message
Irfan (irfan.gwb) wrote :

root@gwb:~# systemctl status autofs.service
● autofs.service - LSB: Automounts filesystems on demand
   Loaded: loaded (/etc/init.d/autofs)
   Active: failed (Result: exit-code) since Thu 2016-10-20 16:11:36 IST; 13s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 3507 ExecStart=/etc/init.d/autofs start (code=exited, status=1/FAILURE)

Oct 20 16:11:36 gwb systemd[1]: Starting LSB: Automounts filesystems on demand...
Oct 20 16:11:36 gwb autofs[3507]: * Starting automount...
Oct 20 16:11:36 gwb autofs[3507]: ...fail!
Oct 20 16:11:36 gwb systemd[1]: autofs.service: control process exited, code=exited status=1
Oct 20 16:11:36 gwb systemd[1]: Failed to start LSB: Automounts filesystems on demand.
Oct 20 16:11:36 gwb systemd[1]: Unit autofs.service entered failed state.
Oct 20 16:11:36 gwb systemd[1]: autofs.service failed.
root@gwb:~#

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi Irfan,
thanks for the log, but this is only the status report requested by Joshua.
Here I can't atm find any further help.

I'd still hope that we could find something in "journalctl -xe -u autofs" if you can provide that.

On the other hand I've seen in the log this:
Oct 17 11:33:22 hostname systemd[1]: Failed to insert module 'autofs4'

Could it be that you updated your kernel and cleaned up but are still in an old environment?
In that case it could fail to load further modules?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for autofs (Ubuntu) because there has been no activity for 60 days.]

Changed in autofs (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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