Bug 10514 - Munin-node do not start because /var/run/munin/ does not exists
Summary: Munin-node do not start because /var/run/munin/ does not exists
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Guillaume Rousse
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2013-06-13 07:33 CEST by Olivier Thauvin
Modified: 2013-09-01 16:20 CEST (History)
1 user (show)

See Also:
Source RPM: munin-2.0.12-2.mga3.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Olivier Thauvin 2013-06-13 07:33:31 CEST 
Description of problem:

Munin-node store its PID into /var/run/munin/ but this directory does not exists when service is started.


Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-06-30 11:58:09 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => guillomovitch

Comment 1 David Walser 2013-08-11 01:05:26 CEST 
The package does have a correct tmpfiles configuration for systemd, but the source code itself has some hard-coded references to /var/run *.  However, if I understand correctly, /var/run is supposed to be a link to /run, so this should still work just fine.  Maybe patching the references in the source to just go to /run would help, but I don't think it should be necessary.

*
node/t/munin_node_config.t
dev_scripts/stop_munin-node
dev_scripts/start_munin-node

CC: (none) => mageia

Comment 2 David Walser 2013-08-13 23:30:47 CEST 
The only thing that's maybe fishy is that the munin tmpfiles thing is in the munin package instead of munin-node, but munin-node requires munin, so /run/munin should still be there.
Comment 3 Guillaume Rousse 2013-09-01 16:20:16 CEST 
The report is incorrect, munin-node is properly configured to use /run/munin to store its pid file. I suspect this is an upgrade issue, caused by an outaded configuration file.

Status: NEW => RESOLVED
Resolution: (none) => INVALID
Note You need to log in before you can comment on or make changes to this bug.