MySQL Bugs: #37108: Wrong value for log-level put init.d script in end-less loop

Bug #37108	Wrong value for log-level put init.d script in end-less loop
Submitted:	30 May 2008 17:43	Modified:	9 Jul 2009 20:24
Reporter:	Geert Vanderkelen	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Agent	Severity:	S3 (Non-critical)
Version:	1.3.1,0.7.0.xxx	OS:	Linux
Assigned to:	Kay Roepke	CPU Architecture:	Any

Description:
I made a typo in the word 'debug' (yes yes, I know..) and init.d script didn't fail, but dotted endlessly, like it was in an endless loop.

How to repeat:
In the configuration file of the service agent:

[agent]
log-level = debugg

This was the same issue as Bug#38607

The init script will now show a startup failure and the log file contains the lines:
2008-08-11 13:51:55: (critical) --log-level=... failed, level 'debugg' is unknown 
2008-08-11 13:51:55: (message) shutting down normally

Not fixed in 1.3.x yet.

tested OK in 2.0.0.7034

Have not closed as there appears to be a question mark over status for 1.3.

Added an entry to the 2.0 changelog:

If the log-level option in the agent configuration file was set to an unknown level by mistake, the init.d script appeared to enter an infinite loop.

Kay Roepke writes: 
this seems to have been resolved some time ago.

Carsten Segieth writes: 
closed, as it's fixed in 2.0 and (just verified) 2.1.0.1074, and there will be no more 1.3 version.