May 2020 - discuss - lists.mariadb.org

[Maria-discuss] Single-threaded DDL limitation still present in Galera?
by Artem Russakovskii 13 Aug '20

13 Aug '20

Hi, On this page https://mariadb.com/kb/en/mariadb-galera-cluster-known-limitations/, a user in 2017 pointed out the following: 3 years, 3 months ago Björn Schneider <https://mariadb.com/kb/user/id/4916> Schema changes of large tables in Galera <https://mariadb.com/kb/en/mariadb-galera-cluster-known-limitations/#comment…> You should be warned that every DDL statement executed on a Galera cluster will per default BLOCK the complete cluster (not only the table, or even just the database the table resides in)! This is the default "Total Order Isolation" (TOI) mode. The DDL statements can't be killed - once issued, it will run until completed or an error occurs. Issuing e.g. a column-altering DDL statement on a large table will take the complete cluster out of commission until every node has completed the migration. Only some operations (e.g. changing DEFAULT values) are always short-timed and won't interefere with the cluster's opperations. Long-running, cluster-blocking DDL are of course a no-go on a productive system. To resolve this issue, there are several resulutions; Percona, for example, provides a script to "online" migrate a table (pt-online-schema-change), or you can use the "Rolling Schema Upgrade" (RSU) for data-compatible changes. More about that in the Galera documentation. In my opionion, this behaviour should definitely added as "observation" to this page - it's definitely not something you'd expect coming from a "normal" MariaDB/MySQL system. We're considering moving to a cluster environment from a 1 master - 3 slave configuration that has proven inflexible, but such a severe limitation seems unusable in production. Is this still the case in 2020? What is the reasoning behind such an architectural decision, if so? Thank you. Sincerely, Artem -- Founder, Android Police <http://www.androidpolice.com>, APK Mirror <http://www.apkmirror.com/>, Illogical Robot LLC beerpla.net | @ArtemR <http://twitter.com/ArtemR>

2 3

[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] Error writing to binary log file
by Gustavo Vieira 29 May '20

29 May '20

Hello, I have several MariaDB 10.1.45 instances running in Linux containers with memory limits. This week I have enabled binary logging on all of them with the following parameters: log-bin = mysqld-bin binlog-format = mixed expire_logs_days = 1 After that I have been getting several errors like this in a few of them: [ERROR] mysqld: Error writing file 'mysqld-bin' (errno: 11 "Resource temporarily unavailable") A few also show these other two errors mixed with the previous one: [ERROR] mysqld: Error writing file 'mysqld-bin' (errno: 12 "Cannot allocate memory") [ERROR] mysqld: Error writing file 'mysqld-bin' (errno: 0 "Internal error/check (Not system error)") It gets stuck on this state, reporting errors to every attempt of executing a query. A restart on the service seems to solve the problem, at least temporarily. Does anybody have a clue on why it gets stuck like that? If the container ran out of memory, should not mariadb crash? I could not find any information about this error and binary logs being related. Thanks in advance, Gustavo Vieira

2 2

[Maria-discuss] backup from any cluster member can't be restarted and restored
by Jeff Dyke 27 May '20

27 May '20

This has biting me for a bit, and i have tried a litany of things. Here is the issue: VPC 1: (prod) Mariadb 10.4.12 - galera in a 3 node cluster, cluster functioning perfectly VPC 2: (staging) Mariadb 10.4.12 galera in a 3 node cluster also running smoothly. -- backup script (clipped for only the essentials) -- set -e DIR="/home/jeff/restore" rm -rf $DIR mkdir $DIR AUTH='--defaults-extra-file=/root/db.cnf -u root' sudo mysql ${AUTH} -e "SET GLOBAL wsrep_desync = ON;" sudo mysql ${AUTH} -e "SET GLOBAL wsrep_on = OFF"; sudo mariabackup ${AUTH} --backup --binlog-info=ON --target-dir="${DIR}" 2>&1 | grep -vE "Copying|done|log scanned" sudo mysql ${AUTH} -e "SET GLOBAL wsrep_on = ON;" sudo mysql ${AUTH} -e "SET GLOBAL wsrep_desync = OFF"; -- end script -- -- restore process -- sudo service mariadb stop (or kill -9 PID only when the server won't start) sudo rm -rf /var/lib/mysl/* sudo mariabackup --prepare --target-dir=restore sudo mariabackup --copy-back --target-dir=restore sudo chown -R mysql:mysql /var/lib/mysql/* sudo service mariadb start -- end restore -- I can run this on any of the script and backup process on any of the *staging* nodes and restore them to a freshly built server within that VPC. I can also take the backup from *staging* and load in into a newly build machine on the *prod* VPC. What i can not do is run the script on any of the prod members and restore it to a newly built server, regardless of location. (really the locations don't matter at all) The following is the log from a failing restore from a proddb backup and restore: 2020-04-15 22:11:10 0 [Note] InnoDB: Using Linux native AIO 2020-04-15 22:11:10 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-04-15 22:11:10 0 [Note] InnoDB: Uses event mutexes 2020-04-15 22:11:10 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2020-04-15 22:11:10 0 [Note] InnoDB: Number of pools: 1 2020-04-15 22:11:10 0 [Note] InnoDB: Using SSE2 crc32 instructions 2020-04-15 22:11:10 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts) 2020-04-15 22:11:10 0 [Note] InnoDB: Initializing buffer pool, total size = 2G, instances = 8, chunk size = 128M 2020-04-15 22:11:10 0 [Note] InnoDB: Completed initialization of buffer pool 2020-04-15 22:11:10 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2020-04-15 22:11:10 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 50331648 bytes 2020-04-15 22:11:10 0 [Note] InnoDB: Setting log file ./ib_logfile1 size to 50331648 bytes 2020-04-15 22:11:10 0 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 2020-04-15 22:11:10 0 [Note] InnoDB: New log files created, LSN=42006460184 2020-04-15 22:11:10 0 [Note] InnoDB: 128 out of 128 rollback segments are active. 2020-04-15 22:11:10 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2020-04-15 22:11:10 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2020-04-15 22:11:10 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2020-04-15 22:11:10 0 [Note] InnoDB: Waiting for purge to start 2020-04-15 22:11:10 0 [Note] InnoDB: 10.4.12 started; log sequence number 42006460428; transaction id 23858673 2020-04-15 22:11:10 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2020-04-15 22:11:10 0 [Note] Plugin 'FEEDBACK' is disabled. 2020-04-15 22:11:11 0 [Note] InnoDB: Buffer pool(s) load completed at 200415 22:11:11 -- hangs here for about an hour before timing out -- Logfile from a successful start 2020-04-15 23:13:15 0 [Note] InnoDB: Using Linux native AIO 2020-04-15 23:13:15 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-04-15 23:13:15 0 [Note] InnoDB: Uses event mutexes 2020-04-15 23:13:15 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2020-04-15 23:13:15 0 [Note] InnoDB: Number of pools: 1 2020-04-15 23:13:15 0 [Note] InnoDB: Using SSE2 crc32 instructions 2020-04-15 23:13:15 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts) 2020-04-15 23:13:15 0 [Note] InnoDB: Initializing buffer pool, total size = 2G, instances = 8, chunk size = 128M 2020-04-15 23:13:16 0 [Note] InnoDB: Completed initialization of buffer pool 2020-04-15 23:13:16 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2020-04-15 23:13:16 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 50331648 bytes 2020-04-15 23:13:16 0 [Note] InnoDB: Setting log file ./ib_logfile1 size to 50331648 bytes 2020-04-15 23:13:16 0 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 2020-04-15 23:13:16 0 [Note] InnoDB: New log files created, LSN=43323668550 2020-04-15 23:13:16 0 [Note] InnoDB: 128 out of 128 rollback segments are active. 2020-04-15 23:13:16 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2020-04-15 23:13:16 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2020-04-15 23:13:16 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2020-04-15 23:13:16 0 [Note] InnoDB: Waiting for purge to start 2020-04-15 23:13:16 0 [Note] InnoDB: 10.4.12 started; log sequence number 43323669004; transaction id 22422468 2020-04-15 23:13:16 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2020-04-15 23:13:16 0 [Note] Plugin 'FEEDBACK' is disabled. 2020-04-15 23:13:16 0 [Note] Server socket created on IP: '0.0.0.0'. 2020-04-15 23:13:16 0 [Note] Reading of all Master_info entries succeeded 2020-04-15 23:13:16 0 [Note] Added new Master_info '' to hash table 2020-04-15 23:13:16 0 [Note] /usr/sbin/mysqld: ready for connections. Version: '10.4.12-MariaDB-1:10.4.12+maria~bionic' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution 2020-04-15 23:13:22 0 [Note] InnoDB: Buffer pool(s) load completed at 200415 23:13:22 ------------------------ The main difference between the two is that: - the server socket is logged - master_info is logged - and it binds to the port/socket Before they *both* end with 2020-04-15 23:13:22 0 [Note] InnoDB: Buffer pool(s) load completed at 200415 23:13:22 -- Other Notes -- - Config files are the same except for ips, both on newly built servers as the cluster as they are managed through salt. I ran a diff -r against prod vs staging and only saw There has to be some corruption in the mariabackup output, but still reported OK. Since i can put a staging backup on a prod server, but i can not put a prod backup on a staging server. If you've gotten this far, thank you. If you have any ideas on what i could try, i'd be grateful. aria_chk and all other table checks return correctly. I'm not sure what makes a server write out the master_info, so possibly that is a pointer. I'm happy to answer any questions, i've tried way to many things to post here as i didn't want to write until i had enough of dumb stuff figured out. I could rebuild the prod cluster but am really looking to understand this. I don't really want to build my own with debug info on b/c why would they be different between the two vpcs.

3 10

[Maria-discuss] Alter table engine causes duplicate key
by Ling, Andy 26 May '20

26 May '20

I'm using MariDB 10.4.12 on Windows server 2016 I have a table with one of the columns defined as `id` bigint(20) NOT NULL AUTO_INCREMENT and PRIMARY KEY (`id`) It is currently a MyISAM table and has been in use for ages. The current auto increment value is AUTO_INCREMENT=106274948879084. Rows have been added and removed over time such that there are gaps in the id value. The table passes all checks, so there are no duplicate entries. I recently tried to change the table to use the Aria engine using the command ALTER TABLE xxx ENGINE=ARIA; and got the error ERROR 1062 (23000) at line 4: ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '106274948781020' for key 'PRIMARY' I can fix the problem by resetting the auto increment values using ALTER TABLE xxx AUTO_INCREMENT=1; but is this something I should expect? First, I don't really see why it is resequencing. No data should be changing. Then why is the resequencing generating a duplicate entry? Fortunately in this instance I don't care what the id is, but had this been used by another table, changing the id may have caused problems. Thanks for any help on this. Andy Ling ********************************************************************** DISCLAIMER: Privileged and/or Confidential information may be contained in this message. If you are not the addressee of this message, you may not copy, use or deliver this message to anyone. In such event, you should destroy the message and kindly notify the sender by reply e-mail. It is understood that opinions or conclusions that do not relate to the official business of the company are neither given nor endorsed by the company. Thank You.

1 0

[Maria-discuss] How to select values at particular time with two temporal tables in MariaDB?
by unit unit 26 May '20

26 May '20

Hi, I'm interested in using MariaDB for temporal data but I'm a bit uncertain on how to solve certain use cases. As an example let's say I define two temporal tables<https://mariadb.com/kb/en/temporal-data-tables> using application time periods<https://mariadb.com/kb/en/temporal-data-tables/#application-time-periods> where one table has a one to many relationship with the other. For example: [cid:8f4d19a2-4743-4e32-9516-16a626f9169f] What I'm looking for is a way to "select a teacher and count the number of associated classes for this teacher" at a moment in time. My questions are: 1. How would I define/create the two tables using temporal tables? 2. What would such a select statement look like? 3. What indexes should be created in order to make the select statement efficient? Note that it's very important that the query is expressed using application time and not system time. BR, /Johan

1 0

[Maria-discuss] Making wsrep_sst_mariabackup more SELinux friendly
by Scott A. Wozny 23 May '20

23 May '20

I’m switching over from Percona XtraDB Cluster 5.7 to MariaDB 10.3 with Galera support on CentOS 7. During this process things have gone mostly smoothly, but I’ve found a lot of SELinux AVC failures once I started testing. Some googling later and I found this article which describes the heart of my issue and it appears to center around a fix that was put into wsrep_sst_xtrabackup-v2 in the Percona repositories, but still exists in wsrep_sst_mariabackup (which, I guess, was ported AFTER Percona made their changes). https://dzone.com/articles/lock-down-enforcing-selinux-with-percona-xtradb-… For the TL;DR set, the crux is this. In the wsrep_sst_mariabackup script, the wait_for_listen function scans all the processes, which upsets SELinux who either forbids or logs the scan of every listening process on the system that mysqld_t doesn’t have rights to do a process getattr on. Solutions to this include runing SELinux in permission mode or allowing a process getattr from mysqld_t to every type attached to a listening process, neither of which is appealing. So where MariaDB 10.3 wsrep_sst_mariabackup calls wait_for_listen() like this: wait_for_listen ${SST_PORT} ${ADDR} ${MODULE} & and executes this function: # waits ~10 seconds for nc to open the port and then reports ready # (regardless of timeout) wait_for_listen() { local PORT=$1 local ADDR=$2 local MODULE=$3 for i in {1..50} do if [ "$OS" = "FreeBSD" ];then sockstat -46lp $PORT | grep -qE "^[^ ]* *(socat|nc) *[^ ]* *[^ ]* *[^ ]* *[^ ]*:$PORT" &&$ else ss -p state listening "( sport = :$PORT )" | grep -qE 'socat|nc' && break fi sleep 0.2 done echo "ready ${ADDR}/${MODULE}//$sst_ver" } Which causes SELinux to light up like a Christmas tree. PXC 5.7’s wsrep_sst_xtrabackup-v2 calls wait_for_listen() like this: # Note: this is started as a background process # So it has to wait for processes that are started by THIS process wait_for_listen $$ ${WSREP_SST_OPT_HOST} ${WSREP_SST_OPT_PORT:-4444} ${MODULE} & and executes this function: # waits ~1 minute for nc/socat to open the port and then reports ready # (regardless of timeout) # # Assumptions: # 1. The socat/nc processes do not launch subprocesses to handle # the connections. Note that socat can be configured to do so. # 2. socat is not bound to a specific interface/address, so the # IP portion of the local address is all zeros (0000...000). # # Parameter 1: the pid of the wsrep_sst_xtrabackup-v2 process. We are looking # for the socat process that was started by this script. # Parameter 2: the IP address of the SST host # Parameter 3: the Port of the SST host # Parameter 4: a descriptive name for what we are doing at this point # wait_for_listen() { local parentpid=$1 local host=$2 local port=$3 local module=$4 # # Check to see if the OS supports /proc/<pid>/net/tcp # if [[ ! -r /proc/$$/net/tcp && ! -r /proc/$$/net/tcp6 ]]; then wsrep_log_debug "$LINENO: Using ss for socat/nc discovery" # Revert to using ss to check if socat/nc is listening wsrep_check_program ss if [[ $? -ne 0 ]]; then wsrep_log_error "******** FATAL ERROR *********************** " wsrep_log_error "* Could not find 'ss'. Check that it is installed and in the path." wsrep_log_error "******************************************** " return 2 fi for i in {1..300} do ss -p state listening "( sport = :${port} )" | grep -qE 'socat|nc' && break sleep 0.2 done echo "ready ${host}:${port}/${module}//$sst_ver" return 0 fi wsrep_log_debug "$LINENO: Using /proc/pid/net/tcp for socat/nc discovery" # Get the index for the 'local_address' column in /proc/xxxx/net/tcp # We expect this to be the same for IPv4 (net/tcp) and IPv6 (net/tcp6) local ip_index=0 local header if [[ -r /proc/$$/net/tcp ]]; then read -ra header <<< $(head -n 1 /proc/$$/net/tcp) elif [[ -r /proc/$$/net/tcp6 ]]; then read -ra header <<< $(head -n 1 /proc/$$/net/tcp6) else wsrep_log_error "******** FATAL ERROR *********************** " wsrep_log_error "* Cannot find /proc/$$/net/tcp (or tcp6)" wsrep_log_error "******************************************** " exit 1 fi for i in "${!header[@]}"; do if [[ ${header[$i]} = "local_address" ]]; then # Add one to the index since arrays are 0-based # but awk is 1-based ip_index=$(( i + 1 )) break fi done if [[ $ip_index -eq 0 ]]; then wsrep_log_error "******** FATAL ERROR *********************** " wsrep_log_error "* Unexpected /proc/xx/net/tcp layout: cannot find local_address" wsrep_log_error "******************************************** " exit 1 fi wsrep_log_debug "$LINENO: local_address index is $ip_index" local port_in_hex port_in_hex=$(printf "%04X" $port) local user_id user_id=$(id -u) for i in {1..300} do # List all socat/nc processes started by the user of this script # Then look for processes that have the script pid as a parent prcoess # somewhere in the process tree wsrep_log_debug "$LINENO: Entering loop body : $i" # List only socat/nc processes started by this user to avoid triggering SELinux for pid in $(ps -u $user_id -o pid,comm | grep -E 'socat|nc' | awk '{ printf $1 " " }') do if [[ -z $pid || $pid = " " ]]; then continue fi wsrep_log_debug "$LINENO: Examining pid: $pid" # Now get the processtree for this pid # If the parentpid is NOT in the process tree, then ignore if ! echo "$(get_parent_pids $pid)" | grep -qw "$parentpid"; then wsrep_log_debug "$LINENO: $parentpid is not in the process tree: $(get_parent_pids $pid)" continue fi # get the sockets for the pid # Note: may not need to get the list of sockets, is it ok to # just look at the list of local addresses in tcp? local sockets sockets=$(ls -l /proc/$pid/fd | grep socket | cut -d'[' -f2 | cut -d ']' -f1 | tr '\n' '|') # remove the trailing '|' sockets=${sockets%|} wsrep_log_debug "$LINENO: sockets: $sockets" if [[ -n $sockets ]]; then # For the network addresses, we expect to be listening # on all interfaces, thus the address should be # 00..000:PORT (all zeros for the IP address). # Dumping the data in the lines #if [[ -n "$WSREP_LOG_DEBUG" ]]; then # lines=$(grep -E "\s(${sockets})\s" /proc/$pid/net/tcp) # if [[ -n $lines ]]; then # while read -r line; do # if [[ -z $line ]]; then # continue # fi # wsrep_log_debug "$LINENO: $line" # done <<< "$lines\n" # fi #fi # Checking IPv4 if grep -E "\s(${sockets})\s" /proc/$pid/net/tcp | awk "{print \$${ip_index}}" | grep -q "^00*:${port_in_hex}$"; then wsrep_log_debug "$LINENO: found a match for pid: $pid" break 2 fi # Also check IPv6 if grep -E "\s(${sockets})\s" /proc/$pid/net/tcp6 | awk "{print \$${ip_index}}" | grep -q "^00*:${port_in_hex}$"; then break 2 fi fi done sleep 0.2 done wsrep_log_debug "$LINENO: wait_for_listen() exiting" echo "ready ${host}:${port}/${module}//$sst_ver" return 0 } which does NOT light up SELinux like a Christmas tree (but DOES still require a few SELinux policy additions to run in enforcing mode). Obviously the PXC function code isn’t directly compatible with the Mariabackup sst script since at the very least it’s not using the same parameters, but can I just change the calling line AND the function itself in my version of wsrep_sst_mariabackup and will it work, or is it more complicated than that? There are also other SELinux AVC failures that I’m prepared to write custom policy for, but I’d like to “patch” the wait_for_listen function in wsrep_sst_mariabackup so I don’t have to remember every time I add a listening daemon on the server that I need to rebuild my custom SELinux policy. If the author of the article is correct, the custom SELinux policy allows needed OUTSIDE the noisy listening port scan should be pretty static and only need a re-check on major version upgrades. So, I know this was a lot and if you think I should take this to the devs list, please let me know. I was hoping there might be a powerful enough user on this list who could suggest the code changes needed in wsrep_sst_mariabackup to get me around the most onerous part of this, OR whatever changes I might need to make outside of drag-and-drop. Thanks, Scott

1 1

[Maria-discuss] migrate gtid replica to cluster member
by Jeff Dyke 22 May '20

22 May '20

I asked here a while ago in here about my inability to make physical mariabackups viable in a new server, it would eventually fail a restart ( i had a test that failed that led me to look into this). This was in one AWS environment(VPC). In the end there were no disk problems, no corrupt tables, no read issues with aria or innodbcheck as well as an online check with mysqlcheck. And as i said in the earlier email, it works perfect in staging. Some of you may remember that. Anyway, to my satisfaction, i have solved that problem, and its more scorched earth solution than anything, happy to elaborate after. No I have two very stable slaves set in strict gtid mode and I want to add them to the cluster that i am having an issue with, eventually retiring old nodes. I have brought up new cluster nodes on so many occasions, but never transitioned from a replica and i don't trust the output of the current cluster SSTs, but it may work now, with my new setups. I'll test that and ask this at the same time. I can layout a base plan for what i would do, but i'm asking for folks that have had to deal with this to compare my notes with. - All servers in the same VPC, spread across AZs, all IAM roles/policies fully in place. - These are mariadb/galera nodes, not members of an RDS cluster. I had needs that RDS didn't have when i built out this layout, in case you're curious or want to say move to RDS. Thanks if you have pointers. This is all mariadb 10.4.12/13. If i can tie this one up, i can release a bunch of simple set of bash scripts but make it safe to run on clusters, regardless if you're testing or provisioning, even as a pipiline test. Thanks again,

1 0

[Maria-discuss] Connector/C Types and Definitions vs Data Types in MariaDB
by Jogchum Reitsma 18 May '20

18 May '20

Hi, As a little learning project I want to program a test case to insert some rows in a table, using MariaDB Connector/C API Prepared Statement . <https://mariadb.com/kb/en/mariadb-connectorc-api-prepared-statement-functio…> That table has column definitions adhering to the MariaDB Data Types, as described in https://mariadb.com/kb/en/data-types/ Following the example given in https://mariadb.com/kb/en/bulk-insert-row-wise-binding/, I want to set the buffer and buffer_type values of the MSQL_BIND struct. But I'm somewhat at a loss here, because the before mentioned datatypes described in https://mariadb.com/kb/en/data-types/ do not always match with the Connector/C Types and Definitions given in https://mariadb.com/kb/en/connectorc-types-and-definitions/ For example, the latter has MYSQL_TYPE_INT24, which is not present in the former. Field types are defined in mariadb_com.h, but the size and the value ranges are not given there, nor at https://mariadb.com/kb/en/connectorc-types-and-definitions/ Hence, especially for the types present in only the list in Connector/C Types and Definitions, I don't know their size and value, and how to connect them to he gcc types. Anyone here who can guide me on this? cheers, Jogchum

1 0

Re: [Maria-discuss] Mariadb 10.3 crashing continuously on Centos 8
by Ralf Hartings 18 May '20

18 May '20

Hi again, Here are the more detailed files and info regarding your questions. The attachments contain the non-truncated output from the systemctl and the journalctl commands. The attachment 2020-05-08..... contains the content of the my.cnf files. It looks like no special options were given here, all is pretty standard - as I never changed anything in these files. db At least not as I am aware of, since I installed mariadb last year and no problems sinces yesterday... Further to your question on the repo, I am using the CENTOS8 packages, version 10.3 : > > [root@server1 Documents]# rpm -qa | grep maria > mariadb-server-utils-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 > mariadb-backup-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 > mariadb-connector-c-3.0.7-1.el8.x86_64 > mariadb-gssapi-server-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 > mariadb-connector-c-config-3.0.7-1.el8.noarch > mariadb-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 > mariadb-errmsg-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 > mariadb-server-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 > mariadb-common-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 > [root@server1 Documents]# > Regarding ulimit, to my knowledge, I have never changed anything here since I installed mariadb.... The only thing I can find on this is the executable at /usr/bin/ulimit As said, my biggest question and concern is: how could this suddenly happen yesterday, without me doing any changes/updates in the server in the last 2 weeks? I am very grateful for any comments/hints to solve this. Could a forced re-installl of the above packages help to put everything back to"standard"? /Ralf On Sunday 17/05/2020 at 16:15, Gordan Bobic wrote: > > There are several obvious issues in what you posted, to so > with ulimit. You need to look at your service scripts and make > sure that they set suitable limits for what you are > configuring in my.cnf. > Are you using the CentOS 8 bundled MariaDB 10.3 or the > packages from the MariaDB repositories? > > Your journalctl output seems incomplete. systemctl status > output may also be useful (make sure neither is truncated in > width). > > Comment out all of your tuning options and see if it > starts then. Unless you know _exactly_ what you are doing or > had somebody who _really_ knows what they are doing change > any options other than innodb_buffer_pool_size, you should > probably leave them at defaults. > > > > On Sun, May 17, 2020 at 3:00 PM Ralf Hartings > <ralf(a)hartings.se> wrote: > >> Hi >> >> My up-to-date Wordpress website running with mariadb 10.3 on >> CentOS8 (up >> to date) has been running for a long time without any >> issues. >> Suddenly, yesterday, my server became unreachable and did >> not respond to >> anything. Only power off/on helped to get it to respond >> again, but the >> website is down. >> I did not update the server in the last 2 weeks. No changes >> whatsoever. >> >> The logs show the mariadb server is restarting and crashing >> continuously. >> I switched off the mariadb.service to avoid any possible >> further issues, >> as I run a mailserver on the same machine (which runs just >> fine now). >> >> Please look at my post in the CentOS forum: >> https://forums.centos.org/viewtopic.php?f=54&t=74436&p=313469#p313469 >> The people there are great experts in CentOS, but probably >> no experts in >> mariadb in the same way as you are, and I really would like >> to get my >> site up again ASAP. >> >> Thanks a lot for reading this post and helping me out on >> this! >> >> /Ralf >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~maria-discuss >> Post to : maria-discuss(a)lists.launchpad.net >> Unsubscribe : https://launchpad.net/~maria-discuss >> More help : https://help.launchpad.net/ListHelp >> _______________________________________________ > Mailing list: https://launchpad.net/~maria-discuss > Post to : maria-discuss(a)lists.launchpad.net > Unsubscribe : https://launchpad.net/~maria-discuss > More help : https://help.launchpad.net/ListHelp > >

1 0