Migrating MySQL database fails due to [#80031] JDBC get connection failed : Communications link failure"

book

Article ID: 100015235

calendar_today

Updated On:

Description

Error Message

Seen in the Server Log

Caused by: com.teneo.esa.common.database.PersistenceException: [#80031] JDBC get connection failed : Communications link failure

Cause

When setting up D.A. (with MySQL also being on the master node), the master's MySQL database must be migrated to itself (from localhost, to the FQDN of itself). After migration has completed, the MySQL service is then disabled automatically as expected. However, the master's MySQL service will need to stay on since it will be the MySQL database too. If MySQL service is off on the master, then the worker nodes will not be able to connect to migrate their database data.

Resolution

Open windows services, and re-enable the "MySQL" service on the master appliance

 

Applies To

This scenario may be seen in a distributed architecture (D.A.) environment that DOES NOT have a stand alone MySQL server (i.e, the master node and the MySQL server will be the same server).

Issue/Introduction

When migrating MySQL data from a worker node to a master appliance (that will be used as a shared MySQL database), an error in the command prompt says "[#80031] JDBC get connection failed :
Communications link failure".
Powered by Wolken Software