Package: munin
Version: 2.0~rc4-1
Severity: important
Dear Maintainer,
munin-cgi-graph and munin-cgi-html fail to start under default
installation.
The respective log files have the correct permissions
set with dpkg-statoverride (owned by www-data:adm), however the
dircetory /var/log/munin is owned by munin:adm, with permissions
0750. This blocks munin-cgi-* from accessing the log files.
I recommend changing the permissions on /var/log/munin to 0751,
which is what I did, or apply some other way to allow access by
www-data.
I am running lighttpd 1.4.30 as my web server.
Cheers,
Chen-Yu Tsai
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these lines ***
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5 (charmap=BIG5)
Shell: /bin/sh linked to /bin/dash
Versions of packages munin depends on:
ii adduser 3.113+nmu1
ii cron 3.0pl1-121
ii libcgi-fast-perl 5.14.2-9
ii libdate-manip-perl 6.31-1
ii libdigest-md5-perl <none>
ii libfile-copy-recursive-perl 0.38-1
ii libhtml-template-perl 2.10-1
ii libio-socket-inet6-perl 2.69-2
ii liblog-log4perl-perl 1.29-1
ii librrds-perl 1.4.7-1
ii libstorable-perl <none>
ii liburi-perl 1.59-1
ii munin-common 2.0~rc4-1
ii perl [libtime-hires-perl] 5.14.2-9
ii perl-modules 5.14.2-9
ii rrdtool 1.4.7-1
ii ttf-dejavu 2.33-2
Versions of packages munin recommends:
ii munin-doc <none>
ii munin-node 2.0~rc4-1
Versions of packages munin suggests:
pn libnet-ssleay-perl 1.45-1
pn lighttpd [httpd] 1.4.30-1
pn www-browser <none>
-- Configuration Files:
/etc/munin/munin.conf changed [not included]
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
