Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1003862: munin-node fails to start on traditional sysvinit system
148 views
Skip to first unread message
Matija Nalis
Jan 16, 2022, 11:30:03 PM1/16/22
to
Package: munin-node
Version: 2.0.69-1~bpo11+1
Severity: normal
X-Debbugs-Cc: mnalis-d...@voyager.hr
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
Version: 2.0.69-1~bpo11+1
Severity: normal
X-Debbugs-Cc: mnalis-d...@voyager.hr
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
Jérôme Bardot
Feb 24, 2023, 4:40:05 PM2/24/23
to
Hello, some news about that bug ?
I currently get the same error. (also without systemd)
Currently the post update conf fails on the post install script.
I currently get the same error. (also without systemd)
Currently the post update conf fails on the post install script.
Jérôme Bardot
May 5, 2023, 10:02:06 AM5/5/23
to
That bug is currently blocking from using munin on not systemd systems.
Holger Levsen
May 5, 2023, 10:30:05 AM5/5/23
to
control: tags -1 + wontfix
thanks
On Fri, May 05, 2023 at 03:49:44PM +0200, Jérôme Bardot wrote:
> That bug is currently blocking from using munin on not systemd systems.
I'm not planning on supporting legacy initscripts myself. And despite tagging
this bug 'wontfix' for the time being I will accept patches, so IOW I'm just
tagging this 'wontfix' to set expectations right.
In the long term I think munin's initscripts should be moved to
src:orphan-sysvinit-scripts and be maintained there by those who care.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄
"A developed country is not a place where the poor have cars. It's where the
rich use public transportation." (quote attributed to several people)
thanks
On Fri, May 05, 2023 at 03:49:44PM +0200, Jérôme Bardot wrote:
> That bug is currently blocking from using munin on not systemd systems.
this bug 'wontfix' for the time being I will accept patches, so IOW I'm just
tagging this 'wontfix' to set expectations right.
In the long term I think munin's initscripts should be moved to
src:orphan-sysvinit-scripts and be maintained there by those who care.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄
"A developed country is not a place where the poor have cars. It's where the
rich use public transportation." (quote attributed to several people)
Jérôme Bardot
May 5, 2023, 10:40:11 AM5/5/23
to
thx …
gregor herrmann
May 25, 2023, 12:00:06 PM5/25/23
to
Control: tag -1 + unreproducible
On Fri, 05 May 2023 14:16:53 +0000, Holger Levsen wrote:
> On Fri, May 05, 2023 at 03:49:44PM +0200, Jérôme Bardot wrote:
> > That bug is currently blocking from using munin on not systemd systems.
> I'm not planning on supporting legacy initscripts myself. And despite tagging
> this bug 'wontfix' for the time being I will accept patches, so IOW I'm just
> tagging this 'wontfix' to set expectations right.
In general I'm happy to help with the sysv initscript; in practice I
can only notice that I'm running munin-node (from testing or
unstable) on several machines with sysvinit, and that I haven't
encountered the issue. I just tried to restart and stop/start
munin-node on 3 machines, and it also just worked.
I guess we need more information from those who hit the issue …
Cheers,
gregor
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
On Fri, 05 May 2023 14:16:53 +0000, Holger Levsen wrote:
> On Fri, May 05, 2023 at 03:49:44PM +0200, Jérôme Bardot wrote:
> > That bug is currently blocking from using munin on not systemd systems.
> I'm not planning on supporting legacy initscripts myself. And despite tagging
> this bug 'wontfix' for the time being I will accept patches, so IOW I'm just
> tagging this 'wontfix' to set expectations right.
can only notice that I'm running munin-node (from testing or
unstable) on several machines with sysvinit, and that I haven't
encountered the issue. I just tried to restart and stop/start
munin-node on 3 machines, and it also just worked.
I guess we need more information from those who hit the issue …
Cheers,
gregor
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
0 new messages