Package: munin
Version: 1.2.6-8
Severity: important

Hi,

installing a fresh munin and changing graph_strategy immediately causes
the munin-html job (which is still required) to fail:

| hugin:/var/www# apt-get install munin   libdate-manip-perl
| Reading package lists... Done
| Building dependency tree       
| Reading state information... Done
| libdate-manip-perl is already the newest version.
| The following NEW packages will be installed:
|   munin
| 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
| Need to get 609kB of archives.
| After this operation, 1020kB of additional disk space will be used.
| Get:1 http://mirror.came.sbg.ac.at lenny/main munin 1.2.6-8 [609kB]
| Fetched 609kB in 0s (22.7MB/s)
| Selecting previously deselected package munin.
| (Reading database ... 25489 files and directories currently installed.)
| Unpacking munin (from .../archives/munin_1.2.6-8_all.deb) ...
| Processing triggers for man-db ...
| Setting up munin (1.2.6-8) ...

| hugin:/var/www# vi /etc/munin/munin.conf
[enabling cgi mode]

| hugin:/var/www# cd munin/
| hugin:/var/www/munin# ls -la
| total 8
| drwxr-xr-x 2 munin munin 4096 Nov  8 15:59 ./
| drwxr-xr-x 3 root  root  4096 Feb  9 18:21 ../

| hugin:/var/www/munin# sudo -u munin sh -x munin-cron
| + '[' -x /usr/share/munin/munin-update ']'
| + /usr/share/munin/munin-update
| + '[' -x /usr/share/munin/munin-limits ']'
| + /usr/share/munin/munin-limits
| + '[' -x /usr/share/munin/munin-graph ']'
| + nice /usr/share/munin/munin-graph --cron
| + fgrep -v '*** attempt to put segment in horiz list twice'
| + '[' -x /usr/share/munin/munin-html ']'
| + nice /usr/share/munin/munin-html
| Cannot open /var/www/munin/localdomain/localhost.localdomain-cpu.html: No 
such f

The localdomain directory in this case would have been created by
munin-graph, but since the graph_strategy was changed to cgi it exits
doing nothing.

Please fix this for lenny r1.

Cheers,
Peter



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to