package nis 3.17-32ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1062802 reported by Carlos Fernández San Millán on 2012-10-06
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nis (Ubuntu)
Undecided
Unassigned

Bug Description

1) Description: Ubuntu 12.04.1 LTS
Release: 12.04

2) nis:
  Installed: 3.17-32ubuntu4.1
  Candidate: 3.17-32ubuntu4.1
  Version table:
 *** 3.17-32ubuntu4.1 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/universe amd64 Packages
        100 /var/lib/dpkg/status
     3.17-32ubuntu4 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages

3) Install nfs and nis

4) I have just run the following command: "sudo apt-get install nis nfs-common" and a crash-report showed up.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: nis 3.17-32ubuntu4.1
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
Uname: Linux 3.2.0-31-generic x86_64
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
Date: Sat Oct 6 13:40:11 2012
DuplicateSignature:
 Setting up nis (3.17-32ubuntu4.1) ...
 start: Job failed to start
 invoke-rc.d: initscript ypbind, action "start" failed.
 dpkg: error processing nis (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
SourcePackage: nis
Title: package nis 3.17-32ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

tags: removed: need-duplicate-check
Robie Basak (racb) wrote :

I tried "sudo apt-get install nis nfs-common" on a 12.04 cloud instance and got a hang on "Setting up nis (3.17-32ubuntu4.1) ...". This looked like it was hung on a "start ypbind" command. Killing that gives me similar results.

However, I don't have a functional nis server, so perhaps this is expected?

So I'm not sure I can confirm this bug right now, but I'll leave these notes here in case someone else can look at it.

James Page (james-page) wrote :

[ 577.868818] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[ 3949.265581] init: ypbind main process (5012) terminated with status 1
[ 3949.265608] init: ypbind main process ended, respawning
[ 3954.378332] init: ypbind main process (5040) terminated with status 1
[ 3954.378378] init: ypbind main process ended, respawning
[ 3959.497166] init: ypbind main process (5068) terminated with status 1
[ 3959.497200] init: ypbind main process ended, respawning
[ 3964.598599] init: ypbind main process (5096) terminated with status 1
[ 3964.598635] init: ypbind respawning too fast, stopped

James Page (james-page) wrote :

ypbind will wait for ypserv to reach state running before trying to start; so if it never reaches that state ypbind hangs for about 30 seconds at which point it should terminate in the pre-start script with a failure.

James Page (james-page) wrote :

Carlos

Please could you check in /var/log/upstart for any yp* related logs and attach them to this bug report - something is causing ypbind to fail and this might give us some pointers.

Cheers

James

Changed in nis (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

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

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

Other bug subscribers