Re: [munin-users] loggrep plugin not listed

[Christoph W. <c.w...@lm...>]

The (incomplete) sections aim at monitoring various logfiles on that
machine.

munin-run --debug loggrep_jboss
# Processing plugin configuration from /etc/munin/plugin-conf.d/loggrep
# Processing plugin configuration from /etc/munin/plugin-conf.d/munin-node
# Set /rgid/ruid/egid/euid/ to /117/0/117 117 /0/
# Setting up environment
# Environment regex_warnings = Concurrent
# Environment label_warnings = JBoss Concurrent Call Exception
# Environment regex = Exception
# Environment label = JBoss Exceptions
# Environment title = JBoss Exceptions
# Environment logfile = /opt/jboss/server/default/log/server.log
# About to run '/etc/munin/plugins/loggrep_jboss'
warnings.value 0
count.value 548

I wished, restarting the node would solve the problem...

Thanks,
Christoph

Am 11.11.2012 22:57, schrieb Nicolai Langfeldt:
> On 11/09/2012 03:57 PM, Christoph Wieser wrote:
>> has anybody a running configuration of the munin loggrep plugin? loggrep
>> is running on the munin-node but not listed when I ask the node from the
>> master and, hence, I get no graph.
>>
>> When I ask the munin-node for the list of plugins loggrep_jboss is not
>> listed as plugin but when I try to fetch the values, I am getting them.
>>
>> I tried to change /etc/munin/plugin-conf.d/loggrep. When I omit the
>> "env." in front of each line, loggrep_jboss gets listed via telnet but
>> then I get warning from the node for "munin-run loggrep_jboss".
> 
> The env. is needed because without it the lines are not doing anything
> at all, and are in fact configuration errors.  So when you configure the
> plugin it somehow breaks.
> 
>> --- /etc/munin/plugin-conf.d/loggrep
>> [loggrep*]
>> user root
>> env.regex Exception
>> env.label JBoss Exceptions
>> env.regex_warnings Concurrent
>> env.label_warnings JBoss Concurrent Call Exception
>>
>> [loggrep_jboss]
>> env.logfile /opt/jboss/server/default/log/server.log
>> env.title JBoss Exceptions
> 
> Not sure why you keep them in two sections, but it should work just
> fine, and munin-run --debug loggrep_jboss should verify that.
> 
> ... The most trivial fault that can lead to a non-listed plugin working
> if you know it's there is not restarting the node at the right time.
> But that does not seem all that likely.  Right?
> 
> Nicolai
> 
> 
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
> _______________________________________________
> munin-users mailing list
> mun...@li...
> https://lists.sourceforge.net/lists/listinfo/munin-users
>