[munin-users] Munin 2.0.25 (Debian jessie) renders wrong URL paths

[Gregor H. <gre...@me...>]

Hi,

we used Munin 2.0.6 on Debian 7 for years.

Now, after upgrading to Debian 8, I fail to find any working configuration for the Munin web frontend (2.0.25, as included with Debian).

We're using Apache 2.4 and fcgid (Debian packages for both).

To start with the best: I managed to set up a working configuration on http://localhost/munin/.

I used "html_strategy cron" und "graph_strategy cgi" and only this small snippet in the Apache 2.4 configuration of http://localhost:

        Alias /munin /var/cache/munin/www
        <Directory /var/cache/munin/www>
                Require local
                Options None
        </Directory>

        ScriptAlias /munin-cgi/munin-cgi-graph /usr/lib/munin/cgi/munin-cgi-graph
        <Location /munin-cgi/munin-cgi-graph>
                Require local
                <IfModule mod_fcgid.c>
                    SetHandler fcgid-script
                </IfModule>
                <IfModule !mod_fcgid.c>
                    SetHandler cgi-script
                </IfModule>
        </Location>


This configuration even works through an SSH tunnel (such as "ssh -L 8082:localhost:80 root@example" and then http://localhost:8082/munin/).


But I completely fail to set up a configuration that works on an external address.




Example 1:

Using the examples from http://munin-monitoring.org/wiki/MuninConfigurationMasterCGI (using "html_strategy cgi" and "graph_strategy cgi"), the start page works fine (on the URL https://mymunin.example.com/). But any subpage is rendered without CSS etc., as plain text. The problems are that the URLs of the resources, e.g.: https://mymunin.example.com/example.com/static/style-new.css.

Also, when traversing the pages, I end up with paths that got longer each links, like https://mymunin.example.com/example.com/example.com/host01.example.com/examples.com/host02.example.com//index.html#network.

I got down to the point that obviously something is wrong with the calculation of R_PATH, but I don't know what.



Example 2:

When I try to setup another Virtual Host in Apache that works as a reverse proxy for the working installation on http://localhost/munin (see above), I end up with a configuration where the start page (now on https://mymunin.example.com/munin/!) loads, but fails to render the munin logo. All the pages bring errors like

    The requested URL /munin-cgi/munin-cgi-html//munin/example.com/host01.example.com/index.html was not found on this server.

(note the double slash).

For the logo (https://mymunin.example.com/munin/static/logo-h.png), the Apache serves an 404. On the localhost, the logo is loaded from the URL http://localhost/munin/static/logo-h.png without problem.

https://mymunin.example.com/ is defined like this:

        ProxyPreserveHost Off
        ProxyPass        / http://127.0.0.1:80/
        ProxyPassReverse / http://127.0.0.1:80/


I'm pretty clear that I'm missing something obvious, but at this point I have no idea where to go on.


I have tried various other things, as rewrite rules or aliases (e.g. for /static), none of which helped. I also tried the Debian Backports packages, which ship Munin 2.0.33.




I think at the moment my problem boils down to this question:



On a system with Debian 8, how do I setup a Munin frontend that works from an external address like https://mymunin.example.com/ (or https://mymunin.example.com/munin/)?

Should I even use the Debian packages or go on with an installation from source?



Best regards,
    Gregor Hoffleit


-- 
MediaSupervision Software Consulting GmbH - www.mediasupervision.de
Niederlassung: Carl-Theodor-Str. 5, 68723 Schwetzingen
Tel: +49 (0)6221 705079-22, E-Mail: gre...@me...
Hauptsitz: Georg-Friedrich-Händel-Str. 13, 69214 Eppelheim / Heidelberg
Amtsgericht Mannheim HRB 336821; Geschäftsführer: Reinhard Kratzke