- discuss - lists.mariadb.org

[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

[Maria-discuss] CONC-312; caching_sha2_plugin
by Michal Schorm 02 Oct '18

02 Oct '18

Hello, Can I get some explanation, why was https://jira.mariadb.org/browse/CONC-312 closed as WON'T FIX ? -- MySQL 8.0 implemented "caching_sha2_password" as its default authentification plugin / method. MariaDB doesn't have support for it so mariadb-connector-c cannot be used for MySQL 8. That makes problems for nearly every Linux OS, beacuse they chose MariaDB over MySQL as the default implemetation. I'd like to know the MariaDB stance to it. Do you see it as an issue as well? Are there any plans to deal with it? How? Michal Schorm -- Michal Schorm Associate Software Engineer Core Services - Databases Team Red Hat

2 2

[Maria-discuss] Step-by-Step Tutorial: How to Setup Your Own e-Commerce Online Store using WooCommerce 3.4.5, Wordpress 4.9.8, and CentOS 1805 (LAMP) in Amazon AWS Cloud
by Turritopsis Dohrnii Teo En Ming 29 Sep '18

29 Sep '18

Good morning from Singapore, You can read my step-by-step tutorial on How to Setup Your Own e-Commerce Online Store using WooCommerce 3.4.5, Wordpress 4.9.8, and CentOS 1805 (LAMP) in Amazon AWS Cloud at any one of my two redundant blogs. My blogs were configured in RAID 1 mirroring array. https://tdtemcerts.wordpress.com/2018/09/29/step-by-step-tutorial-how-to-se… https://tdtemcerts.blogspot.com/2018/09/step-by-step-tutorial-how-to-setup-… Thanks for reading! If there are any mistakes, please do let me know! ===BEGIN SIGNATURE=== Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 30 Oct 2017 [1] https://tdtemcerts.wordpress.com/ <https://tdtemcerts.wordpress.com/>[2] http://tdtemcerts.blogspot.sg/ <http://tdtemcerts.blogspot.sg/>[3] https://www.scribd.com/user/270125049/Teo-En-Ming <https://www.scribd.com/user/270125049/Teo-En-Ming>===END SIGNATURE===

1 0

Re: [Maria-discuss] MariaDB 10.3 and largepages on Linux
by Kenneth Penza 26 Sep '18

26 Sep '18

Good morning, Thanks for the clarification. Yes sure, below please find the requested output. If you prefer I can open a JIRA ticket to facilitate tracking. $ cat /proc/sys/vm/nr_hugepages 512 $ uname -a Linux srv1 3.10.0-862.11.6.el7.x86_64 #1 SMP Fri Aug 10 16:55:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ grep ^Huge /proc/meminfo HugePages_Total: 512 HugePages_Free: 467 HugePages_Rsvd: 167 HugePages_Surp: 0 Hugepagesize: 2048 kB $ grep mysql /etc/security/limits.conf mysql soft memlock 2621440 mysql hard memlock 2621440 $ grep AnonHugePages /proc/meminfo AnonHugePages: 6144 kB $ cat /etc/sysctl.d/99-mysql.conf vm.hugetlb_shm_group = 27 vm.nr_hugepages = 512 vm.swappiness = 10 fs.aio-max-nr = 500000 $ I have also added, "LimitMEMLOCK=2147483648" in systemd file. Kenneth On Wed, Sep 26, 2018 at 1:01 AM Daniel Black <daniel(a)linux.ibm.com> wrote: > On Tue, 25 Sep 2018 10:48:01 +0200 > Kenneth Penza <kpenza(a)gmail.com> wrote: > > > Good morning, > > > Good morning, > > Thanks for the detailed bug report. As the contributor of this feature > I'm happy to try to work this out. First I'll reassure you that the > WARNING is simply that, there's no negative impacts form this apart > from any unexpected core dump will include the large pages as it failed > to to mark them as don't dump. > > A couple of small clarifying questions to start: > > Do you have THP enabled? > $ cat /proc/sys/vm/nr_hugepages > > What kernel version / architecture? > $ uname -a > > What huge page size / current allocation is available? > > $ grep ^Huge /proc/meminfo > > > > 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 > >

1 0

[Maria-discuss] pam / ldap auth
by mourik jan c heupink 25 Sep '18

25 Sep '18

Hi, I installed mariadb using the stock debian packages, configured pam authentication, and configured a mysql pam module like this: > /etc/pam.d/mysql > auth required pam_winbind.so > account required pam_winbind.so As I also added the server to my AD domain, this basically gives my samba winbind users access to mysql using their windows credentials: > root@mysqlserver:~# mysql -udomain_username -p > Enter password: <windows_domain_password> > Welcome to the MariaDB monitor. Commands end with ; or \g. > Your MariaDB connection id is 6 > Server version: 10.1.26-MariaDB-0+deb9u1 Debian 9.1 > > Copyright (c) 2000, 2017, Oracle, MariaDB Corporation Ab and others. > > Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. > > MariaDB [(none)]> So I was happy. Initially. :-) Until I found out this works only from the localhost mariadb is running on. Trying this from a remote mysql client gives: > user@e7470 ~ $ mysql -udomain_user -p -h mysqlserver.full.address > Enter password: ERROR 2059 (HY000): Authentication plugin 'dialog' cannot be loaded: /usr/lib/mysql/plugin/dialog.so: cannot open shared object file: No such file or directory and searching on that remote server for /usr/lib/mysql/plugin/dialog.so gives no results: > user@e7470 ~ $ dpkg --search /usr/lib/mysql/plugin/dialog.so > dpkg-query: no path found matching pattern /usr/lib/mysql/plugin/dialog.so Anyone here with a good suggestion how to make this work from a 'regular' remote mysql client? But more fundamentally: is it possible to have mariadb ldap auth on a server, *without* requiring anything special on the client side? MJ

4 6