Killing all remaining processes... [failed]

[stop]

While shutting down I get the message:
Killing all remaining processes... [failed]
rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w"
modem-manager[599]: <info> caught signal 15, shutting down...

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: rpcbind 0.2.0-6ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Sep 7 23:44:02 2011
EcryptfsInUse: Yes
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: rpcbind
UpgradeStatus: Upgraded to oneiric on 2011-08-31 (7 days ago)

[Steve Langasek (vorlon)]

Is this issue reproducible?

As far as I can tell, the code in /etc/init.d/sendsigs should avoid sending signals to *any* processes belonging to upstart jobs; and in general this works correctly. You don't have a modified version of this script on your system, do you?

[Simon Strandman (nejsimon)]

This happens to me too. I've attatched a photo of the screen. The last message repeats a few times but if I wait like 5 minutes it finally reboots.

[Simon Strandman (nejsimon)]

Actually my problem is probably a different one (I didn't see that this bug was against rpcbind). I'm going to submit a bug against wpa-supplicant instead, sorry for the noise!

[bastubis (pmg-gmx)]

I have this problem too. On boot it's complaining it can't find rpcbind but then it boots OK (although it loads the desktop painfully slowly) and on shutdown I'm getting the same [fail] message as above, then it hangs and I usually end up using the power button to turn it off. NFS is working fine.
Ubuntu 11.10, 3.0.0-12-generic

[Eric Hartmann (hartmann-eric)]

I experience the same trouble with a fresh install of oneiric.

[Fabien Lusseau (fabien-beosfrance)]

Same problem Here !

rpcbind "crash" my computer at stop.

On one of my computers I have to press the power button myself because it won't stop even after waiting 2 minutes.

[Fabien Lusseau (fabien-beosfrance)]

And no, I don't have any modification on my boot scripts. I just installed NFS usually, with the package. And on a wifi laptop.

[Sarkany Istvan (sarkany-istvan)]

I did an upgrade from 11.04 and the same is happening to me also. It also seems almost random in the sense that it won't manifest itself always, or won't always prevent shutdown. What do I need to attach to help investigating this?

[mozgreen (mozgren)]

Same problem here - only shuts down with power button since 'upgrade.' This seems to have been a problem for others since beta looking at reports via google (someone had 3 machines with the same problem). Must be ripe for investigation by those with some insight (not me, alas).

[Morfeusz888 (morfiblog)]

For me too this problem. If I select shutdown, the operating system stops at the communication KIlling all remaining processes [fail]

[Lorrin Nelson (lhn-5)]

I also have been unable to shutdown cleanly since upgrading from 11.04 to 11.10. I also get:
Killing all remaining processes... [fail]

I do have NFS mounts in my fstab but don't see messages about rpcbind.

[Peter Bašista (pbasista)]

I am experiencing similar issues on my Ubuntu 11.10, amd64.

However, mine are definitely not related to rpcbind, because I do not have it installed.

During the shutdown, my Ubuntu just waits a few seconds until all the remaining processes terminate. I assume that the modem manager, refuses to terminate or at least it doesn't terminate in time. So, when the timeout expires, the modem manager is killed and I get an error message like this:
KIlling all remaining processes [fail]
with some information about killing the modem manager process. Then, the shutdown completes successfully.

The problem is why the modem manager needs to be killed?

So, according to my experience, this issue can not be caused by rpcbind. I assume that either the modem manager or some shutdown routine is preventing the shutdown to proceed cleanly.

BTW: I was not able to find the shutdown logs in /var/log. That's why my error messages are not explicit - I couldn't cite them. Is there any way to enable the logging during the shutdown? It might be helpful...

[Steve Langasek (vorlon)]

> However, mine are definitely not related to rpcbind, because
> I do not have it installed.

Then you have a different bug and should file a separate bug report instead of redirecting this one.

[PieroCampa (piero-campa)]

Same problem here.
I get:
        rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w"
and afterwards
        Killing all remaining processes... [failed]

Running Ubuntu Oneiric 11.10 (with LXDE) on Dell Studio XPS 1640 laptop.

Any solution/workaround?

[Steve Langasek (vorlon)]

It would be helpful if people seeing this issue could check whether it still exists with the 12.04 beta.

[Fabien Lusseau (fabien-beosfrance)]

No it's working on 12.04 ! I'm on 12.04 for a long time now, and it's working great !

[PieroCampa (piero-campa)]

My problem was caused by the patch described in: https://answers.launchpad.net/ubuntu/+source/rpcbind/+question/185320
Caused rpcbind to be unresponsive.
By removing the patch this problem was solved.

See: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/995160

[Steve Langasek (vorlon)]

If everyone experiencing this problem has made these same modifications to their /etc/init/portmap.conf, then this is not a bug in Ubuntu, it's self-inflicted breakage. The patch from that answers.launchpad.net entry is COMPLETELY broken and MUST NOT be applied.

[Sven Jacobs (svenjacobs)]

I did *not* apply the patch to portmap.conf but I'm also affected by this issue.

[Steve Langasek (vorlon)]

Sven,

On Fri, May 11, 2012 at 12:42:56PM -0000, Sven Jacobs wrote:
> I did *not* apply the patch to portmap.conf but I'm also affected by
> this issue.

What precisely are you seeing, and with which version of Ubuntu?

[Pit(er) Ralon (pitralon)]

Using ubuntu 13.10 on Acer E1-572 ... is there no chance to shutdown automaticly? Is there a workaround who properly works?

[itzeme (launchacc)]

Workaround:

change the wait time from 10 seconds to 5 seconds:

/etc/init.d/sendsigs

[...]
# Kill all processes.
log_action_begin_msg "Asking all remaining processes to terminate"
killall5 -15 $OMITPIDS # SIGTERM
log_action_end_msg 0
alldead=""
OMITPIDS0="$OMITPIDS"
for seq in 1 2 3 4 5 ; do
 OMITPIDS="$OMITPIDS0"
        [...]

Notice: do not change the time to a lower time, as this might cause more problems

[Seb Bonnard (sebma)]

Hi,

I'm using Ubuntu 14.04.5 LTS and I have the same pb. :

`Killing all remaining processes... [failed]`

How can get logs from what is happening during shutdown (or reboot) ?