Page MenuHomePhabricator
Paste P11254

(An Untitled Masterwork)
ActivePublic

Authored by Kormat on Wed, May 20, 1:18 PM.
May 20 12:57:48 db2137 mysqld[26094]: 2020-05-20 12:57:48 0 [Note] /opt/wmf-mariadb104/bin/mysqld (mysqld 10.4.13-MariaDB-log) starting as process 26094 ...
May 20 12:57:48 db2137 mysqld[26094]: 2020-05-20 12:57:48 0 [Warning] No argument was provided to --log-bin and neither --log-basename or --log-bin-index where used; This may cause repliction to break when this
May 20 12:57:48 db2137 mysqld[26094]: 2020-05-20 12:57:48 0 [ERROR] mysqld: Plugin 'unix_socket' already installed
May 20 12:57:48 db2137 mysqld[26094]: 2020-05-20 12:57:48 0 [ERROR] Couldn't load plugin 'unix_socket' from 'auth_socket.so'.
May 20 12:57:48 db2137 mysqld[26094]: 2020-05-20 12:57:48 0 [Warning] The parameter innodb_file_format is deprecated and has no effect. It may be removed in future releases. See https://mariadb.com/kb/en/library
May 20 12:57:48 db2137 mysqld[26094]: 2020-05-20 12:57:48 0 [Warning] InnoDB: Using innodb_locks_unsafe_for_binlog is DEPRECATED. This option may be removed in future releases. Please use READ COMMITTED transact
May 20 12:57:48 db2137 mysqld[26094]: 2020-05-20 12:57:48 0 [Note] InnoDB: Using Linux native AIO
May 20 12:57:48 db2137 mysqld[26094]: 2020-05-20 12:57:48 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
May 20 12:57:48 db2137 mysqld[26094]: 2020-05-20 12:57:48 0 [Note] InnoDB: Uses event mutexes
May 20 12:57:48 db2137 mysqld[26094]: 2020-05-20 12:57:48 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
May 20 12:57:48 db2137 mysqld[26094]: 2020-05-20 12:57:48 0 [Note] InnoDB: Number of pools: 1
May 20 12:57:48 db2137 mysqld[26094]: 2020-05-20 12:57:48 0 [Note] InnoDB: Using SSE2 crc32 instructions
May 20 12:57:48 db2137 mysqld[26094]: 2020-05-20 12:57:48 0 [Note] mysqld: O_TMPFILE is not supported on /srv/tmp.s4 (disabling future attempts)
May 20 12:57:48 db2137 mysqld[26094]: 2020-05-20 12:57:48 0 [Note] InnoDB: Initializing buffer pool, total size = 185G, instances = 8, chunk size = 128M
May 20 12:57:52 db2137 mysqld[26094]: 2020-05-20 12:57:52 0 [Note] InnoDB: Completed initialization of buffer pool
May 20 12:57:52 db2137 mysqld[26094]: 2020-05-20 12:57:52 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
May 20 12:57:53 db2137 mysqld[26094]: 2020-05-20 12:57:53 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
May 20 12:57:53 db2137 mysqld[26094]: 2020-05-20 12:57:53 0 [Note] InnoDB: Creating shared tablespace for temporary tables
May 20 12:57:53 db2137 mysqld[26094]: 2020-05-20 12:57:53 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
May 20 12:57:53 db2137 mysqld[26094]: 2020-05-20 12:57:53 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
May 20 12:57:53 db2137 mysqld[26094]: 2020-05-20 12:57:53 0 [Note] InnoDB: Waiting for purge to start
May 20 12:57:53 db2137 mysqld[26094]: 2020-05-20 12:57:53 0 [Note] InnoDB: 10.4.13 started; log sequence number 47048; transaction id 9
May 20 12:57:53 db2137 mysqld[26094]: 2020-05-20 12:57:53 0 [Note] InnoDB: Loading buffer pool(s) from /srv/sqldata.s4/ib_buffer_pool
May 20 12:57:53 db2137 mysqld[26094]: 2020-05-20 12:57:53 0 [Note] InnoDB: Buffer pool(s) load completed at 200520 12:57:53
May 20 12:57:53 db2137 mysqld[26094]: 2020-05-20 12:57:53 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
May 20 12:57:53 db2137 mysqld[26094]: 2020-05-20 12:57:53 6 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1017: Can't find file: './mysql/' (errno: 2 "No such file or director
May 20 12:57:53 db2137 mysqld[26094]: 2020-05-20 12:57:53 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
May 20 12:57:53 db2137 mysqld[26094]: 2020-05-20 12:57:53 0 [Note] Server socket created on IP: '::'.
May 20 12:57:53 db2137 mysqld[26094]: 2020-05-20 12:57:53 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.db' doesn't exist
May 20 12:57:53 db2137 mysqld[26094]: 2020-05-20 12:57:53 0 [ERROR] Aborting
May 20 12:57:59 db2137 systemd[1]: mariadb@s4.service: Main process exited, code=exited, status=1/FAILURE

Event Timeline

Kormat created this paste.Wed, May 20, 1:18 PM
root@db2137:/srv# /opt/wmf-mariadb104/scripts/mysql_install_db 

FATAL ERROR: Could not find resolveip

The following directories were searched:

    /opt/wmf-mariadb101/bin
    /opt/wmf-mariadb101/bin

root@db2137:/opt/wmf-mariadb104# ./scripts/mysql_install_db --basedir=/srv/sqldata.s4

FATAL ERROR: Could not find my_print_defaults

The following directories were searched:

/srv/sqldata.s4/bin
/srv/sqldata.s4/extra

If you compiled from source, you need to either run 'make install' to
copy the software into the correct location ready for operation.
If you don't want to do a full install, you can use the --srcdir
option to only install the mysql database and privilege tables.

If you are using a binary release, you must either be at the top
level of the extracted archive, or pass the --basedir option
pointing to that location.

The latest information about mysql_install_db is available at
https://mariadb.com/kb/en/installing-system-tables-mysql_install_db

Kormat added a comment.EditedWed, May 20, 1:43 PM
root@db2137:/opt/wmf-mariadb104# ./scripts/mysql_install_db  --basedir=$PWD --datadir /srv/sqldata.s4/
Installing MariaDB/MySQL system tables in './data' ...
2020-05-20 13:42:54 0 [Warning] No argument was provided to --log-bin and neither --log-basename or --log-bin-index where used;  This may cause repliction to break when this server acts as a master and has its hostname changed! Please use '--log-basename=db2137' or '--log-bin=db2137-bin' to avoid this problem.
2020-05-20 13:42:54 0 [ERROR] mysqld: Plugin 'unix_socket' already installed
2020-05-20 13:42:54 0 [ERROR] Couldn't load plugin 'unix_socket' from 'auth_socket.so'.
2020-05-20 13:42:54 0 [Warning] The parameter innodb_file_format is deprecated and has no effect. It may be removed in future releases. See https://mariadb.com/kb/en/library/xtradbinnodb-file-format/
2020-05-20 13:42:54 0 [Warning] InnoDB: Using innodb_locks_unsafe_for_binlog is DEPRECATED. This option may be removed in future releases. Please use READ COMMITTED transaction isolation level instead; Please refer to https://mariadb.com/kb/en/library/set-transaction/
2020-05-20 13:42:54 6 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1017: Can't find file: './mysql/' (errno: 2 "No such file or directory")
OK

To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system


Two all-privilege accounts were created.
One is root@localhost, it has no password, but you need to
be system 'root' user to connect. Use, for example, sudo mysql
The second is mysql@localhost, it has no password either, but
you need to be the system 'mysql' user to connect.
After connecting you can set the password, if you would need to be
able to connect as any of these users with a password and without sudo

See the MariaDB Knowledgebase at http://mariadb.com/kb or the
MySQL manual for more instructions.

You can start the MariaDB daemon with:
cd '/opt/wmf-mariadb104' ; /opt/wmf-mariadb104/bin/mysqld_safe --datadir='./data'

You can test the MariaDB daemon with mysql-test-run.pl
cd '/opt/wmf-mariadb104/mysql-test' ; perl mysql-test-run.pl

Please report any problems at http://mariadb.org/jira

The latest information about MariaDB is available at http://mariadb.org/.
You can find additional information about the MySQL part at:
http://dev.mysql.com
Consider joining MariaDB's strong and vibrant community:
https://mariadb.org/get-involved/
root@db2137:~# /opt/wmf-mariadb104/bin/mysql_secure_installation --basedir=/opt/wmf-mariadb104/ -S /run/mysqld/mysqld.s4.sock                                                                             [21/2001]
print: /opt/wmf-mariadb104//bin/my_print_defaults

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
      SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!

In order to log into MariaDB to secure it, we'll need the current
password for the root user. If you've just installed MariaDB, and
haven't set the root password yet, you should just press enter here.

Enter current password for root (enter for none):
OK, successfully used password, moving on...

Setting the root password or using the unix_socket ensures that nobody
can log into the MariaDB root user without the proper authorisation.

You already have your root account protected, so you can safely answer 'n'.

Switch to unix_socket authentication [Y/n]
Enabled successfully!
Reloading privilege tables..
 ... Success!


You already have your root account protected, so you can safely answer 'n'.

Change the root password? [Y/n] n
 ... skipping.

By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them.  This is intended only for testing, and to make the installation
go a bit smoother.  You should remove them before moving into a
production environment.

Remove anonymous users? [Y/n]
 ... Success!

Normally, root should only be allowed to connect from 'localhost'.  This
ensures that someone cannot guess at the root password from the network.

Disallow root login remotely? [Y/n]
 ... Success!

By default, MariaDB comes with a database named 'test' that anyone can
access.  This is also intended only for testing, and should be removed
before moving into a production environment.

Remove test database and access to it? [Y/n]
 - Dropping test database...
 ... Success!
 - Removing privileges on test database...
 ... Success!

Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.

Reload privilege tables now? [Y/n]
 ... Success!

Cleaning up...

All done!  If you've completed all of the above steps, your MariaDB
installation should now be secure.

Thanks for using MariaDB!