Ошибка при установке mysql workbench

I looked around the several answer but none solved my problem.
First, I tried sudo apt install mysql-workbench -f.

It shows

The following packages have unmet dependencies:  mysql-workbench :
Depends: libgdal.so.1-1.11.3
                   Depends: libgdal1i (>= 1.8.0) but it is not going to be installed
                   Recommends: mysql-utilities but it is not going to be installed 
E: Unable to correct problems, you have held broken
packages.

If I tried to install libgdal1i, it will show

The following packages have unmet dependencies:  libgdal1i : Depends:
libarmadillo6 but it is not going to be installed
             Depends: libhdf5-10 but it is not going to be installed
             Depends: libnetcdf11 (>= 4.0.1) but it is not going to be installed 
E: Unable to correct problems, you have held broken packages.

There is no end of this story. I tried to install a dep but it always tell me another dep is lack and need to be installed.
Besides, I don’t know why it says E: Unable to correct problems, you have held broken. I checked in synaptic->custom filters->broken, nothing is there.

Also, I tried sudo aptitude install mysql-workbench -f since other posts said aptitude is better.

The following packages have unmet dependencies:  libgfortran3 :
Depends: gcc-5-base (= 5.3.1-14ubuntu2) but 5.4.0-6ubuntu1~16.04.1 is
installed.  mysql-connector-python : Conflicts: python-mysql.connector
but 2.0.4-1 is to be installed. The following actions will resolve
these dependencies:

      Keep the following packages at their current version: 
1)      libarmadillo6 [Not Installed]   
2)      libarpack2> [Not Installed]   
3)      libgdal1i [Not Installed]
4)      libgfortran3 [Not Installed] 
5)      libhdf5-10 [Not Installed]  
6)      liblapack3 [Not Installed]                        
7)      libnetcdf11 [Not Installed]
8)      mysql-connector-python [Not Installed]
9)      mysql-utilities [Not Installed]
10)     mysql-workbench [Not Installed]                    



Accept this solution? [Y/n/q/?]  No packages will be installed,
upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to
remove and 0 not to upgrade. Need to get 0 B of archives. After
unpacking 0 B will be used.

I accepted the solution by type enter, as you can see the issue is not solved.

In the last, I tried to download .deb from official site and install. No luck and the similar errors are prompted.

By inputting apt-cache policy mysql-workbench libgdal1i gcc-5-base libhdf5-10, it displays:

mysql-workbench:   
   Installed: (none)
   Candidate: 6.3.6+dfsg-0ubuntu1  Version table:
         6.3.6+dfsg-0ubuntu1 500
            500 http://au.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 

libgdal1i:   
   Installed: (none)
   Candidate:    1.11.3+dfsg-3build2
   Version table:
         1.11.3+dfsg-3build2 500
            500 http://au.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 

gcc-5-base:
   Installed: 5.4.0-6ubuntu1~16.04.1
   Candidate: 5.4.0-6ubuntu1~16.04.1
   Version table:
  *** 5.4.0-6ubuntu1~16.04.1 100
            100 /var/lib/dpkg/status
         5.3.1-14ubuntu2 500
            500 http://au.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 

libhdf5-10:
   Installed: (none)
   Candidate:  1.8.16+docs-4ubuntu1
   Version table:
         1.8.16+docs-4ubuntu1 500
            500 http://au.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

The result of apt-cache policy libgfortran3 libarmadillo6 libnetcdf11 python-mysql.connector is

libgfortran3:
Installed: 5.3.1-14ubuntu2
Candidate: 5.3.1-14ubuntu2
Version table:
*** 5.3.1-14ubuntu2 500
500 http://au.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
libarmadillo6:
Installed: 1:6.500.5+dfsg-1
Candidate: 1:6.500.5+dfsg-1
Version table:
*** 1:6.500.5+dfsg-1 500
500 http://au.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status
libnetcdf11:
Installed: 1:4.4.0-2
Candidate: 1:4.4.0-2
Version table:
*** 1:4.4.0-2 500
500 http://au.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status
python-mysql.connector:
Installed: 2.0.4-1
Candidate: 2.0.4-1
Version table:
*** 2.0.4-1 500
500 http://au.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
500 http://au.archive.ubuntu.com/ubuntu xenial/universe i386 Packages
100 /var/lib/dpkg/status

The result of grep -v ^# -r /etc/apt/sources.list etc/apt/sources.list.d/*.list is:

/etc/apt/sources.list:
/etc/apt/sources.list:deb http://au.archive.ubuntu.com/ubuntu/ xenial main restricted
/etc/apt/sources.list:
/etc/apt/sources.list:
/etc/apt/sources.list:deb http://au.archive.ubuntu.com/ubuntu/ xenial universe
/etc/apt/sources.list:
/etc/apt/sources.list:deb http://au.archive.ubuntu.com/ubuntu/ xenial multiverse
/etc/apt/sources.list:
/etc/apt/sources.list:
/etc/apt/sources.list:
/etc/apt/sources.list:deb http://apt.postgresql.org/pub/repos/apt/ xenial-pgdg main
/etc/apt/sources.list.d/google-chrome.list:deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
/etc/apt/sources.list.d/mysql.list:deb http://repo.mysql.com/apt/ubuntu/ xenial mysql-apt-config
/etc/apt/sources.list.d/mysql.list:deb http://repo.mysql.com/apt/ubuntu/ xenial mysql-5.7
/etc/apt/sources.list.d/mysql.list:deb http://repo.mysql.com/apt/ubuntu/ xenial mysql-tools
/etc/apt/sources.list.d/mysql.list:deb-src http://repo.mysql.com/apt/ubuntu/ xenial mysql-5.7
/etc/apt/sources.list.d/slack.list:deb https://packagecloud.io/slacktechnologies/slack/debian/ jessie main
/etc/apt/sources.list.d/sublime-text.list:deb https://download.sublimetext.com/ apt/stable/

MySQL Workbench allows connecting to remote server databases from your personal computer.

However, MySQL workbench failed to connect errors happen due to MySQL version compatibility or set up problems.

One such error is,

Failed to Connect to MySQL at 7129bXXX43dc.XXXX.com:3306 through SSH tunnel at wheelxx@xxx.x.xxx.xx:2414 with user username

At Bobcares, we often get requests from our customers to set up MySQL workbench as part of our Server Management Services.

Today, we’ll see the top reasons that result in MySQL failed connection and how our Support Engineers fix them.

How to Connect to a Cloud Database via MySQL Workbench

MySQL workbench is s free, visual tool for database architects, developers, and DBAs. Also, it provides a platform for database management like development, administration, database design, creation, etc. The maintenance of a database becomes easy with this unique tool.

Well, MySQL Workbench is available on Windows, Linux and Mac OS X. And, that’s yet another reason for its popularity.

Here, let’s see how our Support Engineers connect to Cloud Databases via MySQL Workbench.

1. Initially, we go to http://www.mysql.com/products/workbench/ and install MySQL WorkBench.

2. Then, we launch MySQL Workbench, select Server Administration >> New Server Instance option.

3. We select the Remote Host option and enter the URL you received when you created the database instance. Again, we click Continue.

4. Next, we go to Connection Method menu >> select Standard TCP/IP over SSH.

5. Also, we change the value for SSH hostname to name or IP address of a Cloud Server that we have created.

6. Then, we enter the following value as

1. SSH Username:- cloud server user name
2. MySQL Hostname:-  hostname received while creating the database instance via the API.
3. Username:- enter the username received when you created the database instance.

7. After that, we click Continue.

8. Finally, we enter the database instance password.

That’s it, we’ll get the Server Administration screen.

Common problems after setting up MySQL Workbench

From our experience in managing servers, we’ve seen customers facing different kinds of problems after installing MySQL Workbench.

Let’s see how our Support Team solved these common errors.

Missing SSL certificate

Recently, one of our customers contacted us with a problem related to MySQL Workbench. Also, both the SSH connection to the server and from the server to the cloud database worked. But when tried connecting from MySQL Workbench, it didn’t work. He received an error from Workbench. The error said,

Failed to Connect to MySQL at 7129b041xxxx476e8d37651071b12a6681b732.rackspaceclouddb.com:3306 through SSH tunnel at xxx.x.xxx.xx:2414 with user username connection error: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown.

On checking, our Support Engineers found that the problem was related to the SSL of the Cloud instance. In order to solve the problem, the options were to either configure MySQL workbench to connect without SSL OR configure SSL for the cloud instance.

However, configuring MySQL workbench without SSL can be a security risk. So, we set up SSL with the Cloud Database instance and solved the problem.

Incompatible MySQL version

Similarly, another customer had an error when tried to setup workbench for cloud hosting platforms like Appian. He got an error "failed to connect to MySQL at localhost 3306 with user root".

While checking, our Support Engineers found that the installed version of MySql was MySql 8.X which is not compatible with workbench. Therefore, we installed the Version 5.7.X version and it sorted out the problem.

[Never worry about MySQL workbench failed to connect errors anymore! We are here to fix it for you.]

Conclusion

In short, errors like MySQL workbench failed to connect may happen due to MySQL version compatibility or because of missing SSL certificate. Today, we saw how our Support Engineers set up MySQL workbench and fix related errors.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;