Ubuntu
munin package

/etc/init.d/munin-node not systemd compliant

Bug #1270193 reported by Robert Sander
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
munin (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

The script in /etc/init.d/munin-node is not systemd compliant, but the package installs a systemd service:

Setting up munin-node (2.0.17-2ubuntu1) ...
Warning: The home dir /var/lib/munin you specified can't be accessed: No such file or directory
Adding system user `munin' (UID 138) ...
Adding new group `munin' (GID 149) ...
Adding new user `munin' (UID 138) with group `munin' ...
Not creating home directory `/var/lib/munin'.
Initializing plugins..done.
Restarting munin-node..munin-node start/running, process 19825
ln -s '/lib/systemd/system/munin-node.service' '/etc/systemd/system/multi-user.target.wants/munin-node.service'

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: munin-node 2.0.17-2ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-15.8-lowlatency 3.11.10
Uname: Linux 3.11.0-15-lowlatency x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Fri Jan 17 16:38:54 2014
InstallationDate: Installed on 2012-06-14 (581 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: munin
UpgradeStatus: Upgraded to saucy on 2013-10-29 (80 days ago)
modified.conffile..etc.munin.plugin.conf.d.munin.node: [deleted]

Revision history for this message
Robert Sander (gurubert) wrote :
tags: added: systemd
Revision history for this message
Robie Basak (racb) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

So that I can gauge this bug's importance, could you please explain the impact this has on users, and specific failure use cases? Once done, please change the bug status back to New. Thanks!

Changed in munin (Ubuntu):
status: New → Incomplete
Revision history for this message
Robert Sander (gurubert) wrote :

The impact is that it is impossible to stop munin-node with

sudo /etc/init.d/munin-node stop

because systemd will automatically restart it.

Revision history for this message
Robie Basak (racb) wrote :

What proportion of Ubuntu users are running in an affected configuration, please? I thought systemd wasn't used in Ubuntu by default?

Revision history for this message
Robert Sander (gurubert) wrote :

The xfce4-power-manager depends on systemd-services.

Revision history for this message
Robie Basak (racb) wrote :

> The xfce4-power-manager depends on systemd-services.

Please help me out here. I am trying to triage this bug, but you aren't answering my question. What proportion of Ubuntu users are likely to be running in an affected configuration?

Is this limited to users who want to use munin (seeded in ubuntu-server only) and who also use Xubuntu, Lubuntu or Ubuntu Studio (since xfce4-power-manager is seeded in lubuntu, ubuntustudio and xubuntu only)?

I'm going to assume that the intersection of these two sets of users is small, and thus this is an Importance: Low bug as described by https://wiki.ubuntu.com/Bugs/Importance.

Patches welcome. Since munin no longer carries a delta in Ubuntu, it is probably worth you communicating with Debian over any fixes.

Changed in munin (Ubuntu):
status: Incomplete → New
importance: Undecided → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in munin (Ubuntu):
status: New → Confirmed
Revision history for this message
Markus Wörle (mrks) wrote :

I'm also affected by this issue I think. I don't know for now whether it has something to do with systemd or startup, but if the munin-node service gets started with "start munin-node", it can't be stopped with "/etc/init.d/munin-node stop" although it went "[OK]". Also "/etc/init.d/munin-node restart" won't work anymore, it the service has been brought up via "start munin-node".

The same effect occurs vice versa: if you start the node with "/etc/init.d/munin-node start", you can't control it by upstart controls.

Revision history for this message
Robie Basak (racb) wrote :

@Markus

I think you're talking about a different issue. Mixing calling SysV init scripts directly with calling other init systems directly generally isn't a good idea, but the system shouldn't let you shoot yourself in the foot like this. Bug 1273462 covers this.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.