Your message dated Sat, 12 Apr 2025 16:36:53 +0000
with message-id <[email protected]>
and subject line closing as unreproducible
has caused the Debian Bug report #1003862,
regarding munin-node fails to start on traditional sysvinit system
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.)
--
1003862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003862
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: munin-node
Version: 2.0.69-1~bpo11+1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
* What led up to the situation?
After upgrading from Stretch to Buster to Bullseye, munin-node (2.0.49-1)
refuses to start.
(Which was especially frustrating, as Debian fails to finish upgrading normally
then).
# /etc/init.d/munin-node start
Starting Munin-Node service: munin-nodestart-stop-daemon: timed out waiting for
a notification
failed!
In another window I can see the process started immideately, but init script
never realizes that:
root 23786 0.1 0.0 18768 15856 ? S 05:04 0:00 /usr/bin/perl
-wT /usr/sbin/munin-node --foreground
* What exactly did you do (or not do) that was effective (or
ineffective)?
- Trying version from bullseye-backports (munin-node 2.0.67-1~bpo10+1) also
fails to start.
- increasing the timeouts (#954128) doesn't help
- commenting out following two lines however makes munin node start (and stop)
normally:
START_ARGS="--background --notify-await --notify-timeout 15"
DAEMON_ARGS="--foreground"
* What was the outcome of this action?
I was expecting that munin-node would start normally, and control returned to
shell after issuing
"/etc/init.d/munin-node start"
* What outcome did you expect instead?
"/etc/init.d/munin-node start" fails with an error after trying for 15 seconds,
and munin-node does not start.
Note: I'm using sysvinit, not systemd.
-- System Information:
Debian Release: 11.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-10-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages munin-node depends on:
ii init-system-helpers 1.60
ii libnet-server-perl 2.009-2
ii lsb-base 11.1.0
ii munin-common 2.0.69-1~bpo11+1
ii munin-plugins-core 2.0.67-3
ii netbase 6.3
ii perl 5.32.1-4+deb11u2
Versions of packages munin-node recommends:
ii gawk 1:5.1.0-1
ii git 1:2.30.2-1
ii jo 1.3-2
ii jq 1.6-2.1
ii man-db [man] 2.9.4-2
ii munin-plugins-extra 2.0.67-3
ii perl-doc 5.32.1-4+deb11u2
ii procps 2:3.3.17-5
Versions of packages munin-node suggests:
ii munin 2.0.67-3
pn munin-plugins-java <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
control: tags -1 -wontfix
# gregor said he would be happy to provice help with munin sysv issues
# but this bug is unreproducible, thus closing it now
thanks
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄
wirklicher reichtum ist nicht privatjet fliegen, sondern sich vor dem schützen
können, was privatjet fliegen auslöst." <3 böhmermann am 3.2.23
signature.asc
Description: PGP signature
--- End Message ---
