** Changed in: munin (Ubuntu)
Status: Fix Committed = Fix Released
--
munin-node is no longer being started during boot
https://bugs.launchpad.net/bugs/538902
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in ubuntu.
--
Good call. I'll upload your fix once beta freeze is over.
** Changed in: munin (Ubuntu)
Status: Triaged = In Progress
** Changed in: munin (Ubuntu)
Assignee: (unassigned) = Mathias Gug (mathiaz)
--
munin-node is no longer being started during boot
The fixed has already been queued.
Regards
chuck
--
munin-node is no longer being started during boot
https://bugs.launchpad.net/bugs/538902
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in ubuntu.
--
Ubuntu-server-bugs mailing
Waiting in the queue, yes.
Thanks, although a mentioning in the changelog would have been nice.
Chuck, can you look into bug 538594 - the debdiff won't apply anymore,
but it's rather trivial.
** Changed in: munin (Ubuntu)
Status: In Progress = Fix Committed
** Changed in: munin (Ubuntu)
On Monday, March 15, 2010 at 22:22:05 (-), Daniel Hahler wrote:
Great. So, do you have any problems during boot? - or does it all work
fine, except filesystems does not get emitted for you?
In the docked system configuration I have no problems during boot. All
filesystems I have configured
The problem is that it should start on filesystem (which is what mountall
emits), not filesystems.
Fix/Patch ahead.
** Changed in: munin (Ubuntu)
Status: Incomplete = Triaged
** Branch linked: lp:~blueyed/munin/bug-538902
--
munin-node is no longer being started during boot
Can you add your /var/log/daemon.log please?
Thanks
chuck
** Changed in: munin (Ubuntu)
Importance: Undecided = Medium
** Changed in: munin (Ubuntu)
Status: New = Incomplete
--
munin-node is no longer being started during boot
https://bugs.launchpad.net/bugs/538902
You received this
It's not being started for me either, but that's because of a problem
with mountall/cryptsetup/plymouth probably.
It gets started for me after I manually emit the filesystems event:
sudo initctl emit filesystems - please check if that's the case for
you, too.
--
munin-node is no longer being
On Monday, March 15, 2010 at 19:40:34 (-), Daniel Hahler wrote:
It's not being started for me either, but that's because of a problem
with mountall/cryptsetup/plymouth probably.
It gets started for me after I manually emit the filesystems event:
sudo initctl emit filesystems - please
Great. So, do you have any problems during boot? - or does it all work
fine, except filesystems does not get emitted for you?
--
munin-node is no longer being started during boot
https://bugs.launchpad.net/bugs/538902
You received this bug notification because you are a member of Ubuntu
Server
** Attachment added: proc_ps.log
http://launchpadlibrarian.net/40939838/proc_ps.log
--
munin-node is no longer being started during boot
https://bugs.launchpad.net/bugs/538902
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in
11 matches
Mail list logo
