package rpcbind 0.2.3-0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rpcbind (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
tried the command:
sudo apt install icinga2 nagios-plugins
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: rpcbind 0.2.3-0.2
ProcVersionSign
Uname: Linux 4.4.0-101-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
Date: Sun Dec 3 17:18:40 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2015-04-25 (953 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
RelatedPackageV
dpkg 1.18.4ubuntu1.3
apt 1.2.24
SourcePackage: rpcbind
Title: package rpcbind 0.2.3-0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-10-03 (425 days ago)
tags: | removed: need-duplicate-check |
Hi gch,
as a first step I tried the same command to install and it worked fine for me.
Looking at the logs you provided I see:
A dependency job for rpcbind.service failed. See 'journalctl -xe' for details.
The journal as far as attached only has:
Dez 03 17:18:40 hostname systemd[1]: rpcbind.socket: Socket service rpcbind.service already active, refusing.
Dez 03 17:18:40 hostname systemd[1]: Failed to listen on RPCbind Server Activation Socket.
Dez 03 17:18:40 hostname systemd[1]: Dependency failed for RPC bind portmap service.
I can't see further details in the logs, you might be able to check them and report with "journalctl -xe" as well as checking all else you can find on rpcbind.
I did a short search and found some issues with a similar symptom. Those were all related to ipv6 - in one case it was ipv6 only in the other ipv6 was disabled in the kernel and so on. Is your testcase special in regard to ipv6 in any way?
We need a way to reproduce your issue so I hope your further log checks or ipv6 can provide those to help you based on this.