Getting "Using the default of SSL_verify_mode of SSL_VERIFY_NONE" message when running innobackupex on CentOS 7
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB | Status tracked in 2.4 | |||||
2.3 |
Triaged
|
Low
|
Unassigned | |||
2.4 |
Triaged
|
Low
|
Unassigned |
Bug Description
Getting "Using the default of SSL_verify_mode of SSL_VERIFY_NONE" message when running innobackupex on CentOS 7
[root@centos7 ~]# innobackupex --user=root /tmp/
160316 10:05:30 innobackupex: Starting the backup operation
IMPORTANT: Please check that the backup run completes successfully.
At the end of a successful backup run innobackupex
prints "completed OK!".
160316 10:05:30 version_check Connecting to MySQL server with DSN 'dbi:mysql:
160316 10:05:31 version_check Connected to MySQL server
160316 10:05:31 version_check Executing a version check against the server...
*******
Using the default of SSL_verify_mode of SSL_VERIFY_NONE for client
is deprecated! Please set SSL_verify_mode to SSL_VERIFY_PEER
together with SSL_ca_
If you really don't want to verify the certificate and keep the
connection open to Man-In-The-Middle attacks please set
SSL_verify_mode explicitly to SSL_VERIFY_NONE in your application.
*******
at - line 237.
*******
Using the default of SSL_verify_mode of SSL_VERIFY_NONE for client
is deprecated! Please set SSL_verify_mode to SSL_VERIFY_PEER
together with SSL_ca_
If you really don't want to verify the certificate and keep the
connection open to Man-In-The-Middle attacks please set
SSL_verify_mode explicitly to SSL_VERIFY_NONE in your application.
*******
at - line 237.
160316 10:05:32 version_check Done.
160316 10:05:32 Connecting to MySQL server host: localhost, user: root, password: not set, port: 0, socket: /var/lib/
Using server version 5.6.29-76.2
innobackupex version 2.3.4 based on MySQL server 5.6.24 Linux (x86_64) (revision id: e80c779)
...
[root@centos7 ~]# innobackupex --version
innobackupex version 2.3.4 Linux (x86_64) (revision id: e80c779)
[root@centos7 ~]# xtrabackup --version
xtrabackup version 2.3.4 based on MySQL server 5.6.24 Linux (x86_64) (revision id: e80c779)
looks like it is fixed in 2.4.5 , at least I don't have this error...