MySQL instance creation – Fails and Solutions

In this blog post, we are going to discuss how to solve issues which can happen during the MySQL instance creation. Below we are going to review  three different symptoms and causes of this issue and the ways how to solve them. So let’s start.

Symptom 1

Invalid username and password, the following error message is displayed while configuring the MySQL instance. MySQL commands fail with ‘GCC_4.2.0’ not found (required by /usr/lib64/libstdc++.so.6) error

Error Code 87:1
Invalid MySQL User Name and Password.

Cause 1

The instance creation fails if the libgcc_s.so.1 library included with the Commvault software is not compatible with the newer operating system version that it is installed on.

Solution 1

To solve this issue you need to rename /opt/commvault/Base/libgcc_s.so.1 using the following commands:

# cd /opt/commvault/Base
# mv /opt/commvault/Base/libgcc_s.so.1 /opt/Commvault/Base/libgcc_s.so.1.old
# commvault restart

Now you can create the instance again.

Symptom 2

MySQL instance creation fails when using older MySQL 5.5.x versions or earlier and displays the following error message.

Port wrong error

Cause 2

You get this error message and the instance creation fails because the Mysqladmin utility crashes as the -defaults- file does not have the required .ini or .cnf file extensions.

Solution 2

To solve this issue you need to upgrade the MySQL 5.5.x version to the latest available version.

Now you can create the instance again.

Symptom 3

Invalid username and password error is displayed while creating a new MySQL instance.

Error Code 87:1
Invalid MySQL User Name and Password.

MySqlBrowseAgent.log file on the client displays the following error:

Failed to execute mysql_real_connect

Cause 3

The instance creation fails if MySQL server is not alive.

Solution 3

To solve this issue follow the steps below:

Step 1. Check if MySQL Server is alive or not you can do it with the following command:

Windows

mysqladmin.exe --defaults-file=""--default-character-set=utf8 -u ping --port=<port_number> -p""

UNIX

/usr/bin/mysqladmin --defaults-file= --default-character-set=utf8 -u ping --socket="<socket_file>" -p"". If MySQL server is not alive, you will get the following outputs.

Step 2. If MySQL server is not alive, you will get the following outputs.

Windows

mysqladmin.exe: connect to server at 'localhost' failed
error: 'Can't connect to MySQL server on 'localhost' (10061)'
Check that mysqld is running on localhost and that the port is 3306.
You can check this by doing 'telnet localhost 3306'

UNIX

/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists!

Step 3. Start the MySQL Server, and then create the new MySQL instance.

Leave a Reply

Your email address will not be published.