On Thu, Jun 22, 2017 at 12:09:11AM +0200, Tobias Brink wrote:
> After upgrading an LXC container to stretch, the "munin-node.service" systemd
> unit does no longer start at boot, but works fine if started manually later.
> The fix for me was to add
> 
> [Unit]
> After=network.target
> 
> to the munin-node.service file. I assume the reason is that the executable
> tries to bind to an address which is not available, yet (I have a statement
> like "host 192.168.42.42" in /etc/munin/munin-node.conf). Waiting for the
> network fixes this.

Please note that this is likely to take more effort in the IPv6 case
wher an IP address is not fully useable when network.target is reached
because it might still be tentative.

Greetings
Marc, who has been through this with bind9 last week
-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Reply via email to