Error running example vttablet-up.sh

[Wiby]

Hello!

I'm going through the "Start a Vitess Cluster" example and have been stuck on step 5 - Start vttablets. After running vttablet-up.sh, it hangs for a few minutes before giving the following error:

./vttablet-up.sh
enter zk2 env
Starting MySQL for tablet test-0000000100...
Starting MySQL for tablet test-0000000101...
Starting MySQL for tablet test-0000000102...
E0324 22:58:47.005097    3072 mysqld.go:518] failed starting mysqld in time (check mysyql error log /home/wiby/vtdataroot/vt_0000000101/error.log for more info): deadline exceeded waiting for mysqld socket file to appear: /home/wiby/vtdataroot/vt_0000000101/mysql.sock
E0324 22:58:47.009801    3072 mysqlctl.go:254] failed init mysql: deadline exceeded waiting for mysqld socket file to appear: /home/wiby/vtdataroot/vt_0000000101/mysql.sock
E0324 22:58:47.175480    3073 mysqld.go:518] failed starting mysqld in time (check mysyql error log /home/wiby/vtdataroot/vt_0000000102/error.log for more info): deadline exceeded waiting for mysqld socket file to appear: /home/wiby/vtdataroot/vt_0000000102/mysql.sock
E0324 22:58:47.175822    3073 mysqlctl.go:254] failed init mysql: deadline exceeded waiting for mysqld socket file to appear: /home/wiby/vtdataroot/vt_0000000102/mysql.sock
E0324 22:58:47.489137    3071 mysqld.go:518] failed starting mysqld in time (check mysyql error log /home/wiby/vtdataroot/vt_0000000100/error.log for more info): deadline exceeded waiting for mysqld socket file to appear: /home/wiby/vtdataroot/vt_0000000100/mysql.sock
E0324 22:58:47.489410    3071 mysqlctl.go:254] failed init mysql: deadline exceeded waiting for mysqld socket file to appear: /home/wiby/vtdataroot/vt_0000000100/mysql.sock
Starting vttablet for test-0000000100...
Access tablet test-0000000100 at http://ubuntu:15100/debug/status
Starting vttablet for test-0000000101...
Access tablet test-0000000101 at http://ubuntu:15101/debug/status
Starting vttablet for test-0000000102...
Access tablet test-0000000102 at http://ubuntu:15102/debug/status

Inside error.log for one of the 3 tablets:

2019-03-25T04:46:17.723279Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2019-03-25T04:46:17.732637Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2019-03-25T04:46:17.734206Z 0 [Warning] [MY-010915] [Server] '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.
2019-03-25T04:46:17.744662Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.0.15) initializing of server in progress as process 2080
2019-03-25T04:46:17.752231Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2019-03-25T04:46:17.752236Z 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8_general_ci' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
2019-03-25T04:46:17.770983Z 0 [Warning] [MY-000081] [Server] option 'innodb-log-file-size': unsigned value 1048576 adjusted to 4194304.
2019-03-25T04:46:25.038480Z 5 [Warning] [MY-010453] [Server] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
2019-03-25T04:46:29.632406Z 0 [System] [MY-013170] [Server] /usr/sbin/mysqld (mysqld 8.0.15) initializing of server has completed
2019-03-25T04:46:31.760191Z mysqld_safe Logging to '/home/wiby/vtdataroot/vt_0000000100/error.log'.
2019-03-25T04:46:31.771633Z mysqld_safe Starting mysqld daemon with databases from /home/wiby/vtdataroot/vt_0000000100/data
2019-03-25T04:46:32.044754Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2019-03-25T04:46:32.044812Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2019-03-25T04:46:32.044873Z 0 [Warning] [MY-010915] [Server] '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.
2019-03-25T04:46:32.046909Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.15) starting as process 3708
2019-03-25T04:46:32.048479Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2019-03-25T04:46:32.048491Z 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8_general_ci' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
2019-03-25T04:46:32.052703Z 0 [Warning] [MY-000081] [Server] option 'innodb-log-file-size': unsigned value 1048576 adjusted to 4194304.
2019-03-25T04:46:32.580014Z 1 [Warning] [MY-010005] [Server] Skip re-populating collations and character sets tables in read-only mode.
2019-03-25T04:46:32.768360Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2019-03-25T04:46:32.796765Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.15'  socket: '/home/wiby/vtdataroot/vt_0000000100/mysql.sock'  port: 17100  MySQL Community Server - GPL.
2019-03-25T04:46:32.836436Z 0 [ERROR] [MY-011300] [Server] Plugin mysqlx reported: 'Setup of socket: '/var/run/mysqld/mysqlx.sock' failed, can't create lock file /var/run/mysqld/mysqlx.sock.lock'
2019-03-25T04:46:32.836465Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060

I will also see on the other two tablets this error: 'Setup of bind-address: '*' port: 33060 failed, `bind()` failed with error: Address already in use (98). Do you already have another mysqld server running with Mysqlx ?'

I have apparmor uninstalled, this is on ubuntu 16.04 with MySQL 8. Any advice on where else to look would be greatly appreciated.

Thanks.

[Sugu Sougoumarane]

Looks like mysql isn't coming up properly. Can you try to bring up independently? First, manually, and then using mysqlctl.

--
You received this message because you are subscribed to the Google Groups "vitess" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vitess+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Wiby]

I haven't narrowed it down yet but got further. On Sunday I was doing this in a VM. Today I setup two identical real machines, the only difference between them is one has mysql 5.7 and one has mysql 8. Step 5 (Start vttablets) is working with the machine that has mysql 5.7. So could it be something specific to mysql 8? (it has the legacy authentication mode enabled). "git clone https://github.com/vitessio/vitess.git \" is the version I downloaded. I will try again tomorrow from scratch... Maybe I missed something else.

[Sugu Sougoumarane]

There could be something specific to 8.0. Will you be able to get on slack and ask @derekperkins or @koz? They may be able to help you.

[Wiby]

Ok thanks, I'll see if I can reach them on there when I get a chance. And just as an update, I built Vitess again on another VM and can confirm no trouble getting step 5 to work with mysql 5.7, just not on 8.

To unsubscribe from this group and stop receiving emails from it, send an email to vit...@googlegroups.com.

[Derek Perkins]

These are the only additions you should need for my.cnf

default_authentication_plugin   = mysql_native_password

secure_file_priv                = NULL

That specific error looks like you're trying to run multiple instances of MySQL on a single VM without changing the port for the X protocol. I think the only difference there is that it is enabled by default in 8.0. That error isn't related to Vitess.

Derek

[Wiby]

default_authentication_plugin   = mysql_native_password

secure_file_priv                = NULL

Thank you Derek this worked :)