January 2018 - discuss - lists.mariadb.org

[Maria-discuss] why stdout? -> [Note] /usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096
by Reindl Harald 05 Jul '20

05 Jul '20

Aug 6 12:24:24 testserver mysqld: 150806 12:24:24 [Note] /usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096 ... why is this now stdout instead mysql logs? on systemd based distributions that spits now to the global syslog and finally on machines restarting 2 instances every hour for backup reasons it annoys until 10.0.19 or 10.0.20 that was not this way

5 13

[Maria-discuss] MariaDB-10.2.11 Long Time To Start
by Michael Caplan 15 Mar '19

15 Mar '19

Hi, I'm setting up a replication slave based off of MySQL 5.6. There are a large number of tables (400K). The MySQL 5.6 master takes around 10 minutes to start up, where the new MariaDB 10.2 slave takes close to 30 minutes. What is making the startup take soo long? In the below mysql log, you can see in the startup sequence between "Highest supported file format is Barracuda." and "InnoDB: 128 out of 128 rollback segments are active." the startup process takes the majority of its time: 2018-01-07 9:38:15 139980432365760 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-01-07 9:38:15 139980432365760 [Note] InnoDB: Uses event mutexes 2018-01-07 9:38:15 139980432365760 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-01-07 9:38:15 139980432365760 [Note] InnoDB: Using Linux native AIO 2018-01-07 9:38:15 139980432365760 [Note] InnoDB: Number of pools: 1 2018-01-07 9:38:15 139980432365760 [Note] InnoDB: Using SSE2 crc32 instructions 2018-01-07 9:38:15 139980432365760 [Note] InnoDB: Initializing buffer pool, total size = 54G, instances = 8, chunk size = 128M 2018-01-07 9:38:18 139980432365760 [Note] InnoDB: Completed initialization of buffer pool 2018-01-07 9:38:18 139918113195776 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-01-07 9:38:18 139980432365760 [Note] InnoDB: Highest supported file format is Barracuda. 2018-01-07 10:11:48 139980432365760 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-01-07 10:11:48 139980432365760 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-01-07 10:11:48 139980432365760 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-01-07 10:11:48 139980432365760 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-01-07 10:11:48 139980432365760 [Note] InnoDB: Waiting for purge to start 2018-01-07 10:11:48 139980432365760 [Note] InnoDB: 5.7.20 started; log sequence number 1394303471760 2018-01-07 10:11:48 139919461500672 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-01-07 10:11:48 139980432365760 [Note] Server socket created on IP: '::'. 2018-01-07 10:11:49 139980432365760 [Note] Reading of all Master_info entries succeded 2018-01-07 10:11:49 139980432365760 [Note] Added new Master_info '' to hash table 2018-01-07 10:11:49 139980432365760 [Note] /usr/sbin/mysqld: ready for connections. Version: '10.2.11-MariaDB-10.2.11+maria~xenial-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 mariadb.org binary distribution Any ideas why? I've included my my.conf file below. Thanks, Mike # Generated by Percona Configuration Wizard (http://tools.percona.com/) version REL5-20120208 # Configuration name usaddxprdsqlpm3 generated formcaplan(a)labnet.net at 2017-12-22 13:49:58 [mysql] # CLIENT # port = 3306 socket = /var/lib/mysql/mysql.sock [mysqladmin] # CLIENT # port = 3306 socket = /var/lib/mysql/mysql.sock [mysqld] # GENERAL # user = mysql default-storage-engine = InnoDB socket = /var/lib/mysql/mysql.sock pid-file = /var/lib/mysql/mysql.pid character-set-server = utf8 collation_server = utf8_general_ci performance_schema = 0 # MyISAM # key-buffer-size = 32M myisam-recover = FORCE,BACKUP # SAFETY # max-allowed-packet = 20M max-connect-errors = 1000000 skip-name-resolve sysdate-is-now = 1 innodb = FORCE # DATA STORAGE # datadir = /var/lib/mysql/ # BINARY LOGGING # log-bin = /var/lib/mysql/mysql-bin binlog_format = MIXED server-id = 3 expire-logs-days = 7 sync-binlog = 1 # REPLICATION # read-only = 1 skip-slave-start = 1 log-slave-updates = 1 relay-log = /var/lib/mysql/relay-bin slave-net-timeout = 60 sync-master-info = 1 sync-relay-log = 1 sync-relay-log-info = 1 # CACHES AND LIMITS # tmp-table-size = 32M max-heap-table-size = 32M query-cache-type = 0 query-cache-size = 0 max-connections = 500 thread-cache-size = 50 open-files-limit = 65535 table-definition-cache = 4096 table-open-cache = 10240 # INNODB # innodb-flush-method = O_DIRECT innodb-log-files-in-group = 2 innodb-log-file-size = 512M innodb-flush-log-at-trx-commit = 1 innodb-file-per-table = 1 innodb-buffer-pool-size = 54G # LOGGING # log-error = /var/lib/mysql/mysql-error.log log-queries-not-using-indexes = 0 slow-query-log = 0 slow-query-log-file = /var/lib/mysql/mysql-slow.log [mariadb] plugin-load-add=file_key_management file_key_management_filename=/var/lib/mysql/keys.enc file_key_management_filekey=FILE:/var/lib/mysql/mysql.key file_key_management_encryption_algorithm=AES_CTR encrypt_binlog=0

3 19

[Maria-discuss] Charsets and collations
by Peter Laursen 20 Apr '18

20 Apr '18

Does anybody know if there are any plans to bring collations added in MySQL 8 - refer http://mysqlserverteam.com/new-collations-in-mysql-8-0-0/ - to MariaDB and are there any plans to change the default charset to a unicode-based one? -- Peter -- Webyog

2 2

[Maria-discuss] Aurora 'rds.amazonaws.com' string detection
by Evan Burke 31 Jan '18

31 Jan '18

Hi, I recently resolved an issue with an application using the MariaDB JDBC driver being unable to connect to an Amazon Aurora MySQL-compatible database (single instance, not cluster). This turned out to be caused by using 'dblink.[examplehostname].com' for my Aurora connection string, rather than the ...rds.amazonaws.com string checked for in UrlParser.java - https://github.com/MariaDB/mariadb-connector-j/blob/386819936ffad08d0ac2134… I see the code comment indicating that there are problems with detecting Aurora via other methods, as well as compatibility issues preventing the ability to connect to Aurora without a special case, so to some extent I can understand the decision to use hostname or haMode detection. But I wanted to point out that this approach comes with downsides - particularly when it is not documented anywhere that I can see. We had to review the code itself on Github in order to identify the solution, and that's a problem. While I don't expect my experience to be the same as most users, I can't be the only one using an alternate hostname or an IP address to connect, or the only one making the reasonable assumption that the driver is hostname-agnostic. The other consideration - which I am admittedly making somewhat naively - is that the MySQL JDBC driver is able to connect to this Aurora instance without any problems, regardless of hostname. From the perspective of an end user who doesn't care too much about implementation details, I'm probably going to prefer the option that doesn't exhibit unexpected behavior. In any case - despite the frustrating experience I had - I am grateful to everyone who's contributed to the MariaDB project, and I hope my feedback is helpful. -Evan

1 0

[Maria-discuss] Fwd: mysql_insert_id() for INSERT...SELECT statement
by Yuki . 30 Jan '18

30 Jan '18

Hi, I made a post at https://stackoverflow.com/questions/48306962/mysql- insert-id-for-insert-select-statement, but have not received any helpful answer, may be you could help me. I am using MaridDB but I read MySQL documentation because it has much more elaborated documentation than the same page for MariaDB. I am doing similar INSERT...SELECT query to this INSERT INTO table (value1, value2) SELECT 'stuff for value1', 'stuff for value2' FROM DUAL WHERE NOT EXISTS (SELECT * FROM table WHERE value1='stuff for value1' AND value2='stuff for value2') LIMIT 1 , where table has auto-genrated id. And I would like to know if it was inserted or not, of course. I assume the way to do that is to use `mysql_insert_id()`. It returns 0 if no insertions happen and 1 if insertions happen. Looking more details [here]( https://dev.mysql.com/doc/refman/5.7/en/mysql-insert-id.html). > If an INSERT ... SELECT statement is executed, and **NO** automatically > generated value is successfully inserted, mysql_insert_id() **RETURNS** > the ID of the last inserted row. What does it return if no auto-generated ID was successfully inserted? Is this a doc typo? So far I did testing in C and `mysql_insert_id()` returns always 0 if insertion did not happen even if the last insertion succeeded and `mysql_insert_id()` returned non-zero result. A paragraphs in the same manual, mentioned above, confirms this behavior by saying: > mysql_insert_id() returns 0 if the previous statement does not use an AUTO_INCREMENT value. .... > > The value of mysql_insert_id() is affected only by statements issued within the current client connection. It is not affected by statements issued by other clients. > > The LAST_INSERT_ID() SQL function will contain the value of the first automatically generated value that was successfully inserted. LAST_INSERT_ID() is not reset between statements because the value of that function is maintained in the server. .... And that feels kind of logical otherwise `INSERT...SELECT` would be useless in many cases, if you cannot know within the code if your insertion worked or not. But it totally contradicts to the statement above. Did anyone have experience with this? >From MariaDB manual, also suggests that the value should be zero in case of insertion did not happen: > The mysql_insert_id() function returns the ID generated by a query on > a table with a column having the AUTO_INCREMENT attribute or the value > for the last usage of LAST_INSERT_ID(expr). If the last query wasn't > an INSERT or UPDATE statement or if the modified table does not have a > column with the AUTO_INCREMENT attribute and LAST_INSERT_ID was not > used, this function will return zero. Does `mysql_insert_id()` of MariaDB returns 0 for `INSERT...SELECT` if an insertion did not happen, or it might return some other non-zero value? Do you think it is a typo at MySQL documentation? Best, Yuki

2 3

[Maria-discuss] Replication set up to ignore Delete statements
by Furlong, John 25 Jan '18

25 Jan '18

I am new to MariaDB and am wondering if it's possible to set up replication to only replicate INSERTS & UPDATES? Can Deletes be ignored? The purpose is to keep the primary DB small and the secondary DB would be a data warehouse. Does --binlog-format=STATEMENT mean all writes? I've been reading the documention but haven't been able to find a definitive answer. If Delete statements are executed by a different user is it possible to ignore them that way such as through the CURRENT_USER()<https://mariadb.com/kb/en/current_user/> function? Thanks. John

1 0

[Maria-discuss] ALTER TABLE ENIGNE=InnoDB performance
by Conor Murphy 25 Jan '18

25 Jan '18

Hi, We're looking at changing an existing database from MyISAM to InnoDB. The existing system is using MariaDB 5.5.56 on RHEL 7.4 The plan is to - create a replication slave on the same host - use ALTER TABLE .. ENGINE=InnoDB on the slave, with 4 ALTERs running concurrently - replace the master with the "coverted" slave Doing this with a small database (~ 3.5GB) works okay with the largest table taking ~ 7 minutes to convert. However, while trying to figure out how to replicate from the new master, we found that we need "FLUSH TABLES .. FOR EXPORT" which isn't available in MariaDB 5.5. So we updated to MariaDB 10.2.12 and started again. Now when we run the "ALTER TABLE .. ENIGNE=InnoDB", it takes hours from the ALTERs to complete and we're getting the following log entries 2018-01-09 12:36:03 140132036818688 [ERROR] InnoDB: Cannot save table statistics for table `statsdb`.`#sql-6d1a_12#P#P20160101` /* Partition `P20160101` */: Lock wait timeout 2018-01-09 12:36:54 140132036515584 [ERROR] InnoDB: Cannot save table statistics for table `statsdb`.`#sql-6d1a_13#P#P20160101` /* Partition `P20160101` */: Lock wait timeout 2018-01-09 12:37:45 140132036818688 [ERROR] InnoDB: Cannot save table statistics for table `statsdb`.`#sql-6d1a_12#P#P20160601` /* Partition `P20160601` */: Lock wait timeout 2018-01-09 12:38:36 140132036818688 [ERROR] InnoDB: Cannot save table statistics for table `statsdb`.`#sql-6d1a_12#P#P20160701` /* Partition `P20160701` */: Lock wait timeout 2018-01-09 12:39:27 140132037728000 [ERROR] InnoDB: Cannot save table statistics for table `statsdb`.`#sql-6d1a_11#P#P20160701` /* Partition `P20160701` */: Lock wait timeout ... Any ideas on what's wrong here? Thanks, Conor

3 8

[Maria-discuss] MariaDB 10.3.4 consumes extremely much CPU on Windows.
by Peter Laursen 21 Jan '18

21 Jan '18

On a 4-core (4 physical, 8 logical cores), 3.5 Ghz box, MariaDB 10.3.4 consumes typically 35-40% of available CPU even when completely idle according to Task Manager. Please see image. I cannot tell if previous 10.3 versions also did, as I don't have 10.3 running constantly in the backgorund. I just observed this now. This does not happen with MariaDB 10.1, MariaDB 10.2, MySQL 5.6, MySQL 5.7 and MySQL 8.0 (all those I have starting with Windows on this box), where the CPU-load is neglible unless the server is "doing real work". As a result, the CPU clock frequency is always highest possible 3.5 Ghz (this CPU model is a 4th generation Intel with the option to scale down CPU frequency to around 40-50% of max. when there is no need for more) when MariaDB 10.3.4 is running. -- Peter -- Webyog

2 7

[Maria-discuss] OpenLDAP & PAM authentication
by Adam Balgach 19 Jan '18

19 Jan '18

Hello – I am having an issue configuring openLDAP to authenticate users on an instance in RHEL (CentOS 7) MariaDB server configured with plugin-load=auth_pam.so in my /etc/pam.d/mysql: auth required pam_ldap.so account required pam_ldap.so when I try and access the server from either the localhost, or any server inside my internal network, I see the LDAP authentication happen without issue and login is fine. When I try and access the server from outside the network, on the mariadb server in /var/log/secure I see the following: Jan 19 08:32:35 mysqld: pam_ldap(mysql:auth): unexpected response from failed conversation function Jan 19 08:32:35 mysqld: pam_ldap(mysql:auth): conversation failed Jan 19 08:32:35 mysqld: pam_ldap(mysql:auth): failed to get password: Authentication token manipulation error And in my client (Cygwin) I get the following error: ERROR 2059 (HY000): Authentication plugin 'mysql_clear_password' cannot be loaded: No such file or directory However I see this plugin in the /usr/lib64/mysql/plugin directory Any idea what is going wrong with remote logins? Thanks-

2 1

[Maria-discuss] MariaDB 10.3.4 installation blocked ny MS "Windows Defender" malware protection
by Peter Laursen 19 Jan '18

19 Jan '18

Please see image. (you can clik "more info" adn the option to "install anyway" will appear. Did you forget to sign the installer this time or has some certificate expired? -- Peter -- Webog

2 5