On Thu, Dec 16, 2010 at 08:12:49AM -0000, Thomas Herve wrote: > Since Maverick, NetworkManager seems to do some weird trick with > /etc/hosts, making the local hostname unresolvable at some points. At > least when it doesn't start, I get a "can't resolve hostname" error in > startup_err, which could map with what Björn is saying, where the > hostname can't be found at shutdown (presumably after NM did his job on > a laptop).
Right, this seems to be the issue somehow. I can reproduce the issue without shutting down the laptop, if I disconnect any network that NetworkManager is connected to. If NM isn't connected to anything, rabbit-multi status says that rab...@ixia is "not_running" and rabbitmq-multi stop_all hangs while trying to stop rab...@ixia. > Björn: do you have anything in shutdown_err by any chance? No, nothing. -- Björn Tillenius | https://launchpad.net/~bjornt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rabbitmq-server in ubuntu. https://bugs.launchpad.net/bugs/670289 Title: Laptop won't shut down with rabbitmq running -- 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
