Bug 225671 - munin has no plugins available, neither incl. in the ~amd64 munin-ebuild, nor separately. Therefore doesn't work
|
Bug#:
225671
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: AMD64
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: major
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: robbat2@gentoo.org
|
Reported By: gordonp@sfu.ca
|
|
Component: Applications
|
|
|
URL:
|
|
Summary: munin has no plugins available, neither incl. in the ~amd64 munin-ebuild, nor separately. Therefore doesn't work
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2008-06-09 21:05 0000
|
Edit /etc/portage/package.keywords, to accept unstable
net-analyzer/munin-1.3.4. Emerge 'munin', run "emerge --config
net-analyzer/munin" per ebuild-message. Watch the cron-error-emails arrive,
every 5min, whether or not munin-node is running.
Reproducible: Always
Steps to Reproduce:
1. emerge unstable (~amd64) net-analyzer/munin. Installs
net-analyzer/munin-1.3.4 at time of reporting.
2. emerge --config net-analyzer/munin
3. cron-error-emails arrive, every 5min thereafter
Actual Results:
Cron-error-message, received via email:
HTML::Template::param() : attempt to set parameter 'groups' with a scalar -
parameter is not a TMPL_VAR! at /usr/libexec/munin/munin-html line 162
Also:
# su -s /bin/bash munin
$ munin-cron
produces:
HTML::Template::param() : attempt to set parameter 'groups' with a scalar -
parameter is not a TMPL_VAR! at /usr/libexec/munin/munin-html line 162
Expected Results:
Should have nice munin-graphs
edit /var/lib/munin/crontab and comment out the cron-line which runs munin-cron
every 5min. This stops the mail-messages, at least.
Fixed in CVS. I patched it to have a more useful error message.
The actual source of the error is that your munin-update has not generated any
RRD files yet, so munin-graph has not generated any graphs, and thus munin-html
has no input data to generate pages for.
The full set of instructions does tell you to symlink plugins into
/etc/munin/plugins/ before you start munin-node.
Thanks for the speedy response!
When will this fix hit the tree?