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

[30 May 2008 17:43] Geert Vanderkelen
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
[11 Aug 2008 11:54] Kay Roepke
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
[11 Aug 2008 11:58] Kay Roepke
Not fixed in 1.3.x yet.
[25 Aug 2008 13:19] Carsten Segieth
tested OK in 2.0.0.7034
[8 Sep 2008 16:45] Tony Bedford
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.
[8 Jul 2009 16:57] Enterprise Tools JIRA Robot
Kay Roepke writes: 
this seems to have been resolved some time ago.
[9 Jul 2009 20:24] Enterprise Tools JIRA Robot
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.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.