[Bug 616962] Re: munin after install: 403 forbidden
*** This bug is a duplicate of bug 534647 *** https://bugs.launchpad.net/bugs/534647 This is my third try to write a reply. Startet writing and solved the problem on my first machine. Then I wrote about the other machine and solved the problem there. It was just misconfiguration by myself in (both) /etc/munin/apache.conf. Thank you for (indirectly) guiding me to the solution :) -- munin after install: 403 forbidden https://bugs.launchpad.net/bugs/616962 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 616962] Re: munin after install: 403 forbidden
** Changed in: munin (Ubuntu) Status: New = Incomplete -- munin after install: 403 forbidden https://bugs.launchpad.net/bugs/616962 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 616962] Re: munin after install: 403 forbidden
Hi Christian, thank you for reporting this bug and working with us to make ubuntu better! The NEWS.Debian file does in fact mention this problem: munin (1.4.0-1) unstable; urgency=low Move htmldir to /var/cache/munin/www. Note that we currently don't have a proper upgrade mechanism in place. When upgrading from a previous version of munin, you'll need to change /etc/munin/munin.conf htmldir parameter, from /var/www/munin, to /var/cache/munin/www. So, when upgrading, you do need to do some manual reconfiguration. Adding this capability would be nice, and is probably worthy of a separate wishlist bug explaining exactly what you would expect to see on upgrade. The package does, by default, restrict access to 127.0.0.1 only, so you should see it when hitting http://localhost from the machine itself. More complex access controls will require you to define exactly what you want. For the rest of it, I suspect your configuration is the problem, and so I'm marking this incomplete. Please post your apache configuration files so we can ascertain what might be causing the 403. Also you may want to look in /var/log/apache2/error.log for some clues. -- munin after install: 403 forbidden https://bugs.launchpad.net/bugs/616962 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 616962] Re: munin after install: 403 forbidden
*** This bug is a duplicate of bug 534647 *** https://bugs.launchpad.net/bugs/534647 ** This bug has been marked a duplicate of bug 534647 default apache config causes an empty webpage on lucid -- munin after install: 403 forbidden https://bugs.launchpad.net/bugs/616962 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
