Re: [munin-users] -nan with apache plugin, works manually

[Axel B. <axe...@gm...>]

Hi Ralph,

great. I am so ... forgetful. Yes I changed the ports of the virtual host
which has server-status configured. It _used_ to he 6864. Works like a
charm now I reconfigured the plugin.

What irritates me though is that the plugin used to work when called
manually - it does not read the plugin config files, it seems.


Thank you so much & greetings,
Axel.


2013/3/20 Kenyon Ralph <ke...@ke...>

> On 2013-03-20T17:13:26+0100, Axel Bock <axe...@gm...> wrote:
> > I have this annoying problem with the apache_* plugins. I have them
> > configured to work with "localhost:80" as server, a virtual host which
> > _only_ listens on 127.0.0.1.
> >
> > when called manually (e.g. "./apache_volume") the plugin delivers the
> > values all right. the vhost is properly configured, also also "<plugin>
> > autoconf" returns "yes".
>
> How about when run with munin-run, e.g.,
>
> sudo munin-run apache_volume
>
> > when called via the telnet interface I get this:
> >
> > fetch apache_volume
> > volume6864.value U
>
> Where is this 6864 coming from? That is the port number. Do you have
> this port configured in your /etc/munin/plugin-conf.d/munin-node (or
> equivalent)?
>
> --
> Kenyon Ralph
>
>
> ------------------------------------------------------------------------------
> 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_mar
> _______________________________________________
> munin-users mailing list
> mun...@li...
> https://lists.sourceforge.net/lists/listinfo/munin-users
>
>