OVH Community, votre nouvel espace communautaire.

Pb avec le contenu HTML de Munin


bbr
11/10/2014, 14h00
je l'installe et configure comme ceci : http://www.how-to.ovh/viewtopic.php?f=10&t=18

elekaj34
11/10/2014, 12h30
Bonjour,

Sur une install débian wheezy, j'installe les paquets de munin et munin-node.
Je configure munin comme suit (munin.conf) (ip anonymisée et commetaires supprimés)

Code:
dbdir	/var/lib/munin
htmldir /var/www/munin
logdir /var/log/munin
rundir  /var/run/munin
tmpldir	/etc/munin/templates

includedir /etc/munin/munin-conf.d

graph_strategy cron
html_strategy cron

[vega]
    address 127.0.0.1

[ns2]
    address 1.2.3.4

[altair]
    address 5.6.7.8
Tout cre passe bien ou presque (cf ligne en gras) de munin-update.log

2014/10/11 13:15:01 [INFO]: Starting munin-update
2014/10/11 13:15:01 [INFO] starting work in 29094 for altair/5.6.7.8:4949.
2014/10/11 13:15:01 [INFO] starting work in 29095 for ns2/1.2.3.4:4949.
2014/10/11 13:15:01 [INFO] starting work in 29096 for vega/127.0.0.1:4949.
2014/10/11 13:15:01 [WARNING] Config node ns2 listed no services for ns2. Please see http://munin-monitoring.org/wiki/FAQ_no_graphs for further information.
2014/10/11 13:15:01 [INFO]: Munin-update finished for node ns2;ns2 (0.15 sec)
2014/10/11 13:15:02 [INFO]: Munin-update finished for node altair;altair (1.18 sec)
2014/10/11 13:15:02 [INFO] Reaping Munin::Master::UpdateWorker. Exit value/signal: 0/0
2014/10/11 13:15:04 [INFO]: Munin-update finished for node vega;vega (2.22 sec)
2014/10/11 13:15:04 [INFO] Reaping Munin::Master::UpdateWorker. Exit value/signal: 0/0
2014/10/11 13:15:04 [INFO] Reaping Munin::Master::UpdateWorker. Exit value/signal: 0/0
2014/10/11 13:15:04 [INFO]: Munin-update finished (2.32 sec)
Le munin-html.log
2014/10/11 13:10:04 [INFO] config generated (0.06 sec)
2014/10/11 13:10:04 [INFO] Starting munin-html, getting lock /var/run/munin/munin-html.lock
2014/10/11 13:10:04 [INFO] Creating problem page /var/www/munin/problems.html
2014/10/11 13:10:04 [INFO] Releasing lock file /var/run/munin/munin-html.lock
2014/10/11 13:10:04 [INFO] munin-html finished (0.46 sec)
2014/10/11 13:15:04 [INFO] config generated (0.06 sec)
2014/10/11 13:15:04 [INFO] Starting munin-html, getting lock /var/run/munin/munin-html.lock
2014/10/11 13:15:04 [INFO] Creating problem page /var/www/munin/problems.html
2014/10/11 13:15:04 [INFO] Releasing lock file /var/run/munin/munin-html.lock
2014/10/11 13:15:04 [INFO] munin-html finished (0.46 sec)
Le munin-graph.log est vide

Mais quand je regarde l’interface web de munin, la page index ne me fait apparaitre que localhost
Et celle-ci a été générée le 10 oct à 15H25 (heure de l'install de munin) et les modifs de config de munin faites ensuite ne semblent pas prises en compte (y compris sur le localhost)
Pourtant j'ai bien redémarré munin et munin-node.

Si je supprime le contenu de /var/www/munin, le contenu est regénéré, mais la page d'index ne change pas a priori (la date de génération reste le 10 oct à 15H25)

Des idées ?
Donc comment ajouter des nodes à munin et que les modifs soient prises en compte.

Autre étrangetée : dans /var/www/munin, j'ai plusieurs fichiers html, si je tapes l'url de munin dans mon navigateurs, j'ai une erreur 404
Ex de ls /var/www/munin
altair mysql-day.html postfix-week.html system-week.html
apache-day.html mysql-month.html postfix-year.html system-year.html
apache-month.html mysql-week.html problems.html time-day.html
apache-week.html mysql-year.html processes-day.html time-month.html
apache-year.html network-day.html processes-month.html time-week.html
disk-day.html network-month.html processes-week.html time-year.html
disk-month.html network-week.html processes-year.html vega
disk-week.html network-year.html static
disk-year.html postfix-day.html system-day.html
index.html postfix-month.html system-month.html
Et bien si je saisi "http://192.168.0.100/munin/apache-day.html, j'ai une erreur 404