Bug#905457: munin: general protection fault
Lars Kruse a écrit : > Hello Bertrand, > > > Am Sun, 5 Aug 2018 10:01:58 +0200 > schrieb BERTRAND Joël : > >> Yesterday, after my bug report, I have done a apt dist-upgrade and this >> message disappears. Very strange, perl and munin were not upgraded. > > What a pity - this issue looked mysteriously interesting :) > > I fail to have an idea, which kind of magic could have pushed this error > message line to your log. > > Let's agree on closing this bug as "unreproducible" and hoping for the monster > to never return again? Of course, you can close this bug. JKB
Bug#905457: munin: general protection fault
Hello Bertrand, Am Sun, 5 Aug 2018 10:01:58 +0200 schrieb BERTRAND Joël : > Yesterday, after my bug report, I have done a apt dist-upgrade and this > message disappears. Very strange, perl and munin were not upgraded. What a pity - this issue looked mysteriously interesting :) I fail to have an idea, which kind of magic could have pushed this error message line to your log. Let's agree on closing this bug as "unreproducible" and hoping for the monster to never return again? Cheers, Lars
Bug#905457: munin: general protection fault
Lars Kruse a écrit : > Package: munin > Followup-For: Bug #905457 > > Hello Bertrand, Hello Lars, > On Sat, 04 Aug 2018 22:35:54 +0200, BERTRAND Joël wrote, > >> I don't understand why perl tries to run /usr/sbin/munin, there is no >> such script nor executable. > > indeed there is no such file shipped in any munin package. > > I just tried to reproduce this issue on a fresh and up-to-date buster > system. But I failed to find this log message here on my host. > > I could only imagine the following two sources of this log messages > (both of which feel equally unlikely): > 1) a locally installed munin plugin I don't have this kind of plugins. > 2) a cron-job that is not related to the packaged "munin-cron" > > For 1) you could take a look at /etc/munin/plugins/ and check for > non-packaged plugins. > For 2) you could temporarily disable the "munin-cron" cron job and check > whether the mysterious log message still appears. > > Or maybe you have a different idea how to trace the origin of this > message? Yesterday, after my bug report, I have done a apt dist-upgrade and this message disappears. Very strange, perl and munin were not upgraded. Best regards, JB
Bug#905457: munin: general protection fault
Package: munin Followup-For: Bug #905457 Hello Bertrand, On Sat, 04 Aug 2018 22:35:54 +0200, BERTRAND Joël wrote, > I don't understand why perl tries to run /usr/sbin/munin, there is no > such script nor executable. indeed there is no such file shipped in any munin package. I just tried to reproduce this issue on a fresh and up-to-date buster system. But I failed to find this log message here on my host. I could only imagine the following two sources of this log messages (both of which feel equally unlikely): 1) a locally installed munin plugin 2) a cron-job that is not related to the packaged "munin-cron" For 1) you could take a look at /etc/munin/plugins/ and check for non-packaged plugins. For 2) you could temporarily disable the "munin-cron" cron job and check whether the mysterious log message still appears. Or maybe you have a different idea how to trace the origin of this message? Cheers, Lars
Bug#905457: munin: general protection fault
Package: munin Version: 2.0.37-2 Severity: important Dear Maintainer, I run debian testing (buster) and since a few days, munin doesn't run as expected. In syslog, I have a lot of : Aug 4 22:35:01 rayleigh CRON[11229]: (munin) CMD (if [ -x /usr/bin/munin-cron ]; then /usr/bin/munin-cron; fi > /dev/null 2>&1) Aug 4 22:35:02 rayleigh kernel: [986015.327521] traps: /usr/sbin/munin[11238] general protection ip:559e936f2282 sp:71816870 error:0 in perl[559e93627000+1f8000] Aug I don't understand why perl tries to run /usr/sbin/munin, there is no such script nor executable. Best regards, JB -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages munin depends on: ii cron [cron-daemon]3.0pl1-130 ii fonts-dejavu-core 2.37-1 ii libdate-manip-perl6.72-1 pn libdigest-md5-perl ii libfile-copy-recursive-perl 0.44-1 ii libhtml-template-perl 2.97-1 ii libio-socket-inet6-perl 2.72-2 ii liblog-log4perl-perl 1.49-1 ii libperl5.22 [libtime-hires-perl] 5.22.2-5 ii libperl5.24 [libtime-hires-perl] 5.24.1-7 ii librrds-perl 1.7.0-1+b2 pn libstorable-perl ii liburi-perl 1.74-1 ii lsb-base 9.20170808 ii munin-common 2.0.37-2 ii perl [libtime-hires-perl] 5.26.2-6 ii rrdtool 1.7.0-1+b2 ii systemd-sysv 239-7 Versions of packages munin recommends: ii libcgi-fast-perl 1:2.13-1 ii munin-doc 2.0.37-2 ii munin-node2.0.37-2 Versions of packages munin suggests: iu apache2 [httpd]2.4.34-1 ii elinks [www-browser] 0.12~pre6-13 ii firefox [www-browser] 61.0.1-1 ii iceape [www-browser] 2.7.12-1+b1 ii konqueror [www-browser]4:18.04.0-1 pn libapache2-mod-fcgid ii libnet-ssleay-perl 1.85-1 ii links [www-browser]2.16-1 ii lynx [www-browser] 2.8.9rel.1-1 ii seamonkey-mozilla-build [www-browser] 2.49.3-0ubuntu1 ii w3m [www-browser] 0.5.3-36+b1 -- Configuration Files: /etc/cron.d/munin changed: MAILTO=root */5 * * * * munin if [ -x /usr/bin/munin-cron ]; then /usr/bin/munin-cron; fi > /dev/null 2>&1 14 10 * * * munin if [ -x /usr/share/munin/munin-limits ]; then /usr/share/munin/munin-limits --force --contact nagios --contact old-nagios; fi /etc/munin/munin.conf changed: dbdir /var/lib/munin htmldir /var/cache/munin/www logdir /var/log/munin rundir /var/run/munin tmpldir /etc/munin/templates staticdir /etc/munin/static cgitmpdir /var/lib/munin/cgi-tmp includedir /etc/munin/munin-conf.d graph_period second graph_strategy cron munin_cgi_graph_jobs 6 html_strategy cron [rayleigh.systella.fr] address 127.0.0.1 use_node_name yes [legendre.systella.fr] address 192.168.1.2 use_node_name yes [pythagore.systella.fr] address 192.168.10.102 use_node_name yes [cervantes.systella.net] address 192.168.2.5 use_node_name yes -- no debconf information
