Munin apache plugin bad response

apache-2.2munin

All my apache plugins returns the same value :

/usr/share/munin/plugins# munin-run apache_volume volume443.value U

Here is my config in /etc/munin/plugin-conf.d/munin-node

[apache_*] env.ports 443

Some have an idea where is the problem ?

Thanks in advance

Best Answer

I found the solution.

The apache scripts are not compatible with ssl. You have to use modified version on :
http://munin-monitoring.org/attachment/wiki/PluginCat/apache_volume
http://munin-monitoring.org/attachment/wiki/PluginCat/apache_accesses
http://munin-monitoring.org/attachment/wiki/PluginCat/apachessl_processes

Be sure to have the perl libraries LWP::UserAgent and Crypt::SSLeay installed

Modify also /etc/munin/plugin-conf.d/munin-node :
[apache_*] env.ports 443 env.url https://localhost:443/server-status?auto

It works fine after that ;-)

Related Solutions

Bash-Scripting – Munin Plugin don’t work

Do not check munin scripts with just direct scripts running. It's wrong way. There is special perl script munin-run that executes scripts exactly the same way as it runs during munin update and you'll able to find all errors. May be you'll need define special settings for you script. You can do it in /etc/munin/plugin-conf.d/munin-node file next way:

[script_file_mask_*]
user USER_FOR_YOR_SCRIPT
env.VARIABLE some_variable

In your case seems that script just hasn't tighr to read log file. So add

[lighttpd_*]
user root

in /etc/munin/plugin-conf.d/munin-node and restart munin-node. It should help.

Postgresql – Munin with postgresql 9.2

Turned out SELinux was blocking access to the socket.

setsebool -P allow_user_postgresql_connect on

Best Answer

Related Solutions

Bash-Scripting – Munin Plugin don’t work

Postgresql – Munin with postgresql 9.2

Related Topic