System completely up-to-date as of 2020-06-02
munin-node fails to start on boot:
Jun 3 17:29:57 <hostname> /etc/init.d/munin-node: start-stop-daemon: did not create a valid pid in `/run/munin-node.pid'
Jun 3 17:29:57 <hostname> /etc/init.d/munin-node: ERROR: munin-node failed to start
No process "*munin*" there after boot.
Have to start munin-node after boot manually with
only after that munin-node is in status running:
* status: started
Init-System is OpenRC
After manually starting, things look ok:
So there is a problem with the pid file only on boot.
The following modification of /etc/init.d/munin-node fixes the bug for me:
diff backup/munin-node ./munin-node
< before cron
> need net
Without this patch, munin-node was tried to start right after syslog-ng as the second daemon according to /var/log/messages (when the network links where not up yet), which was apparently too early for some reason.
BTW what is the reason for the "before cron" dependency? A comment should explain it.
I am not quite sure, if there is a use case when munin-node should run on a node without network (or at least without an init script resource that provides "net").
Maybe, also "net" is not really needed by munin-node, but something other, I don't know, it just fixes the bug for me, to depend on net.
The bug has been closed via the following commit(s):
Author: Hans de Graaff <email@example.com>
AuthorDate: 2023-07-22 08:11:33 +0000
Commit: Hans de Graaff <firstname.lastname@example.org>
CommitDate: 2023-07-23 05:51:01 +0000
net-analyzer/munin: depend on hostname and net in init file
Signed-off-by: Hans de Graaff <email@example.com>
net-analyzer/munin/files/munin-node_init.d_2.0.73 | 27 ++
net-analyzer/munin/munin-2.0.73-r3.ebuild | 417 ++++++++++++++++++++++
2 files changed, 444 insertions(+)