On Fri, May 02, 2008 at 02:02:32PM +0200, Petter Reinholdtsen wrote:
Well, I find it important that a bogus configuration file can block
the boot completely and make the machine fail to come up as it should.
Not sure if 'wishlist' is the correct severity for such problem. :)
I marked the bug
Hi Petter,
I guess it need to be fixed there. On the other hand I would
recommend munin-node dying with an error instead of blocking the boot
when it encounter a bogus configuration file. It would have avoided
this problem.
So if I understand this bug correctly, it can be downgraded to a
[Thijs Kinkhorst]
So if I understand this bug correctly, it can be downgraded to a
wishlist please error on bogus configuration file?
Well, I find it important that a bogus configuration file can block
the boot completely and make the machine fail to come up as it should.
Not sure if 'wishlist'
On Mon, 14 Apr 2008 23:28:21 +0200, Petter Reinholdtsen [EMAIL PROTECTED]
said:
[Matthias Schmitz]
Would you please provide this file or check if it is valid? If i
touch an empty file and use it as config i got the same result:
Sure. This is the content when all the comments are removed:
Hi Petter, hi *,
Am Mon, 14 Apr 2008 23:28:21 +0200
schrieb Petter Reinholdtsen [EMAIL PROTECTED]:
[Matthias Schmitz]
Would you please provide this file or check if it is valid? If i
touch an empty file and use it as config i got the same result:
Sure. This is the content when all the
[Matthias Schmitz]
please add the following statements:
port 4949
setsid yes
(And maybe also:
user root
group root )
I'll try to get it added.
When did this change? The configuration worked in Etch. It would be
best for existing installations if it continued to work also in Lenny.
Can
Hi Petter, hi *,
Am Tue, 15 Apr 2008 08:52:37 +0200
schrieb Petter Reinholdtsen [EMAIL PROTECTED]:
[Matthias Schmitz]
please add the following statements:
port 4949
setsid yes
(And maybe also:
user root
group root )
I'll try to get it added.
When did this change? The
[Matthias Schmitz]
i take a look into the sources of 'debian-edu-config' and it looks
like you give the munin.conf to the munin-node. Which is not
intendend :-). Are you sure that this ever worked?
Nope. I am getting quite sure that the change done in svn 2008-04-04
never worked. The
Hi Petter, hi *,
Am Mon, 14 Apr 2008 09:55:24 +0200
schrieb Petter Reinholdtsen [EMAIL PROTECTED]:
[Stig Sandbeck Mathisen]
Thanks for the report. We'll find a fix for this.
Thank you. Please include a fix for #440003 too in the next upload, as
i'am currently working at the debian package
Hi Petter, hi *,
Am Sat, 12 Apr 2008 12:56:29 +0200
schrieb Petter Reinholdtsen [EMAIL PROTECTED]:
After installation, munin-node fail to put the daemon in the
background, and blocks the boot. This the output from
'bash -x /etc/init.d/munin-node start'. I marked the point where I
had to
[Matthias Schmitz]
Would you please provide this file or check if it is valid? If i
touch an empty file and use it as config i got the same result:
Sure. This is the content when all the comments are removed:
dbdir /var/lib/munin
htmldir /var/www/munin
logdir
On Sat, 12 Apr 2008 12:56:29 +0200, Petter Reinholdtsen [EMAIL PROTECTED]
said:
Setting severity to grave, as this break the boot for Debian Edu
where munin-node is installed automatically.
Thanks for the report. We'll find a fix for this.
--
Stig Sandbeck Mathisen, Linpro
--
To
[Stig Sandbeck Mathisen]
Thanks for the report. We'll find a fix for this.
Thank you. Please include a fix for #440003 too in the next upload, as
that bug made us in Debian Edu have to fork the package for Etch.
Happy hacking,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to [EMAIL
Package: munin-node
Version: 1.2.5-2
Severity: grave
After installation, munin-node fail to put the daemon in the
background, and blocks the boot. This the output from
'bash -x /etc/init.d/munin-node start'. I marked the point where I
had to use ^C to kill the script with XXX.
Setting
14 matches
Mail list logo
