January 2025 - discuss - lists.mariadb.org

Are default_m and ef_search "implementation specific" vector store parameters?
by Vishal Rao 30 Jan '25

30 Jan '25

Hello, I'm replacing the use of Chroma with MariaDB as the vector store and the Chroma code sets the ef_search parameter to a value of 50. My question is, to achieve "similar results" with the MariaDB vector store will setting ef_search to 50 here as well have the intended effect? Or is there no relation between the actual values across implementations and I need to experiment/test to observe how MariaDB performs to arrive at an appropriate value for it? Thank you. -- "The World is a book, and those who do not travel read only a page." - St. Augustine.

2 2

Set vector ef_search value in CREATE TABLE statement?
by Vishal Rao 30 Jan '25

30 Jan '25

Hello! The mariadb vector 11.7.1-rc release has the option to specify default_m in the CREATE TABLE statement VECTOR specification by including "M=x" option but apparently no option to specify the ef_search value. Is there any intent to add this option to the CREATE TABLE statement on the roadmap - I hope this is a valid way to set the ef_search value per table? Currently I saw this comment here : https://jira.mariadb.org/browse/MDEV-35244?focusedCommentId=293664&page=com… which I can use as a workaround to set session value of ef_search for my needs but wanted to know if I can open a Jira wishlist ticket unless this is already planned? Thanks! -- "The World is a book, and those who do not travel read only a page." - St. Augustine.

3 4

Incorrect CN Being Reported When Using Postfix With MariaDB
by duluxoz 24 Jan '25

24 Jan '25

Hi All, I'm not sure if this is was Postfix issue, a TLS Certificate issue, and/or a MariaDB issue, so I started in the Postfix mailing lists. Their reply (below) indicated that I should post here instead - apologises if this is not the right place. My original post: I'm using a MariaDB backend to Postfix. Everything is working correctly until I attempt to secure the Postfix<->MariaDB connection with a TLS Certificate. When I perform a `postmap -q example.com mysql:/etc/postfix/virtual_domains.cf` command on the postfix server *without* using TLS I get a successful response. However, when I engage TLS I get the following error in the MariaDB log: `X509 subject mismatch: should be 'CN=mail_user(a)example.com' but is '/CN=mail_user(a)example.com'`. Now, obviously the issue is the extra '/' at the start of the 'CN=', but for the life of me I can't figure out where that '/' is coming from. It is *not* in the TLS Certificate (verified by OpenSSL). It is *not* in the virtual_domains.cf file (see below). It is *not* in the MariaDB 'GRANT' statement used to allow access to the database: `GRANT SELECT ON mail_server.* TO 'mail_user'@'example.com' IDENTIFIED BY '{PASWORD OBSCURED}' REQUIRE SUBJECT 'CN=mail_user(a)example.com'`. OS of both servers: Rocky Linux 9.5 Postfix Version: 3.9.1 MariaDB Version: 11.6.2 virtual_domains.cf: ~~~ hosts = mariadb.example.com dbname = mail_server user = mail_user password = {PASWORD OBSCURED} tls_cert_file = /etc/pki/tls/certs/mail_user(a)exampl.com.crt tls_key_file = /etc/pki/tls/certs/mail_user(a)exampl.com.key tls_CApath = /etc/pki/tls/certs/root_ca.crt query = SELECT TRUE FROM virtual_domains WHERE domain_name='%s' ~~~ The Postfix mailing List Reply: There is (of course if happens to know too much about X.509 naming) no such "slash" in the actual certificate. The subject DN is a sequence of relative distinguished names (RDNs) of which CN=... is in this case the first element. There are many ways to write the sequence as a string, the two most popular are: /RDN1/RDN2/.../RDNx RDN1, RDN2, ..., RNDx It looks you have a buggy MariaDB library that expects to get DNs in the second format, but ends up with the first, because of a failure to be specific about the format, or just outright getting it wrong... Perhaps the default changed between OpenSSL 1.1.1 and 3.0, or something about the way OpenSSL was built? Anyway, Postfix is just the messenger, it is the MariaDB library that sets up TLS connection. Could someone please point me in the right direction to get this sorted - thanks Cheers Dulux-Oz

2 2

galera | mariabackup SST fails with Database page corruption detected
by sacawulu 21 Jan '25

21 Jan '25

Hi, Short outline: I am testing backup restores in a 3-node galera cluster used for zabbix from backups made with mariabackup. Everything is running virtualized under virtualbox/almalinux9, mariadb version 10.11 on XFS, wsrep_sst_method = mariabackup We have a FULL mariabackup from a few days ago and an INCREMENTAL backup from today, both including --galera-info. Steps taken: - made sure mariadb was shutdown on all nodes - extract and prepare the full backup - applied the incremental to the full - prepared again (which is not neccesary, I think..?) No errors, all finished as expected - set correct permissions, including selinux context - moved (manually) the result back into <datadir> on one node - bootstrapped galera_new_cluster this node This all worked, no errors. Then on one of the two remaining nodes: - emptied <datadir> - systemctl start mariadb This fails, with logging on the donor: > [01] 2025-01-17 11:59:24 Streaming ./acc_zabbix/valuemap.ibd > [01] 2025-01-17 11:59:24 ...done > [01] 2025-01-17 11:59:24 Streaming ./acc_zabbix/items.ibd > [01] 2025-01-17 11:59:24 Database page corruption detected at page 1532, retrying... > [01] 2025-01-17 11:59:24 Database page corruption detected at page 1532, retrying... > [01] 2025-01-17 11:59:24 Database page corruption detected at page 1532, retrying... > [01] 2025-01-17 11:59:24 Database page corruption detected at page 1532, retrying... > [01] 2025-01-17 11:59:24 Database page corruption detected at page 1532, retrying... > [01] 2025-01-17 11:59:24 Database page corruption detected at page 1532, retrying... > [01] 2025-01-17 11:59:25 Database page corruption detected at page 1532, retrying... > [01] 2025-01-17 11:59:25 Database page corruption detected at page 1532, retrying... > [01] 2025-01-17 11:59:25 Database page corruption detected at page 1532, retrying... > [01] 2025-01-17 11:59:25 Error: failed to read page after 10 retries. File ./acc_zabbix/items.ibd seems to be corrupted. > len 16384; hex 6a88faf1cd270aa737902c6aac0bc8ff4cfef39f4c2ee1fe9a957bac05ac642a78e50468b09ea5d65b58fea9a708ed5c22ec10b0ccf46c0e7f2bdf86d2667c22c1902483c0a34607baab109d01635f4687bf5fddc8f2d7b6723813825b630a8315675e78b4b8d0336a4ad66e867e878690e092286bc3ba8259dbb21475b45198d20dc33488b8a3e407a91557c0a77598bf6cd2a81da3388c8d629466ffdf258a3d3e837d9f4cb54a13847495b64d616b801cdd237c1af0f52b9ace7fbc37601a7b5da5264a5478d926c0e50554f811b6d2586288c2b7df74ce5a3b0e9f2f6546846ffe9890fb21b19e23703f1e243c9d67514bcee9685be15dea8afc6c018290731dc517c894394ff72e1a913b6a197d422dadaed06d968abc8e784f9347b2ffd79fcbdee20c7a566ab8374c7ed4fa78977cf0fc10ae402900676b5c3b6a427a26a987743ccdf3d93b32d3a4544c5ba9f4bfa50f910765e5349f605cad4c874061aa9f3339870ef745e7e40d1 So on the donor I ran: > mariadb-check --all-databases All OK, no errors. Then on the doner I ran > mysqldump --all-databases > /tmp/alldb.sql also works, and /tmp/alldb.sql looks healthy, ending with -- Dump completed on 2025-01-17 12:06:40 And then, just for fun, I tried to create a fresh mariabackup from this restored database on donor, and yes, it fails with the same error that items.ibd seems to be corrupted. Then I changed wsrep_sst_method to rsync, and attempted to start the other two nodes: the SST worked, nodes came online, DB/galera came up healthy: zabbix is now running. Just for fun I also tried making a mariaback on one of the other (now syned) galera nodes, and it fails also, but on a different table: > [01] 2025-01-17 12:34:48 Database page corruption detected at page 363, retrying... > [02] 2025-01-17 12:34:48 Database page corruption detected at page 643, retrying... > [01] 2025-01-17 12:34:48 Database page corruption detected at page 363, retrying... > [02] 2025-01-17 12:34:48 Database page corruption detected at page 643, retrying... > [01] 2025-01-17 12:34:48 Error: failed to read page after 10 retries. File ./acc_zabbix/auditlog.ibd seems to be corrupted. So I'm looking for feedback here: what is happening? IS my db corrupted, or NOT? How to better check? Why would mariadb-check, mysqldump, plus zabbix all work, but can I no longer run mariabackup. Is there something wrong/missing in the procedure outlined above? Are there better ways to check integrity? Luckily this is all testing, and I'm just trying to understand things better. :-) Ending with the complete output of mariabackup errors, as perhaps it means something to someone..? Thanks! MJ > [02] 2025-01-17 12:21:29 Streaming ./acc_zabbix/changelog.ibd > [01] 2025-01-17 12:21:29 Database page corruption detected at page 363, retrying... > [01] 2025-01-17 12:21:30 Database page corruption detected at page 363, retrying... > [02] 2025-01-17 12:21:30 Database page corruption detected at page 643, retrying... > [01] 2025-01-17 12:21:30 Database page corruption detected at page 363, retrying... > [02] 2025-01-17 12:21:30 Database page corruption detected at page 643, retrying... > [01] 2025-01-17 12:21:30 Database page corruption detected at page 363, retrying... > [02] 2025-01-17 12:21:30 Database page corruption detected at page 643, retrying... > [01] 2025-01-17 12:21:30 Database page corruption detected at page 363, retrying... > [02] 2025-01-17 12:21:30 Database page corruption detected at page 643, retrying... > [01] 2025-01-17 12:21:30 Database page corruption detected at page 363, retrying... > [02] 2025-01-17 12:21:30 Database page corruption detected at page 643, retrying... > [01] 2025-01-17 12:21:30 Database page corruption detected at page 363, retrying... > [02] 2025-01-17 12:21:30 Database page corruption detected at page 643, retrying... > [01] 2025-01-17 12:21:30 Database page corruption detected at page 363, retrying... > [02] 2025-01-17 12:21:30 Database page corruption detected at page 643, retrying... > [01] 2025-01-17 12:21:30 Error: failed to read page after 10 retries. File ./acc_zabbix/auditlog.ibd seems to be corrupted. > len 16384; hex 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000[02] 2025-01-17 12:21:30 Database page corruption detected at page 643, retrying... > 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000616c2d76616375756d3a2072656e616d652066756e6374696f6e20746f206d6174636820737472756374206e616d6520282332313832363332290a2d206a6f75726e616c2d76616375756d3a2075736520434c45414e55505f415252415920282332313832363332290a2d2070616d3a206164642063616c6c20746f2070616d5f756d61736b20282332323130313435290a2d20756465762d6275696c74696e2d6e65745f69643a20616c69676e20564620726570726573656e746f72206e616d65732077697468205646206e616d657320282332323138383836290a2d2070616d3a2061646420612063616c6c20746f2070616d5f6e616d65737061636520282332323138313834290a2d2072756c65733a206f6e6c696e6520435055206175746f6d61746963616c6c79206f6e2049424d20733339307820706c6174666f726d73207768656e20636f6e6669677572656420282332323132363132290a2d20636f72652f6d6f756e743a2065736361706520696e76616c69642055544638206368617220696e2064627573207265706c7920282332323038323430290a2d205265766572742022757365723a2064656c65676174652063707520636f6e74726f6c6c65722c2061737369676e207765696768747320746f207573657220736c696365732220282332313736383939290a2d20756465762d72756c65733a20666978206e766d652073796d6c696e6b206372656174696f6e206f6e206e616d657370616365206368616e67657320282332313732353039290a2d2072756c65733a20616464207768697465737061636520616674657220636f6d6d61206265666f726520746865206c696e6520636f6e74696e756174696f6e20282332313732353039290a2d20756465763a20726573746f726520636f6d7061742073796d6c696e6b20666f72206e766d65206465766963657320282332313732353039290a2d2072756c65733a2064726f7020646f75626c656420737061636520282332313732353039290a2d206d616e616765723a20646f6e2774207461696e742074686520686f7374206966206367726f757073207631206973207573656420282332313933343536290a2d20636f72652f00003895000000002840c66b57bff3333e9bd34a3f62511e00003896736572766963653a207768656e20726573657474696e672050494420616c736f207265736574206b6e6f776e20666c616720282332323130323337290a2d2063693a2064726f702073797374656d642d737461626c652066726f6d20616476616e6365642d636f6d6d69742d6c696e74657220636f6e6669672028233231373038383329002d2063693a20747269676765722060646966666572656e7469616c2d7368656c6c636865636b6020776f726b666c6f77206f6e207075736820282332313030343430290a2d2063693a20776f726b666c6f7720666f7220676174686572696e67206d6574616461746120666f7220736f757263652d676974206175746f6d6174696f6e20282332313030343430290a2d2063693a2066697273742070617274206f662074686520736f757263652d676974206175746f6d6174696f6e202d20636f6d6d6974206c696e74657220282332313030343430290a2d206369284d657267696679293a20636865636b20436f6465514c20616e64206275696c6420776f726b666c6f7773206261736564206f6e206368616e6765642066696c657320282332313030343430290a2d2063693a20616464204e4f5449434520746f20616c736f207570646174652072656765787020696e20602e6d6572676966792e796d6c60207768656e207570646174696e6720607061746873602070726f706572747920282332313030343430290a2d20537570706f7274202f6574632f73797374656d2d75706461746520666f72204f53547265652073797374656d7320282332323033313333290a2d206a6f75726e616c2d6465663a206669782074797065206f66207369676e617475726520746f206d61746368207468652061637475616c206669656c6420696e20746865204865616465722073747275637475726520282332313833353436290a2d206a6f75726e616c3a2075736520636f6d706f756e6420696e697469616c697a6174696f6e20666f72206a6f75726e616c2066696c65204865616465722073747275637475726520282332313833353436290a2d206a6f75726e616c643a20666978206c6f67206d65737361676520282332313833353436290a2d2073642d6a6f75726e616c3a20636163686520726573756c7473206f662070617273696e6720656e7669726f6e6d656e74207661726961626c657320282332313833353436290a2d20636f6d70726573733a20696e74726f6475636520636f6d7072657373696f6e5f737570706f7274656428292068656c7065722066756e6374696f6e20282332313833353436290a2d2073642d6a6f75726e616c3a20616c77617973207573652074686520636f6d7072657373696f6e20616c676f726974686d2073706563696669656420696e207468652068656164657220282332313833353436290a2d2073642d6a6f75726e616c3a20616c6c6f7720746f207370656369667920636f6d7072657373696f6e20616c676f726974686d207468726f75676820656e7620282332313833353436290a2d20746573743a20616464207465737420636173652074686174206a6f75726e616c2066696c6520697320637265617465642077697468207468652072657175657374656420636f6d7072657373696f6e20616c676f726974686d20282332313833353436290a2d2072756c65733a20646f206e6f74206f6e6c696e6520435055206175746f6d61746963616c6c79206f6e2049424d20706c6174666f726d732028233231343331303729002d2073797374656d643a20537570706f7274204f4f4d506f6c69637920696e2073636f706520756e69747320282332313736393138290a2d2073797374656d643a2044656661756c7420746f204f4f4d506f6c6963793d636f6e74696e756520666f72206c6f67696e2073657373696f6e2073636f70657320282332313736393138290a2d206d616e3a207265776f726b206465736372697074696f6e206f66204f4f4d506f6c6963793d20612062697420282332313736393138290a2d20636f72652c6d616e3a20616464206d697373696e6720696e746567726174696f6e206f66204f4f4d506f6c6963793d20696e2073636f70657320282332313736393138290a2d206d65736f6e3a2053746f72652066757a7a20746573747320696e20737472756374757265642077617920282332313736393138290a2d206d65736f6e3a2047656e65726174652066757a7a657220696e707574732077697468206469726563746976657320282332313736393138290a2d206f73732d66757a7a3a20696e636c7564652067656e65726174656420636f72706f726120696e207468652066696e616c207a69702066696c6520282332313736393138290a2d20756e69743a20496e206367726f757076312c20677261636566756c6c79207465726d696e6174652064656c6567617465642073636f70657320616761696e2028233231383031323029002d206a6f75726e616c2d66696c653a204669782072657475726e2076616c756520696e2062756d705f656e7472795f617272617928292028233231373336383229002d20746573743a2061646420636f76657261676520666f722023323431373720282331393835323838290a2d206c6f67696e642d73657373696f6e3a206d616b652073746f7070696e67206f662069646c652073657373696f6e2076697369626c6520746f2061646d696e732028233231373234303129002d206a6f75726e616c63746c3a2061637475616c6c792072756e20746865207374617469632064657374727563746f727320282332313232353030290a2d206566693a2064726f702065786563757461626c652d737461636b206269742066726f6d202e656c662066696c6520282332313430363436290a2d20696e7374616c6c3a206661696c206561726c792069662073706563696669657220657870616e73696f6e206661696c656420282332313338303831290a2d20746573743a2061646420636f76657261676520666f72202332363436372028233231333830383129002d206e73732d6d79686f73746e616d653a2066697820696e76657274656420636f6e646974696f6e20696e20282332313637343638290a2d206e73732d6d79686f73746e616d653a20646f206e6f742072657475726e20656d70747920726573756c742077697468204e53535f5354415455535f5355434345535320282332313637343638290a2d20736c6565703a2072656e616d652068696265726e6174655f64656c61795f736563202d3e205f7573656320282332313531363132290a2d20736c6565703a2066657463685f6261747465726965735f63617061636974795f62795f6e616d65282920646f6573206e6f742072657475726e202d454e4f454e5420282332313531363132290a2d20736c6565703a2064726f7020756e6e65636573736172792074656d706f72616c2076616961626c6520616e6420696e697469616c697a6174696f6e20282332313531363132290a2d20736c6565703a20696e74726f647563652053757370656e64457374696d6174696f6e5365633d20282332313531363132290a2d20736c6565703a20636f64696e67207374796c65206669786c65747320282332313531363132290a2d20736c6565703a2073696d706c69667920636f646520612062697420282332313531363132290a2d20736c6565703a2066697820696e64656e746174696f6e20282332313531363132290a2d20736c6565703a20656e756d6572617465206f6e6c79206578697374696e6720616e64206e6f6e2d6465766963652062617474657269657320282332313531363132290a2d20636f72653a207768656e2069736f6c6174696e6720746f206120756e69742c20616c736f206b65657020756e6974732072756e6e696e672074686174206172652074726967676572656420627920756e697473207765206b6565702072756e6e696e6720282331393532333738290a2d20756465762f6e65745f69643a20696e74726f64756365206e616d696e6720736368656d6520666f72205248454c2d392e322028233231373035303029002d20756465763a206d616b65206765745f76697274666e5f696e666f28292070726f7669646520706879736963616c205043492064657669636520282332313539343438290a2d20746573743a206d616b652068656c7065725f636865636b5f6465766963655f756e6974732829206c6f6720756e6974206e616d6520282332313338303831290a2d20746573743a20616464206120746573746361736520666f72206c76657874656e6420282332313338303831290a2d20706964313a206669782073656776207472696767657265642062792073746174757320717565727920282332363237392920282332313338303831290a2d20746573743a2063726561746520636f6e66696720756e646572202f72756e20282332313338303831290a2d20746573743a2061646420746573747320666f72206d444e5320616e64204c4c4d4e522073657474696e677320282332313338303831290a2d207265736f6c7665643a20696e74726f6475636520746865205f6c6f63616c646e737374756220616e64205f6c6f63616c646e7370726f7879207370656369616c20686f73746e616d657320666f72203132372e302e302e3534202b203132372e302e302e353320282332313338303831290a2d20746573743a207761697420666f7220746865206d6f6e69746f72696e67207365727669636520746f206265636f6d652061637469766520282332313338303831290a2d20746573743a207375707072657373206563686f20696e206d6f6e69746f725f636865636b5f7272282920282332313338303831290a2d205265766572742022746573743a207761697420666f7220746865206d6f6e69746f72696e67207365727669636520746f206265636f6d65206163746976652220282332313338303831290a2d20746573743a2073686f7720616e6420636865636b20616c6d6f737420616c6c206a6f75726e61[02] 2025-01-17 12:21:30 Database page corruption detected at page 643, retrying... > 6c20656e74726965732073696e6365207468652072656c6576616e7420636f6d6d616e64206265696e6720696e766f6b656420282332313338303831290a2d20746573743a20636f766572204950763620696e20746865207265736f6c766564207465737420737569746520282332313338303831290a2d20746573743a20616464206120636f75706c65206f6620535256207265636f72647320746f20636865636b2073657276696365207265736f6c7574696f6e20282332313338303831290a2d20746573743a206164642061207465737420666f7220746865204f50454e5047504b455920525220282332313338303831290a2d20746573743a20646f6e27742068616e6720696e646566696e6974656c79206f6e206e6f206d6174636820282332313338303831290a2d20746573742d6e646973633a20666978206d656d6c65616b20616e64206664206c65616b20282332313338303831290a2d20746573742d756e69742d6e616d653a20666978206664206c65616b20282332313338303831290a2d20746573743a2062756d7020442d4275732000003896000000002840c66b57bff333acadea911ad4b23300003897736572766963652073746172742074696d656f75742069662077652072756e20776974686f757420616363656c20282332313338303831290a2d20746573743a2062756d702074686520636c69656e742d736964652074696d656f757420696e2073642d6275732061732077656c6c20282332313338303831290a2d20746573743a2062756d702074686520636f6e7461696e657220737061776e2074696d656f757420746f2036307320282332313338303831290a2d206e6574776f726b3a20666978206d656d6c65616b20282332313338303831290a2d2062757363746c3a2066697820696e74726f7370656374696e6720444275732070726f7065727469657320282332313338303831290a2d2062757363746c3a2073696d706c696679207065656b696e6720746865207479706520282332313338303831290a2d207265736f6c76653a2064726f7020726564756e64616e742063616c6c206f6620736f636b65745f697076365f69735f737570706f72746564282920282332313338303831290a2d207265736f6c76653a20696e74726f64756365206c696e6b5f6765745f6c6c6d6e725f737570706f7274282920616e64206c696e6b5f6765745f6d646e735f737570706f7274282920282332313338303831290a2d207265736f6c76653a2070726f766964652065666665637469766520737570706f7274696e67206c6576656c73206f66206d444e5320616e64204c4c4d4e5220282332313338303831290a2d207265736f6c766563746c3a207761726e2069662074686520676c6f62616c206d444e53206f72204c4c4d4e5220737570706f7274206c6576656c206973206c6f776572207468616e2074686520726571756573746564206f6e6520282332313338303831290a2d207265736f6c76653a20656e61626c65207065722d6c696e6b206d444e532073657474696e672062792064656661756c742028233231333830383129002d20737761703a2074656c6c20737761706f6e20746f207265696e697469616c697a652073776170206966206e656564656420282332313531393933290a2d20636f726564756d703a2061646a757374207768697465737061636520282332313535353137290a2d20636f726564756d703a20646f206e6f7420616c6c6f77207573657220746f2061636365737320636f726564756d70732077697468206368616e676564207569642f6769642f6361706162696c697469657320282332313535353137290a2d20526576657274202262617369633a206164642066616c6c6261636b20696e2063686173655f73796d6c696e6b735f616e645f6f70656e646972282920666f72206361736573207768656e202f70726f63206973206e6f74206d6f756e7465642220282332313338303831290a2d20676c7970682d7574696c3a20616464207761726e696e67207369676e207370656369616c20676c79706820282332313338303831290a2d2063686173652d73796d6c696e6b3a207768656e20636f6e76657274696e67206469726563746f7279204f5f5041544820666420746f207265616c2066642c20646f6e277420626f746865722077697468202f70726f632f20282332313338303831290a2d2073797374656d63746c3a207072696e74206120636c656172207761726e696e672069662070656f706c6520696e766f6b652073797374656d63746c20776974686f7574202f70726f632f20282332313338303831290a2d20544553542d36353a20636865636b206361742d636f6e666967206f7065726174696f6e20696e206368726f6f7420282332313338303831290a2d20544553542d36353a20757365205b5b202d76205d5d206d6f726520282332313338303831290a2d2073797374656d63746c3a207761726e20696620747279696e6720746f2064697361626c65206120756e69742077697468206e6f20696e7374616c6c20696e666f20282332313431393739290a2d2073797374656d63746c3a20616c6c6f7720737570707265737320746865207761726e696e67206f66206e6f20696e7374616c6c20696e666f207573696e67202d2d6e6f2d7761726e20282332313431393739290a2d2072706d2f73797374656d642d7570646174652d68656c7065723a20757365202d2d6e6f2d7761726e207768656e2064697361626c696e6720756e69747320282332313431393739290a2d2073797374656d63746c3a207375707072657373207761726e696e672061626f7574206d697373696e67202f70726f632f207768656e202d2d6e6f2d7761726e20282332313431393739290a2d207368656c6c2d636f6d706c6574696f6e3a2073797374656d63746c3a20616464202d2d6e6f2d7761726e20282332313431393739290a2d20636f72652f756e69743a2064726f7020646f75626c656420656d707479206c696e6520282332313630343737290a2d20636f72652f756e69743a2064726f7020646570656e64656e637920746f2074686520756e6974206265696e67206d657267656420282332313630343737290a2d20636f72652f756e69743a20666978206c6f676963206f662064726f7070696e672073656c662d7265666572656e63696e6720646570656e64656e6369657320282332313630343737290a2d20636f72652f756e69743a206d657267652074776f206c6f6f707320696e746f206f6e6520282332313630343737290a2d20746573743a206164642074657374206361736520666f7220737973762d67656e657261746f7220616e6420696e76616c696420646570656e64656e637920282332313630343737290a2d20636f72652f756e69743a206d6572676520756e6974206e616d6573206166746572206d657267696e67206465707320282332313630343737290a2d20636f72652f756e69743a20666978206c6f67206d65737361676520282332313630343737290a2d20746573743a206578706c696369746c792063726561746520746865202f6574632f696e69742e64206469726563746f727920282332313630343737290a2d20746573743a20737570706f72742061206e6f6e2d64656661756c742053797356206469726563746f72792028233231363034373729002d20746573743a20636865636b2069662077652063616e207573652053484131204d4420666f72207369676e696e67206265666f7265207573696e6720697420282332313431393739290a2d20626f6f743a20636c65616e75707320666f72206566697661725f676574282920616e6420667269656e647320282332313431393739290a2d20626f6f743a206669782066616c7365206d617962652d756e696e697469616c697a6564207761726e696e6720282332313431393739290a2d20747265652d776964653a206d6f6465726e697a6174696f6e732077697468205245545f4e4552524e4f282920282332313337353834290a2d2073642d6275733a2068616e646c65202d45494e54522072657475726e2066726f6d206275735f706f6c6c282920282332313337353834290a2d20737464696f2d6272696467653a20646f6e277420626520626f74686572656420776974682045494e545220282332313337353834290a2d207661726c696e6b3a20616c736f2068616e646c652045494e545220677261636566756c6c79207768656e2077616974696e6720666f722045494f207669612070706f6c6c282920282332313337353834290a2d2073642d6e65746c696e6b3a2068616e646c652045494e54522066726f6d20706f6c6c282920677261636566756c6c792c206173207375636365737320282332313337353834290a2d207265736f6c7665643a2068616e646c65202d45494e54522072657475726e65642066726f6d2066645f776169745f666f725f6576656e7428292062657474657220282332313337353834290a2d20686f6d65643a2068616e646c652045494e545220677261636566756c6c79207768656e2077616974696e6720666f7220646576696365206e6f646520282332313337353834290a2d2075746d702d77746d703a20666978206572726f7220696e2063617365206973617474792829206661696c7320282332313337353834290a2d2075746d702d77746d703a2068616e646c652045494e545220677261636566756c6c79207768656e2077616974696e6720746f20777269746520746f2074747920282332313337353834290a2d20696f2d7574696c3a20646f63756d656e742045494e545220736974756174696f6e20612062697420282332313337353834290a2d207465726d696e616c2d7574696c3a20536574204f504f5354207768656e2073657474696e67204f4e4c435220282332313338303831290a2d206367746f703a20446f206e6f742072657772697465202d50206f72202d6b206f7074696f6e73202823; asc al-vacuum: rename function to match struct name (#2182632) - journal-vacuum: use CLEANUP_ARRAY (#2182632) - pam: add call to pam_umask (#2210145) - udev-builtin-net_id: align VF representor names with VF names (#2218886) - pam: add a call to pam_namespace (#2218184) - rules: online CPU automatically on IBM s390x platforms when configured (#2212612) - core/mount: escape invalid UTF8 char in dbus reply (#2208240) - Revert "user: delegate cpu controller, assign weights to user slices" (#2176899) - udev-rules: fix nvme symlink creation on namespace changes (#2172509) - rules: add whitespace after comma before the line continuation (#2172509) - udev: restore compat symlink for nvme devices (#2172509) - rules: drop doubled space (#2172509) - manager: don't taint the host if cgroups v1 is used (#2193456) - core/ 8 (@ kW 3> J?bQ 8 service: when resetting PID also reset known flag (#2210237) - ci: drop systemd-stable from advanced-commit-linter config (#2170883) - ci: trigger `differential-shellcheck` workflow on push (#2100440) - ci: workflow for gathering metadata for source-git automation (#2100440) - ci: first part of the source-git automation - commit linter (#2100440) - ci(Mergify): check CodeQL and build workflows based on changed files (#2100440) - ci: add NOTICE to also update regexp in `.mergify.yml` when updating `paths` property (#2100440) - Support /etc/system-update for OSTree[02] 2025-01-17 12:21:31 Error: failed to read page after 10 retries. File ./acc_zabbix/changelog.ibd seems to be corrupted. > len 16384; hex 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 systems (#2203133) - journal-def: fix type of signature to match the actual field in the Header structure (#2183546) - journal: use compound initialization for journal file Header structure (#2183546) - journald: fix log message (#2183546) - sd-journal: cache results of parsing environment variables (#2183546) - compress: introduce compression_supported() helper function (#2183546) - sd-journal: always use the compression algorithm specified in the header (#2183546) - sd-journal: allow to specify compression algorithm through env (#2183546) - test: add test case that journal file is created with the requested compression algorithm (#2183546) - rules: do not online CPU automatically on IBM platforms (#2143107) - systemd: Support OOMPolicy in scope units (#2176918) - systemd: Default to OOMPolicy=continue for login session scopes (#2176918) - man: rework description of OOMPolicy= a bit (#2176918) - core,man: add missing integration of OOMPolicy= in scopes (#2176918) - meson: Store fuzz tests in structured way (#2176918) - meson: Generate fuzzer inputs with directives (#2176918) - oss-fuzz: include generated corpora in t0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000he final zip file (#2176918) - unit: In cgroupv1, gracefully terminate delegated scopes again (#2180120) - journal-file: Fix return value in000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 bump_entry_array() (#2173682) - test: add coverage for #24177 (#1985288) - logind-session: make stopping of idle session visible to admins (#2172401) - journalctl: actually run the static destructors (#2122500) - efi: drop executable-stack bit from .elf file (#2140646) - install: fail early if specifier expansion failed (#2138081) - test: add coverage for #26467 (#2138081) - nss-myhostname: fix inverted condition in (#2167468) - nss-myhostname: do not return empty result with NSS_STATUS_SUCCESS (#2167468) - sleep: rename hibernate_delay_sec -> _usec (#2151612) - sleep: fetch_batteries_capacity_by_name() does not return -ENOENT (#2151612) - sleep: drop unnecessary temporal vaiable and initialization (#2151612) - sleep: introduce SuspendEstimationSec= (#2151612) - sleep: coding style fixlets (#2151612) - sleep: simplify code a bit (#2151612) - sleep: fix indentation (#2151612) - sleep: enumerate only existing and non-device batteries (#2151612) - core: when isolating to a unit, al0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000so keep units running that are triggered by units we keep running (#1952378) - udev/net_id: introduce naming scheme for RHEL-9.2 (#2170500) - udev: make get_virtfn_info() provide physical PCI device (#2159448) - test: make helper_check_device_units() log unit name (#2138081) - test: add a testcase for lvextend (#2138081) - pid1: fix segv triggered by status query (#26279) (#2138081) - test: create config under /run (#2138081) - test: add tests for mDNS and LLMNR settings (#2138081) - resolved: introduce the _localdnsstub and _localdnsproxy special hostnames for 127.0.0.54 + 127.0.0.53 (#2138081) - test: wait for the monitoring service to become active (#2138081) - test: suppress echo in monitor_check_rr() (#2138081) - Revert "test: wait for the monitoring service to become active" (#2138081) - test: show and check almost all journal entries since the relevant command being invoked (#2138081) - test: cover IPv6 in the resolved test suite (#2138081) - test: add a couple of SRV records to check service resolution (#2138081) - test: add a test for the OPENPGPKEY RR (#2138081) - test: don't hang indefinite000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000ly on no match (#2138081) - test-ndisc: fix memleak and fd leak (#2138081) - test-unit-name: fix fd leak (#2138081) - test: bump D-Bus 8 (@ kW 3 3 8 service start timeout if we run without accel (#2138081) - test: bump the client-side timeout in sd-bus as well (#2138081) - test: bump the container spawn timeout to 60s (#2138081) - network: fix memleak (#2138081) - busctl: fix introspecting DBus properties (#2138081) - busctl: simplify peeking the type (#2138081) - resolve: drop redundant call of socket_ipv6_is_supported() (#2138081) - resolve: introduce link_get_llmnr_support() and link_get_mdns_support() (#2138081) - resolve: provide effective supporting levels of mDNS and LLMNR (#2138081) - resolvectl: warn if the global mDNS or LLMNR support level is lower than the requested one (#2138081) - resolve: enable per-link mDNS setting by default (#2138081) - swap: tell swapon to reinitialize swap if needed (#2151993) - coredump: adjust whitespace (#2155517) - coredump: do not allow user to access 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000coredumps with changed uid/gid/capabilities (#2155517) - Revert "basic: add fallback in chase_symlinks_and_opendir() for cases when /proc is not mounted" (#2138081) - glyph-util: add warning sign special glyph (#2138081) - chase-symlink: when converting directory O_PATH fd to real fd, don't bother with /proc/ (#2138081) - systemctl: print a clear warning if people invoke systemctl without /proc/ (#2138081) - TEST-65: check cat-config operation in chroot (#2138081) - TEST-65: use [[ -v ]] more (#2138081) - systemctl: warn if trying to disable a unit with no install info (#2141979) - systemctl: allow suppress the warning of no install info using --no-warn (#2141979) - rpm/systemd-update-helper: use --no-warn when disabling units (#2141979) - systemctl: suppress warning about missing /proc/ when --no-warn (#2141979) - shell-completion: systemctl: add --no-warn (#2141979) - core/unit: drop doubled empty line (#2160477) - core/unit: drop dependency to the unit being merged (#2160477) - core/unit: fix logic of dropping self-referencing dependencies (#2160477) - core/unit: merge two loops into one (#2160477) - test: add test case for sysv-generator and invalid dependency (#2160477) - core/unit: merge unit names after merging deps (#2160477) - core/unit: fix log message (#2160477) - test: explicitly create the /etc/init.d directory (#200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000160477) - test: support a non-default SysV directory (#2160477) - test: check if we can use SHA1 MD for signing before using it (#2141979) - boot: cleanups for efivar_get() and friends (#2141979) - boot: fix false maybe-uninitialized warning (#2141979) - tree-wide: modernizations with RET_NERRNO() (#2137584) - sd-bus: handle -EINTR return from bus_poll() (#2137584) - stdio-bridge: don't be bothered with EINTR (#2137584) - varlink: also handle EINTR gracefully when waiting for EIO via ppoll() (#2137584) - sd-netlink: handle EINTR from poll() gracefully, as success (#2137584) - resolved: handle -EINTR returned from fd_wait_for_event() better (#2137584) - homed: handle EINTR gracefully when waiting for device node (#2137584) - utmp-wtmp: fix error in case isatty() fails (#2137584) - utmp-wtmp: handle EINTR gracefully when waiting to write to tty (#2137584) - io-util: document EINTR situation a bit (#2137584) - terminal-util: Set OPOST when setting ONLCR (#2138081) - cgtop: Do not rewrite -P or -k options (#;0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000b30089d40803020300b30089d30803020300b30089d20803020300b30089d10803020300b30089d00803020300b30089cf0803020300b30089ce0803020300b30089cd0803020300b30089cc0803020300b30089cb0803020300b30089ca0803020300b30089c90803020300b30089c80803020300b3[01] 2025-01-17 12:21:31 mariabackup: xtrabackup_copy_datafile() failed. > [00] FATAL ERROR: 2025-01-17 12:21:31 failed to copy datafile.

2 1

Which GSSAPI implementation should be used to compile mariadb-connector-c/cpp?
by 张天夫 16 Jan '25

16 Jan '25

I'm trying to compile mariadb-connector-c/cpp on Windows. However, Windows does not provide native GSSAPI. Do I need to look for other implementations? Which is the recommended implementation?

2 1

Inquiry Regarding Parameters of Modified HNSW Algorithm in MariaDB Vector
by kase jojo 13 Jan '25

13 Jan '25

Dear Sir, I hope this message finds you well. I am currently working with the MariaDB vector functionality and am particularly interested in the modified HNSW (MHNSW) algorithm. Specifically, I would like to inquire about the meaning and usage of the parameter "M" in MHNSW, as well as how it compares to other HNSW implementations, such as pgvector. （ https://mariadb.com/kb/en/vector-system-variables/） Typically, HNSW has two key construction parameters: "M" and "efconstruction." However, I noticed that in MHNSW, there doesn't seem to be an "efc" parameter. This has led me to wonder if the "M" parameter in MHNSW has a different meaning or purpose compared to the traditional HNSW "M." Could you kindly clarify the role of the "M" parameter in the modified HNSW algorithm, and how it differs from or is similar to other implementations like pgvector? Thank you for your time and assistance. I look forward to your response. Best regards！

2 1

MariaDb Master/Replica. How to recover replication when reverting Master to an earlier backup?
by Simon Avery 12 Jan '25

12 Jan '25

Hello We have two Mariadb 10.11.10 servers acting as Master and Replica. Both have unique local databases, plus seven that are replicated from Master to Replica with Replicate_Wild_Do_Table: DB1Name.%, DB2Name.% etc The size of the replicated databases is just over 1Tb, with the single largest being almost 500Gb. Both machines are in vmware and on the same network. Yesterday, we hit an issue with the Master which required that vm to be restored to a backup four hours previously. This got Master back in play, but obviously has broken Replication. Traditional wisdom seems to suggest that I need to recreate this replication setup from scratch - ie, stop Master (from changing, ie, close firewall and block clients, flush logs), note the Log Position, and then mysqldump each database. However, due to the size of these databases, that is going to take many hours and we can't accept that downtime for Master. It's occurred to us that we might speed this up by: Stop Master from changing. Note Log Position. Clone Master's vm to Master-Clone. (< 10 minutes) Restart Master. Then we would be at relative leisure to [On Clone] Mysqldump the databases onto a temporary drive. [On Replica] DROP the seven databases. Import the dumped databases from the temporary drive. Update the log position in config and restart the slave user. Then Replica should start syncing from Master again, even if Clone was several days old? Does that sound sensible? These databases have partitions - is that going to cause issues dumping and reimporting them or should I use another method? Any pitfalls? Any alternative ways? Thank you

2 6

Re: Inquiry Regarding Slow Index Creation with MariaDB 11.7 RC (SIFT1M)
by Sergei Golubchik 12 Jan '25

12 Jan '25

Hi, kase, First: please send questions like this to discuss(a)lists.mariadb.org. it's a public mailing list dedicated to MariaDB and how to use it better. I am subscribed, so I'll see you mail there, and you may be sure I will, because it won't be accidentally catched by my spam filter, or sorted out in some obscure folder. Furthermore other subscribers will see your question and could reply if I will be not available (e.g. I could be travelling). Thank you. On Jan 12, kase jojo wrote: > Dear Sir > > I hope you are doing well. I recently read your blog > https://mariadb.com/resources/blog/how-fast-is-mariadb-vector/ and was > particularly impressed by the efficient index-building times demonstrated > in your tests. However, when I attempted similar experiments on MariaDB > 11.7 RC, using the SIFT1M dataset and building an index with M=32, I > noticed that the index creation process was much slower than expected. > > In my case, I have been inserting data into the table gradually, and I > wanted to inquire about the process you mentioned in your blog: "We > build the index slowly as we insert the data row by row." Could you > clarify how this process works? Specifically, I am curious to know if > there are any steps or techniques you followed to ensure such > efficient index construction, as it seems to differ from my > experience. To get faster inserts you need to use a smaller M. Try M=8, for example. It will reduce the recall, and you'll need to increase ef_search to compensate for that. Look at it this way: MariaDB needs to do the work to get good recall. It has to do it *somewhere*. But you can decide where to do it. MariaDB can spend more time doing inserts, build a better index, and search in it quickly. Or it can insert faster, the index will be of worse quality, and it'll need to spend more time searching in it. It's a trade-off and you decide what is more important for your application. See https://github.com/vuvova/ann-benchmarks/blob/dev/ann_benchmarks/algorithms… For faster inserts you can use M=8 and ef_search=800. Of course, always make sure that the mhnsw_max_cache_size is big enough to hold your entire data set. SIFT1M is rather small, 300M should likely be enough. I'd use at least mhnsw_max_cache_size=1G to be safe, it's an upper limit, MariaDB won't use more memory than necessary anyway. Regards, Sergei Chief Architect, MariaDB Server and security(a)mariadb.org

1 0

increasing InnoDB history length and stalls on MariaDB 11.4
by kazuhiko＠nexedi.com 08 Jan '25

08 Jan '25

Hello, Our application has a sustained rate of DML queries in parallel with DQL. We can achieve good performance using innodb-locks-unsafe-for-binlog on MariaDB 10.4, with careful consideration of its 'unsafeness'. But innodb-locks-unsafe-for-binlog is removed in MariaDB 10.5 or later and our application runs much slower without it because of gap locking. https://mariadb.com/docs/server/ref/mdb/cli/mariadbd/innodb-locks-unsafe-fo… To achieve a good performance as before, we now use READ COMMITTED transaction isolation for DML and use REPEATABLE READ isolation for DQL on MariaDB 11.4. This way guarantees the consistency for our application. Our database contains totally 13.7G rows and uses 4.5TB storage. Here is the configuration : innodb_buffer_pool_size = 17179869184 (16GB) innodb_buffer_pool_instances = 16 (no meaning in 11.4) innodb_log_file_size = 134217728 (128MB) innodb_flush_method = O_DIRECT Please see the attached graphs drawing 'InnoDB history length (right axis)' and 'free redo log in % (left axis)' (i.e. 100 - Redo Log Occupancy) while running our reference workload. https://mariadb.com/kb/en/innodb-redo-log/#determining-the-redo-log-occupan… These tests are done with the same workload, but only MariaDB version and/or configuration is different. (Please disregard the 'warehouse history length' and 'activities history length' series in those plots, they are not relevant to the current issue.) On MariaDB 10.4, the performance and the behaviour between 'using innodb-locks-unsafe-for-binlog' and 'using READ COMMITTED and REPEATABLE READ' are similar. But on MariaDB 11.4, I found two serious issues. Issue 1: InnoDB history length keeps growing while running lots of DML and DQL queries in parallel. InnoDB history length is stable around 5k on 10.4, but it keeps growing on 11.4 up to 100k until the end. In our experience, increases in history list length are roughly correlated with poor query performance (causing queries to "step over tombstones" ?), and we do our best to avoid having long-running transactions in order to allow older snapshots to be freed ASAP. We are satisfied with the status on 10.4, where history list is constant. What is the reason behind such increases on 11.4 and is there any configuration to avoid such ? Issue 2: MariaDB stalls when free redo log is too small. When MariaDB stalls, even a quite simple query takes too long. (table definition) CREATE TABLE `catalog` ( `uid` bigint(20) unsigned NOT NULL, `path` varchar(255) NOT NULL DEFAULT '', ... PRIMARY KEY (`uid`), KEY `Path` (`path`), ... ) (from pt-query-digest output) # Attribute pct total min max avg 95% stddev median # ============ === ======= ======= ======= ======= ======= ======= ======= # Count 2 91 # Exec time 2 716s 1s 17s 8s 15s 5s 7s # Lock time 0 22ms 156us 491us 238us 366us 70us 204us # Rows sent 0 663 3 10 7.29 8.91 1.09 6.98 # Rows examine 0 663 3 10 7.29 8.91 1.09 6.98 # Rows affecte 0 0 0 0 0 0 0 0 # Bytes sent 0 52.10k 330 749 586.24 685.39 68.46 563.87 # Query size 0 470.83k 3.56k 5.26k 5.17k 5.20k 225.56 5.20k SELECT uid, path FROM catalog WHERE path in ('...', /*... omitted 80 items ...*/)\G (here, these SELECT are issued in READ COMMITTED isolation level) Our understanding is that the stalls are caused by the undo log cleanup job, and/or the innodb buffer pool writeback job. Increasing the undo log size a lot seems to reduce the frequency of those stalls. For our reference workload here, we still have stalls with 1GB log file but we don't have stalls with 2GB or more log file. If we need 'big enough' log file size to avoid stalls, will the ideal size be proportional to the amount of data or proportional to the buffer pool size ? We have never had such stall on MariaDB 10.4 even with small 128MB log file. How this difference happen and is there any configuration to improve the behaviour ? Thanks in advance ! Best regards, Kazuhiko SHIOZAKI

4 15

MariaDB Day @ Brussels 01.02.2025
by Anna Widenius 05 Jan '25

05 Jan '25

Hi All! We are at it again, MariaDB Day is coming to Brussels 1.02.2025 - https://www.meetup.com/mariadb-server/events/305194675/ MariaDB Day events bring together the MariaDB Foundation and community to celebrate and share the latest developments in MariaDB Server. Theme: Vectors, RAG, and everything new in MariaDB Server. With the imminent GA release of MariaDB Vector in MariaDB 11.7, we’re excited to showcase new functionality, real-world use cases, and the promise of Gen AI capabilities within MariaDB Server. Early previews already point to significant enhancements in both features and performance. Compatibility remains a hallmark of MariaDB Server. In many cases, upgrading from MySQL to the latest MariaDB release is simpler than moving to newer MySQL versions, particularly MySQL 8.0 and later. If you’ve attended previous MariaDB Days, you’ll notice a continuing commitment to our core themes. We see databases as a constant source of innovation—one of the many reasons we love gathering with you around FOSDEM each year. Remember to RSVP - places are limited! 💥 https://mariadb.org/projects/mariadb-vector/ Anna Widenius Chief of Staff, MariaDB Foundation

1 0