The
vttablet-up.sh script failed to start mysqlI have done the following steps:
1. install GO
2. install Percona 5.7
rpm -qa | grep Percona
Percona-Server-server-57-5.7.21-20.1.el7.x86_64
Percona-Server-shared-compat-57-5.7.21-20.1.el7.x86_64
Percona-Server-client-57-5.7.21-20.1.el7.x86_64
Percona-Server-devel-57-5.7.21-20.1.el7.x86_64
Percona-Server-shared-57-5.7.21-20.1.el7.x86_64
mysqld --version
mysqld Ver 5.7.21-20 for Linux on x86_64 (Percona Server (GPL), Release 20, Revision ed217b06ca3)
service mysqld status
Redirecting to /bin/systemctl status mysqld.service
● mysqld.service - MySQL Server
Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
Active: inactive (dead)...
ls -l /bin/mysql
-rwxr-xr-x. 1 root root 3905088 Feb 16 10:12 /bin/mysql
3. install jdk
4. define all variables:
env | grep -i vt
VTDATAROOT=/vtdataroot
VTTOP=/opt/vitess/src/vitess.io/vitess
VT_TEST_FLAGS=--topo-server-flavor=consul
VTROOT=/opt/vitess
VT_MYSQL_ROOT=/
VTPORTSTART=15000
PYTHONPATH=/opt/vitess/py-vtdb:/opt/vitess/dist/selenium/lib/python2.7/site-packages:/opt/vitess/dist/py-mock-1.0.1/lib/python2.7/site-packages:/opt/vitess/dist/grpc/usr/local/lib/python2.7/site-packages:
[root@vitess703 bin]# env | grep -i mysql
MYSQL_FLAVOR=MySQL56
VT_MYSQL_ROOT=/
5. built vitess
6. started ZK
root 30451 1 0 10:40 ? 00:00:00 /bin/bash /opt/vitess/bin/zksrv.sh /vtdataroot/zk_001/logs /vtdataroot/zk_001/zoo.cfg /vtdataroot/zk_001/zk.pid
root 30455 30451 0 10:40 ? 00:00:04 /usr/bin/java -server -DZOO_LOG_DIR=/vtdataroot/zk_001/logs -cp /opt/vitess/dist/vt-zookeeper-3.4.10/lib/zookeeper-3.4.10-fatjar.jar:/usr/local/lib/zookeeper-3.4.10-fatjar.jar:/usr/share/jav
a/zookeeper-3.4.10.jar org.apache.zookeeper.server.quorum.QuorumPeerMain /vtdataroot/zk_001/zoo.cfg
7. starting vtctld
cat $VTDATAROOT/tmp/vtctld.out
F0313 11:44:59.831021 8359 servenv.go:87] servenv.Init: running this as root makes no sense
the vtctld is not running, what could be the problem?
1. what am I missing in the mysql configuration?
./vttablet-up.sh
Starting mysqld for all shards
Starting mysqld for shard -80 ...
Running mysqld-up-instance-100.sh
Starting MySQL for tablet cell1-0000000100...
W0313 10:46:18.241393 6049 mysqld.go:231] mysqld_safe not found in any of //{sbin,bin}: trying to launch mysqld instead
E0313 10:51:12.678403 6049 mysqld.go:532] failed starting mysqld in time (check mysyql error log /vtdataroot/vt_0000000100/error.log for more info): deadline exceeded waiting for mysqld socket file to appear: /vtdataroot/vt_0000000100/
mysql.sock
E0313 10:51:12.679289 6049 mysqlctl.go:260] failed init mysql: deadline exceeded waiting for mysqld socket file to appear: /vtdataroot/vt_0000000100/mysql.sock
cd /vtdataroot/vt_0000000101
cat error.log
2018-03-13T10:51:14.388860Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-03-13T10:51:14.388926Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2018-03-13T10:51:14.388930Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2018-03-13T10:51:14.388991Z 0 [ERROR] Can't find error-message file '/share/percona-server/errmsg.sys'. Check error-message file location and 'lc-messages-dir' configuration directive.
2018-03-13T10:51:14.395652Z 0 [Warning] InnoDB: Using innodb_support_xa is deprecated and the parameter may be removed in future releases. Only innodb_support_xa=ON is allowed.
2018-03-13T10:51:15.568170Z 0 [Warning] InnoDB: New log files created, LSN=45790
2018-03-13T10:51:16.278937Z 0 [Warning] InnoDB: Creating foreign key constraint system tables.
2018-03-13T10:51:16.390264Z 0 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 746675e2-26ac-11e8-91a3-42010a800022.
2018-03-13T10:51:16.392188Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2018-03-13T10:51:16.701119Z 0 [Warning] CA certificate ca.pem is self signed.
2018-03-13T10:51:16.901375Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
2018-03-13T10:51:17.603072Z 1 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
2018-03-13T10:51:17.603096Z 1 [Warning] 'user' entry 'mysql.session@localhost' ignored in --skip-name-resolve mode.
2018-03-13T10:51:17.603103Z 1 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.
2018-03-13T10:51:17.603113Z 1 [Warning] 'db' entry 'performance_schema mysql.session@localhost' ignored in --skip-name-resolve mode.
2018-03-13T10:51:17.603116Z 1 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
2018-03-13T10:51:17.603123Z 1 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
2018-03-13T10:51:17.603157Z 1 [Warning] 'tables_priv' entry 'user mysql.session@localhost' ignored in --skip-name-resolve mode.
2018-03-13T10:51:17.603163Z 1 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
2. each tablet will create mysql instance on different port? or tablets will reside on same mysql instance?