Your message dated Wed, 26 Dec 2012 12:06:40 +0100 with message-id <[email protected]> and subject line I'd call that a feature has caused the Debian Bug report #675178, regarding munin-node: All munin plugins fail with error "Unable to set umask" in Service.pm to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 675178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675178 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: munin-node Version: 2.0~rc6-3 Severity: important Dear Maintainer, The problem appeared after recent update to munin 2.0, two days ago. All plugins stopped working or at least munin cannot retrieve their results. Looking into /var/lib/munin/mydomain directory, the *.rrd files did update regularly. I did see the files change between the munin upgrade and at least half an hour ago. However, the graph files were not displayed and I don't see any image files. So I tried to locate the problem, and run munin-node-configure --suggest. All plugins have a suggestion column set to "no" and in fact at the end of the report, all of them did encounter a first error. Here is an excerpt of this final reporting error: [snip] # The following plugins caused errors: # acpi: # Non-zero exit during autoconf (255) # amavis: # Non-zero exit during autoconf (255) # apache_accesses: # Non-zero exit during autoconf (255) # apache_processes: # Non-zero exit during autoconf (255) # apache_volume: # Non-zero exit during autoconf (255) [snip] I did reinstall autoconf, but the problem was still there. I looked at the /var/log/munin/munin-node.log file and found hundreds of lines with an error about Service.pm being unable to set umasq: [snip] 2012/05/30-12:40:04 [11406] Error output from uptime: 2012/05/30-12:40:04 [11406] 2012/05/30-12:40:04 [11417] Unable to set umask: \n at /usr/share/perl5/Munin/Node/Service.pm line 244 2012/05/30-12:40:04 [11406] Error output from uptime: 2012/05/30-12:40:04 [11406] 2012/05/30-12:40:04 [11418] Unable to set umask: \n at /usr/share/perl5/Munin/Node/Service.pm line 244 2012/05/30-12:40:04 [11406] Error output from load: 2012/05/30-12:40:04 [11406] 2012/05/30-12:40:04 [11419] Unable to set umask: \n at /usr/share/perl5/Munin/Node/Service.pm line 244 [snip] The same error appear if I try to run one service from command-line as shown below: root@b3:/var/lib/munin# munin-run --debug uptime # Processing plugin configuration from /etc/munin/plugin-conf.d/munin-node # Setting /rgid/ruid/ to /117/65534/ # Setting /egid/euid/ to /117 117/65534/ # Setting up environment Unable to set umask: at /usr/share/perl5/Munin/Node/Service.pm line 244 root@b3:/var/lib/munin# Line 244 of file Service.pm is: Munin::Node::OS::set_umask(); Since I did the various attempts above, the rrd files stopped updating. The munin-node.log file updates and always shows the same errors, but not the rrd files. Note that in the /var/lib/munin directory, the date of the files state-mydomain-myhost-mydomain.storable, munin-update.stats, datafile.storable, datafile, limits, and graphs do update (despite graphs remains empty), but htmlconf.storable file stopped updating when I did these attempts (this morning), despite it did updates since last 2 days, after upgrade. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (980, 'stable-updates'), (980, 'stable'), (90, 'experimental'), (90, 'unstable') Architecture: armel (armv5tel) Kernel: Linux 2.6.39.4-11 Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages munin-node depends on: ii adduser 3.113+nmu2 ii gawk 1:4.0.1+dfsg-1 ii libnet-server-perl 0.99-4 ii lsb-base 4.1+Debian4 ii munin-common 2.0~rc6-3 ii munin-plugins-core [munin-plugins] 2.0~rc6-3 ii perl 5.14.2-11 ii procps 1:3.3.2-3 Versions of packages munin-node recommends: ii libnet-snmp-perl 6.0.1-2 ii munin-plugins-core 2.0~rc6-3 Versions of packages munin-node suggests: pn ethtool 1:3.2-1 pn hdparm <none> pn libcache-cache-perl 1.06-2 pn libcrypt-ssleay-perl 0.58-1 pn libdbd-mysql-perl <none> pn libdbd-pg-perl <none> pn liblwp-useragent-determined-perl <none> pn libnet-irc-perl <none> pn libtext-csv-xs-perl <none> pn libwww-perl 6.04-1 pn libxml-simple-perl 2.18-3 pn lm-sensors 1:3.3.2-1 pn logtail <none> pn munin 2.0~rc6-3 pn munin-java-plugins <none> pn munin-plugins-extra <none> pn mysql-client <none> pn net-tools 1.60-24.1 pn python 2.7.2-10 pn ruby1.8 [ruby] 1.8.7.352-2 pn smartmontools <none> -- Configuration Files: /etc/munin/plugin-conf.d/munin-node [Errno 13] Permission denied: u'/etc/munin/plugin-conf.d/munin-node' -- no debconf information
--- End Message ---
--- Begin Message ---Hi, if munin fails cause your systems umask is set to 0000, I'd call it a feature ;-) Having umask set to 0000 system wide is a recipe for desaster. Thus closing this bug report. cheers, Holger
--- End Message ---
