- discuss - lists.mariadb.org

[Maria-discuss] account locking?
by Felipe Gasper 05 Nov '18

05 Nov '18

Hello, Does the MariaDB development team intend to add account locking? I don’t see it in the 10.4 roadmap. MySQL added this in 5.7.6. Previously we’d accomplished this by reversing the password hash; for our servers that run MariaDB it would be great to be able to use the same facility. Thank you! -Felipe Gasper

2 1

[Maria-discuss] wsrep_node_incoming_address not honoured?
by George Diamantopoulos 02 Nov '18

02 Nov '18

Hello all, I've setup a galera cluster with 3 nodes, and I believe that wsrep_node_incoming_address is not honoured when set in the configuration. More specifically, the setting persists in mariadb: +-----------------------------+---------------+ | Variable_name | Value | +-----------------------------+---------------+ | bind_address | 172.30.20.1 | | wsrep_node_address | 172.30.20.129 | | wsrep_node_incoming_address | 172.30.20.129 | | wsrep_sst_receive_address | 172.30.20.129 | +-----------------------------+---------------+ But the process listens on all interfaces instead: root@gal0-cn1:~# netstat -plunt | grep mysql tcp 0 0 172.30.20.1:3306 0.0.0.0:* LISTEN 17229/mysqld tcp 0 0 0.0.0.0:4567 0.0.0.0:* LISTEN 17229/mysqld Is this expected behaviour? Shouldn't mysqld only listen on 172.30.20.129:4567, as configured? Thanks! BR, George

2 2

[Maria-discuss] Modify Global Variable "open_files_limit" not working
by c.monty＠web.de 02 Nov '18

02 Nov '18

2 1

[Maria-discuss] adding syslog crashes container
by Paul Chubb 30 Oct '18

30 Oct '18

hi I am trying to get Mariadb to log to syslog - this is for log consolidation etc. I am using Maria in a docker container from docker hub. Other things from the container are successfully logging to syslog on my logging server but Maria isn't. If I add the word 'syslog' to a [mysqld_safe] section the configuration is not read (as reported by mysqld --print-defaults). The container init script calls mysqld rather than mysqld_safe If I change the init script to call mysqld_safe instead of mysqld, syslog is set as reported by --print-defaults however the container continually crashes after restart. If I add the word 'syslog' to [mysqld] the configuration is read however after restart, mariadb continually crashes - at least the container does. I have checked for log-error statements, when checking global vars log_error is empty and it is not reported on the print-defaults output. If I setup to log to a file, this works fine. The container is running Ubuntu 18.04 Mariadb version is 10.3.10 rsyslog version is kinetic 8.32.0 Not sure what you want to see to help me, advise and I will do my best to give it to you. Cheers paul

3 3

[Maria-discuss] Secure replication with mariadb
by Danishka Navin 26 Oct '18

26 Oct '18

Hi Team, I am working on deploying moodle (using mariadb) in over 1000 centers and connect each remote center with central server. Each remote center has no identical data as users are totally different. (But same type of data across these 1000 remote center nodes). We can not gurrenty the connectivity between remote server and centralized server in all 1000 nodes (some of the remote servers may have connectivity issues but we need to recover all data once the connectivity establish). Is it possible to replicate each remote server in to single central server over TLS? or do we have better solution? Regards, Danishka

1 0

[Maria-discuss] My Solution to MariaDB Database Server Crashed in Experimental Online Store
by Turritopsis Dohrnii Teo En Ming 23 Oct '18

23 Oct '18

Good evening from Singapore, Here is my solution: # systemctl start mariadb.service # mysql Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 2 Server version: 5.5.60-MariaDB MariaDB Server Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> quit Bye # systemctl enable mariadb.service ===BEGIN SIGNATURE=== Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 30 Oct 2017 [1] https://tdtemcerts.wordpress.com/ [2] http://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming ===END SIGNATURE===

4 8

[Maria-discuss] aws key management plugin
by Paul Chubb 19 Oct '18

19 Oct '18

Hi, on the repo there only seems to be copies of this for Ubuntu yacketty (16.10) and Ubuntu zesty (17.04). Both of these are end of life. Is there supposed to be support for Bionic (18.04)? Secondly, they are tagged with the mariadb version number. Are they supposed to work across versions because not every version of Mariadb is represented? Thirdly is there any reason I can't pull the code from Gidhub and compile it myself? Many thanks in advance Paul

3 4

[Maria-discuss] help
by Paul Chubb 18 Oct '18

18 Oct '18

1 0

[Maria-discuss] gtid_slave_pos row count
by Reinis Rozitis 15 Oct '18

15 Oct '18

Hi, before considering this as a bug wanted to ask in mailing list: I know that gtid_slave_pos table can have multiple entries, but (at least on 10.3.9 but maybe also earlier (just noticed now)) while running: slave_parallel_threads = 20 slave_parallel_mode = optimistic the table starts to grow continuously: MariaDB [mysql]> select count(*) from gtid_slave_pos; +----------+ | count(*) | +----------+ | 5577268 | +----------+ 1 row in set (1.553 sec) If I switch back to conservative mode it never goes above 2-3 rows even with the same 20 threads. Same happens also with gtid_pos_auto_engines - when in conservative each engine table has several records, once I switch to optimistic the gtid tables just grow. Is there something wrong with the purger? (something similar like in https://jira.mariadb.org/browse/MDEV-12147 ? ) rr

2 10

[Maria-discuss] MariaDB 10.3 and largepages on Linux
by Kenneth Penza 12 Oct '18

12 Oct '18

Good morning, I am currently running RHEL 7.5 and MariaDB 10.3.9. After setting "large_pages=on" I noticed that MariaDB is reporting an error on startup and shutdown as per below output. To use large pages I modified /etc/sysctl.conf, /etc/security/limits.conf and the systemd unit file. By monitoring /proc/meminfo I verified that largepage are being used. Configuration: mysqld would have been started with the following arguments: --port=3306 --socket=/var/lib/mysql/mysql.sock --thread_stack=256K --large_pages=on --key_buffer_size=16K --max_allowed_packet=512M --table_open_cache=32 --sort_buffer_size=512K --net_buffer_length=8K --read_buffer_size=256K --read_rnd_buffer_size=256K --slow_query_log=1 --slow_query_log_file=mysql-slow.log --long_query_time=0.1 --log-queries-not-using-indexes=on --thread_handling=pool-of-threads --thread_pool_idle_timeout=60 --thread_pool_max_threads=1000 --thread_pool_size=8 --innodb_buffer_pool_size=256M --innodb_strict_mode=1 --innodb_file_per_table=1 --innodb_flush_method=O_DIRECT --innodb_log_files_in_group=4 --innodb_log_file_size=50331648 --innodb_undo_logs=128 --innodb_undo_tablespaces=8 --slow_query_log=1 --slow_query_log_file=mysql-slow.log --long_query_time=30 --log-queries-not-using-indexes=off --log_bin=mariadblog --binlog_format=ROW --binlog_row_image=MINIMAL --max_binlog_size=10240000 --expire_logs_days=1 --server-id=1 --innodb_flush_log_at_trx_commit=1 --sync_binlog=1 --relay-log=mariadb-relay-bin --performance_schema=off --histogram_size=255 --histogram_type=SINGLE_PREC_HB --use_stat_tables=preferably --optimizer_use_condition_selectivity=4 Startup messages: Sep 25 10:40:53 srv1 mysqld: 2018-09-25 10:40:52 0 [Note] InnoDB: Opened 8 undo tablespaces Sep 25 10:40:53 srv1 mysqld: 2018-09-25 10:40:53 0 [Warning] InnoDB: Failed to set memory to DODUMP: Invalid argument ptr 0x2aaac5400000 size 2097152 Sep 25 10:40:53 srv1 mysqld: 2018-09-25 10:40:53 0 [Note] InnoDB: 128 out of 128 rollback segments in 8 undo tablespaces are active. Shutdown messages: Sep 25 10:41:18 srv1 mysqld: 2018-09-25 10:41:18 0 [Note] InnoDB: Buffer pool(s) dump completed at 180925 10:41:18 Sep 25 10:41:19 srv1 mysqld: 2018-09-25 10:41:19 0 [Warning] InnoDB: Failed to set memory to DODUMP: Invalid argument ptr 0x2aaac3400000 size 33554432 Sep 25 10:41:19 srv1 mysqld: 2018-09-25 10:41:19 0 [Note] InnoDB: Shutdown completed; log sequence number 1522725; transaction id 22 Do you have ideas on what is causing "InnoDB: Failed to set memory to DODUMP: Invalid argument ptr .. " warning? Kenneth

2 3