On 6/25/2012 10:03 AM, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the munin package: > > #678928: Squeeze safe-upgrade pulled munin 2.0.0-1~bpo60+1, graphs won't > display > > It has been closed by Holger Levsen <hol...@layer-acht.org>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Holger Levsen > <hol...@layer-acht.org> by > replying to this email.
Hi Holger, You misread my report, and closed this prematurely. Note that I simply kept my original config files during safe-upgrade. When munin didn't work, I replaced them withe the new 2.0 files provided by the upgrade process. Munin still didn't work. I followed the instructions you linked, including the lighttpd configuration here: http://munin-monitoring.org/wiki/CgiHowto2 and it still doesn't work. The cgi and html processes launch but hang. According to this: The FastCGI processes will log to "/var/log/munin/munin-cgi-graph.log" and "/var/log/munin/munin-cgi-html.log". Note that these run with the web server's permissions, unless specified otherwise. If the web server does not have write access to the specific log files (or access to the directory they are in), the cgi processes will hang, and not produce any output. they should only hang when write access isn't present. But there are entries in these log files, though it seems they're not complete, so maybe one process can write them but no all the processes that need to: [root@greer]/var/log/munin$ cat munin-cgi-graph.log 2012/06/25 11:23:34 Opened log file 2012/06/25 11:23:34 Opened log file 2012/06/25 11:23:34 Opened log file 2012/06/25 11:23:35 Opened log file [root@greer]/var/log/munin$ cat munin-cgi-html.log 2012/06/25 11:23:32 Opened log file 2012/06/25 11:23:33 Opened log file 2012/06/25 11:23:33 Opened log file 2012/06/25 11:23:33 Opened log file If indeed it's a permissions issue, why doesn't the installer script set the correct permissions on these files automatically like most/all other packages do? When I installed munin 1.4.x I had zero problems getting it working. Why are so many contortions required to get the 2.0 upgrade working? The upgrade installer is simply broken. This isn't the Debian Stable I know and love. My big complaint is that an 'aptitude safe-upgrade' shouldn't install a package upgrade that is so completely broken and does not work without major surgery. The backports repo is supposed to contain stable working packages backported from testing, or so I thought. And frankly I'm surprised a safe-upgrade pulls packages from backports. I was under the impression it only pulls from the stable repo. And, no, I've never modified any apt preferences or whatever to cause it to pull packages from backports. I don't even know how this would be done. This is something that happened automatically. So what do I do now? Can 2.0 be made to work on my system? Or is it simply completely hosed? Should I file a bug report against the upgrade script? If so, how do I do that? What's the package name for it? I, the user, did nothing to break my munin. Fault lay with the developers. An upgrade shouldn't completely totally break a program so that it simply won't run at all, which is what has happened here. This is very frustrating to say the least. If this is not a bug, and a bug report isn't the proper place to receive troubleshooting assistance to get this working, where do you recommend I go for assistance? Please don't say "debian-users". I've been a subscriber for over 3 years. Munin is never discussed and there's likely no other munin users there who could help. Thanks. -- Stan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
