Comment 8 for bug 670289

Client, thanks for looking at it. As Björn mentioned there is not much to say. I think I've identified one linked problem though, where the service doesn't start sometimes: rabbitmq is tied to the existence of a particular hostname (generally the one detected when first installed).

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).

Björn: do you have anything in shutdown_err by any chance?