Red Hat Bugzilla – Bug 846866
Submitting updated unit file for munin-node and two new units
Last modified: 2013-12-31 21:48:02 EST
Created attachment 603138 [details]
Updated munin-node unit
Description of problem:
Added the Documentation feature removed no longer necessary syslog.target in the After= line.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 603140 [details]
Created attachment 603141 [details]
We probably should add the relevant fcgi magic to the munin apache conf file and or in a separated one + I'm wondering if munin does not beling in /usr/share/munin and if we should not split out the plugins into separated packages with correct perl dependency on them ( or install all the required perl modules for all the shipped plugins )?
Then there is a question if we should not create a munin wikipage on fedoraprojects wiki along with test cases...
Making the .service file change is trivial, but I do have a question. Can I use the same (revised) service file in f16/f17/f18, or is this feature change specific to f18+ ?
The fcgi magic is already in the munin-async package, not sure what you mean otherwise?
For plugins, the java-plugin is in another package entirely, but munin-node contains the remaining. (Due to the dep-tree pulled in for java specifically)
The reason the bulk of the plugins exist in munin-node is so that "munin-node-configure" can run and auto-configure a base set of plugins that the node would likely be able to use.
How would you break up the plugins differently?
Open to suggestions, and as always: Patches Welcome!
(In reply to comment #3)
> Making the .service file change is trivial, but I do have a question. Can I
> use the same (revised) service file in f16/f17/f18, or is this feature
> change specific to f18+ ?
You can make the change on all releases. The Documentation part in the status output however wont be displayed on F16.
Anything pointing to /var/run should be fixed to point directly to /run instead along with using /usr/bin,/sbin instead of /bin/sbin in $path but it's non trivial and that problem probably lands on some community member to clean up in the distant future.
> The fcgi magic is already in the munin-async package, not sure what you mean
Those unit file exist for nginx which does does not spawn your FCGI-process automatically at least according to that upstream documentation
> For plugins, the java-plugin is in another package entirely, but munin-node
> contains the remaining. (Due to the dep-tree pulled in for java
> The reason the bulk of the plugins exist in munin-node is so that
> "munin-node-configure" can run and auto-configure a base set of plugins that
> the node would likely be able to use.
> How would you break up the plugins differently?
There are two flaws to our implementation that administrators are dealing with to deliver that perfect out of the box experience.
Missing perl packages for plugins and missing configuration for plugins so I would either.
package each plugin or group of plugins from /usr/share/munin/plugins in a separate munin plugin sub package with the correct perl dependency and configuration file
Install all the needed perl packages for all those plugins to work as well as all the configuration files needed for those plugins to work.
I think this may be resolved now. Can you verify 2.0.9-3+ works as expected ?
(At this time, there is a 2.0.10-1 in queue for build as well to resolve additional bugs)
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.