default apache config causes an empty webpage on lucid

[Teun Vink]

Binary package hint: munin

the default apache include for munin on lucid causes an empty webpage to be shown, due to the "Options None" entry. Changing it to "Options Indexes" actually shows a munin webpage.

[Andreas Olsson (andol)]

Not really sure I understand the symptoms you are experiencing.

First of all I assume you are accessing /munin/ by http://localhost/munin/? Based on the default configuration in /etc/munin/apache.conf (symlinked from /etc/apache2/conf.d/munin) it shouldn't be accessible at all from a remote host.

Secondly I have a hard time seeing how "Options Indexes" should do any difference, as munin webpage is an actual index.html file, no a directory index. Might the explaination be that when you first, before modifying your apache configuration, there hadn't yet been a index.html generated inside the /var/cache/munin/www/? Could there be something which I have misunderstood?

Can you try to reproduce the problem, with the original "Options None", while at the same time verify the existence of the file /var/cache/munin/www/index.html?

[Chuck Short (zulcss)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Teun Vink (teunvink)]

I agree that this shouldn't solve the problem. I can't repoduce it
right now, since the box is running production now. I've tried it a
couple of times before reporting the bug. Unless something really
strange is going on, I can think of 2 other explanations: apache
restart didn't happen properly (which it should) or the indexpage
hadn't been generated, however, there should've been a 404 in that
case, not blank page.

Regards,
teun

On Mar 9, 2010, at 9:21 PM, Andreas Olsson wrote:

> Not really sure I understand the symptoms you are experiencing.
>
> First of all I assume you are accessing /munin/ by
> http://localhost/munin/? Based on the default configuration in
> /etc/munin/apache.conf (symlinked from /etc/apache2/conf.d/munin) it
> shouldn't be accessible at all from a remote host.
>
> Secondly I have a hard time seeing how "Options Indexes" should do any
> difference, as munin webpage is an actual index.html file, no a
> directory index. Might the explaination be that when you first, before
> modifying your apache configuration, there hadn't yet been a
> index.html
> generated inside the /var/cache/munin/www/? Could there be something
> which I have misunderstood?
>
> Can you try to reproduce the problem, with the original "Options
> None",
> while at the same time verify the existence of the file
> /var/cache/munin/www/index.html?
>
> --
> default apache config causes an empty webpage on lucid
> https://bugs.launchpad.net/bugs/534647
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “munin” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: munin
>
> the default apache include for munin on lucid causes an empty
> webpage to be shown, due to the "Options None" entry. Changing it to
> "Options Indexes" actually shows a munin webpage.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/munin/+bug/534647/+subscribe

[Simon Gornall (simon-gornall)]

So, I've just had the same problem, though changing the Options (to either 'Indexes' or 'All') doesn't solve the problem for me.

This is a fresh install of munin, on a system freshly upgraded to 2.6.32-21-server running x86_64.

I had changed the permissions on the /etc/munin/apache.conf to read:

    Allow from localhost 127.0.0.0/8 192.168.1.1/24 ::1

... so I could see the data from another host on my internal LAN. The page delivered, however, is just blank. Selecting 'view source' gives me an empty window (no source). At first I assumed it was an apache config issue, even if I couldn't find anything wrong, but copying the munin 'index.html' file to 'test.xx' and requesting the url http://192.168.1.201/munin/test.xx resulted in the file being downloaded correctly to the desktop.

Similarly, requesting http://192.168.1.201/munin/localdomain/localhost.localdomain/cpu-day.png shows me a graph that does update in real-time if I re-request it, so the system is working, it's just not showing me the graphs by default.

Simon.

[Teun Vink (teunvink)]

I tried reproducing this bug on a fresh lucid install (instead of the original box which was an upgraded karmic install), but failed, it seems to work properly now.

[Simon Gornall (simon-gornall)]

Ah - so my machine is also an upgrade (actually from 'Intrepid Ibex', it's been out-of-commission for a while :). Perhaps there's the common thread.

Simon

[Brice Terzaghi (terzag)]

I have a similar problem on personal webpages after upgrading my server to Lucid. Some others of my pages work and I'm trying to find the origin of the problem.

It isn't related to Munin as I don't use it and the problem shows up only on a few pages I've coded.

When using wget to download a problematic page, I get an error 500 message so I'm not sure it is related to the pages themselves (which worked fined before the upgrade) or to some Apache configuration.

[Brice Terzaghi (terzag)]

Well, I've narrowed my problem to its source and it's not a bug from Apache or PHP but a coding issue from me: I used a custom function named goto() and it seems that since PHP 5.3, goto is the name of a new operator.

[joecarter (joe-carter)]

I upgraded from Karmic and hit 403 errors on the munin directory.
Changing the allow option to "Allow from all" and "Options Indexes" showed me an empty directory instead of a 403.
Removing the /etc/apache.d/conf/munin symbolic link to /etc/munin/apache.conf fixed the problem for me.

[Christian Matt (cmf)]

Is there any chance to get that 403 problem fixed?
Still get it on a new installed 10.04 and an upgraded 9.10.

[Launchpad Janitor (janitor)]

[Expired for munin (Ubuntu) because there has been no activity for 60 days.]