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 rabbit@ixia is "not_running" and
rabbitmq-multi stop_all hangs while trying to stop rabbit@ixia.
> Björn: do you have anything in shutdown_err by any chance?
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 rabbit@ixia is "not_running" and
rabbitmq-multi stop_all hangs while trying to stop rabbit@ixia.
> Björn: do you have anything in shutdown_err by any chance?
No, nothing.
-- /launchpad. net/~bjornt
Björn Tillenius | https:/