Bug #57574 mysqlmonitorctl script changes for installations not using bundled repository

Submitted:	19 Oct 2010 15:53
Reporter:	Roger David Nay	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Enterprise Monitor: Server	Severity:	S3 (Non-critical)
Version:	2.2.0.1709	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
When not using the bundled repository (using a local mysql installation instead). The mysqlmonitorctl.sh script for tomcat/mysql does not give any feedback that you are not using the bundled repository. It doesn't start/stop the local mysql installation obviously, but doesn't give any indication that you cannot use the script to stop it.

The 'status' option on the other hand, gives 'Not running' which can be confusing.

The manual doesn't have any mention of the kind of response you get if you are not using the bundled repository either.

'restart' is probably the same.

How to repeat:
Use the stop/start/status/restart of the mysql process when you are running with a local version of mysql for the repository (not the bundled one).

Suggested fix:
If you are not using the bundled version then there should be different messages output from the mysqlmonitorctl.sh script alerting you to the fact that you are not using the bundled repository.

Add some messages if you are not using the bundled version to the script and to the manual to explain them.

Page generated in 0.039 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.