Tobias Brink <tobias.br...@gmail.com> writes:

> Package: munin-node
> Version: 2.0.33-1
> Severity: important
> Tags: patch
>
> 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.

After looking at
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/, I
suspect that network-online.target might be a better choice than
network.target.  The page says about network-online.target:

  "It's [sic] primary purpose is to actively delay activation of
  services until the network is set up."

...so I'll go with that.

Thanks for reporting the bug.

-- 
Stig Sandbeck Mathisen

Reply via email to