The specific error message in the logs is: Preparing to unpack .../rpcbind_0.2.1-2ubuntu2.2_amd64.deb ... stop: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. invoke-rc.d: initscript rpcbind, action "stop" failed. dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... dpkg: ... it looks like that went OK Unpacking rpcbind (0.2.1-2ubuntu2.2) over (0.2.1-2ubuntu2.1) ... [...] Setting up rpcbind (0.2.1-2ubuntu2.2) ... start: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. invoke-rc.d: initscript rpcbind, action "start" failed.
Your bug report says that you are running Ubuntu 14.04, however these error messages indicate you are not running upstart as your init system. Are you running Ubuntu in a chroot on a non-upstart system? If so you should have a policy-rc.d in place to disable starting of services in the chroot. Have you done something to cause an init system other than upstart to be used on Ubuntu 14.04? If so that is entirely unsupported. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rpcbind in Ubuntu. https://bugs.launchpad.net/bugs/1503098 Title: package rpcbind 0.2.1-2ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1503098/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
