Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

apache2 + munin configuration

151 views
Skip to first unread message

rudu

unread,
Nov 12, 2013, 12:00:02 PM11/12/13
to
Hi,
Well, I wouldn't have thought having so many difficulties setting up a
simple monitoring system on my Jessie amd64 desktop, but after a few
hours wandering the net, I guess I could use some guidance ...

What I've done so far :
aptitude install apache2 munin munin-node
ii apache2 2.4.6-3 amd64 Apache HTTP
Server
ii munin 2.0.17-3 all
network-wide graphing framework (grapher/gatherer)
ii munin-node 2.0.17-3 all
network-wide graphing framework (node)

Then I tried to connect to http://localhost/munin only to get :
Forbidden
You don't have permission to access /munin on this server.
Apache/2.4.6 (Debian) Server at localhost Port 80

I found some threads here and there via google which lead me to try
several things.
First in /etc/munin/apache.conf :
replace

<Directory /var/cache/munin/www>
Order allow,deny
Allow from localhost 127.0.0.0/8 ::1

Options None
[...]
</Directory>

by

<Directory /var/cache/munin/www>
Order allow,deny
Allow from all

Options None
[...]
</Directory>

Then I did :
chown -R www-data:munin /var/cache/munin/www
chmod -R 775 /var/cache/munin/www

I even added my user to the munin group
But I still get this error 403 from apache.

FWIW I got this in /var/log/apache2/error.log :
[Tue Nov 12 17:53:03.987560 2013] [authz_core:error] [pid 2758:tid
139900372383488] [client ::1:53049] AH01630: client denied by server
configuration: /var/cache/munin/www

Thanks for any help.
Rudu


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/52825D71...@cegetel.net

Vicios

unread,
Nov 13, 2013, 3:40:01 AM11/13/13
to
Hi!

I don't know why your configuration doesn't work. When I install Munin
always add my subnet in the config file, for example:

[...]
Allow from localhost 127.0.0.0/8 ::1 192.168.0.0/24
[...]

Regards.
Fernando.

El 12/11/13 17:55, rudu escribió:
Archive: http://lists.debian.org/52833AB...@gmail.com

rudu

unread,
Nov 13, 2013, 4:20:02 AM11/13/13
to
Le 13/11/2013 09:39, Vicios a écrit :
> Hi!
>
> I don't know why your configuration doesn't work. When I install Munin
> always add my subnet in the config file, for example:
>
> [...]
> Allow from localhost 127.0.0.0/8 ::1 192.168.0.0/24
> [...]
>
> Regards.
> Fernando.

Thank for the suggestion Fernando.
I tried but still no luck.

Rudu
Archive: http://lists.debian.org/52834394...@cegetel.net

Karl E. Jorgensen

unread,
Nov 13, 2013, 5:50:01 AM11/13/13
to
Hi

On Tue, Nov 12, 2013 at 05:55:13PM +0100, rudu wrote:
> Hi,
> Well, I wouldn't have thought having so many difficulties setting up
> a simple monitoring system on my Jessie amd64 desktop, but after a
> few hours wandering the net, I guess I could use some guidance ...
>
> What I've done so far :
> aptitude install apache2 munin munin-node
> ii apache2 2.4.6-3 amd64 Apache
> HTTP Server
> ii munin 2.0.17-3 all
> network-wide graphing framework (grapher/gatherer)
> ii munin-node 2.0.17-3 all
> network-wide graphing framework (node)
>
> Then I tried to connect to http://localhost/munin only to get :
> Forbidden
> You don't have permission to access /munin on this server.
> Apache/2.4.6 (Debian) Server at localhost Port 80

At this point, your first stop should be the apache error log...

>
> I found some threads here and there via google which lead me to try
> several things.
> First in /etc/munin/apache.conf :
> replace
>
> <Directory /var/cache/munin/www>
> Order allow,deny
> Allow from localhost 127.0.0.0/8 ::1
>
> Options None
> [...]
> </Directory>
>
> by
>
> <Directory /var/cache/munin/www>
> Order allow,deny
> Allow from all
>
> Options None
> [...]
> </Directory>

Hm.. Either should work.

If it had no effect, then I suggest you revert that out before doing
other changes.

> Then I did :
> chown -R www-data:munin /var/cache/munin/www
> chmod -R 775 /var/cache/munin/www
>
> I even added my user to the munin group

This would have no effect... I suggest you tidy up again by undoing
that.

> But I still get this error 403 from apache.
>
> FWIW I got this in /var/log/apache2/error.log :
> [Tue Nov 12 17:53:03.987560 2013] [authz_core:error] [pid 2758:tid
> 139900372383488] [client ::1:53049] AH01630: client denied by server
> configuration: /var/cache/munin/www

Hm.. That is reasonably conclusive...

But there is a clue: authz_core ... Isn't that the apache module that
is used for user authentication?

Makes me wonder what the rest of your apache configuration is like -
there must be some interaction between munin and other things in
apache...

Hope this helps
--
Karl E. Jorgensen


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20131113104910.GI11883@hawking

Darac Marjal

unread,
Nov 13, 2013, 6:30:02 AM11/13/13
to
If you're running Apache 2.4 (which you are), you should add "Require
all granted" below the Allow/Deny statements. This basically tells the
new authorisation module to honour the configuration of the older
module.

signature.asc

rudu

unread,
Nov 13, 2013, 6:40:02 AM11/13/13
to
Le 13/11/2013 11:49, Karl E. Jorgensen a écrit :
> Hi
>
> On Tue, Nov 12, 2013 at 05:55:13PM +0100, rudu wrote:
>> Hi,
>> Well, I wouldn't have thought having so many difficulties setting up
>> a simple monitoring system on my Jessie amd64 desktop, but after a
>> few hours wandering the net, I guess I could use some guidance ...
>>
>> What I've done so far :
>> aptitude install apache2 munin munin-node
>> ii apache2 2.4.6-3 amd64 Apache
>> HTTP Server
>> ii munin 2.0.17-3 all
>> network-wide graphing framework (grapher/gatherer)
>> ii munin-node 2.0.17-3 all
>> network-wide graphing framework (node)
>>
>> Then I tried to connect tohttp://localhost/munin only to get :
>> Forbidden
>> You don't have permission to access /munin on this server.
>> Apache/2.4.6 (Debian) Server at localhost Port 80
> At this point, your first stop should be the apache error log...
[...]
>
>> But I still get this error 403 from apache.
>>
>> FWIW I got this in /var/log/apache2/error.log :
>> [Tue Nov 12 17:53:03.987560 2013] [authz_core:error] [pid 2758:tid
>> 139900372383488] [client ::1:53049] AH01630: client denied by server
>> configuration: /var/cache/munin/www
> Hm.. That is reasonably conclusive...
>
> But there is a clue: authz_core ... Isn't that the apache module that
> is used for user authentication?
>
> Makes me wonder what the rest of your apache configuration is like -
> there must be some interaction between munin and other things in
> apache...
>
> Hope this helps
Hello Karl,
Thanks for your help.

I guess this is an apache2 config problem ...
FWIW, here is my /etc/apache2/apache2.conf file :
http://cjoint.com/?CKnmznaq7cZ

There's a symlink of /etc/munin/apache2.conf in
/etc/apache2/conf-{available|enabled}/
Should'nt there be something in sites-enabled too ?
# ls -al /etc/apache2/sites-enabled/
total 8
drwxr-xr-x 2 root root 4096 août 12 21:02 .
drwxr-xr-x 8 root root 4096 nov. 13 12:19 ..

Regards,
Rudu


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/528364C3...@cegetel.net

rudu

unread,
Nov 13, 2013, 6:50:01 AM11/13/13
to
Le 13/11/2013 12:22, Darac Marjal a écrit :
> If you're running Apache 2.4 (which you are), you should add "Require
> all granted" below the Allow/Deny statements. This basically tells the
> new authorisation module to honour the configuration of the older
> module.

Brilliant Darac !
That did it nicely.

Thanks to Karl and Fernando too.

;c)

Rudu


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/528366B5...@cegetel.net
0 new messages