[MDEV-33040] MariaDB restarted [ERROR] mysqld got signal 11 Created: 2023-12-15 Updated: 2023-12-18 Resolved: 2023-12-17 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Optimizer - Window functions |
| Affects Version/s: | 10.5.9 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | R S N Murthy | Assignee: | Daniel Black |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | crash | ||
| Environment: |
Red Hat Enterprise Linux 8.5 (Ootpa) |
||
| Attachments: |
|
| Description |
|
MariaDB service was noticed restarted when checked with "status" command , however the OS process still shows older date. The Mariadb Error log file , /var/log/message and dmsg logs are attached to ticket .
|
| Comments |
| Comment by Sergei Golubchik [ 2023-12-15 ] | ||||||||||||||||||||||||||||||||||||||||
|
as the log shows, it could be due to the statement
could you show the table structure of denodo_camp_promo_view please? | ||||||||||||||||||||||||||||||||||||||||
| Comment by Daniel Black [ 2023-12-15 ] | ||||||||||||||||||||||||||||||||||||||||
|
10.5.9 is really old, has had almost 3 years of bugs fixes. I suspect this has been fixed already. Can you test the same insert query in the logs on the same data with a newer MariaDB version? It looked like mysqld_safe respawned the process. Until | ||||||||||||||||||||||||||||||||||||||||
| Comment by R S N Murthy [ 2023-12-16 ] | ||||||||||||||||||||||||||||||||||||||||
|
These is a "BASE TABLE" , as per table definition the default value of all columns is NULL. MariaDB [(none)]> select table_schema,table_name,table_type from information_schema.tables where table_name like '%denodo_camp_promo_view%';
-------------
------------- MariaDB [(none)]> show create table campaign.denodo_camp_promo_view;
-----------------------
----------------------- MariaDB [(none)]> select * from campaign.denodo_camp_promo_view where id is null;
-----
----- MariaDB [(none)]> | ||||||||||||||||||||||||||||||||||||||||
| Comment by R S N Murthy [ 2023-12-16 ] | ||||||||||||||||||||||||||||||||||||||||
|
Worked on TestEnv with the insert statement. same errors are observed. Insert statement using select crashed the instance Attaching the complete log containing error log , /var/log/messages and dmesg . MariaDB [(none)]> status; Connection id: 10 Threads: 3 Questions: 84 Slow queries: 0 Opens: 33 Open tables: 4 Queries per second avg: 0.000 MariaDB [(none)]> SELECT
-------------------------------------------
------------------------------------------- MariaDB [plan]> show tables; MariaDB [plan]> CREATE TABLE `denodo_camp_promo_view` ( MariaDB [plan]> INSERT INTO denodo_camp_promo_view (ID, name, startdate, enddate, ownerid, promotion_code__c, PROMOCODE_DETAILS) SELECT ROW_NUMBER() OVER (ORDER BY (SELECT NULL)),NULL,NULL,NULL,NULL,NULL,'NA'; MariaDB [plan]> status; -------------- Connection id: 5 Threads: 3 Questions: 20 Slow queries: 0 Opens: 17 Open tables: 11 Queries per second avg: 0.833 MariaDB [plan]> MariaDB [plan]> show tables;
------------------------
------------------------ MariaDB [plan]> select * from denodo_camp_promo_view; MariaDB [plan]> | ||||||||||||||||||||||||||||||||||||||||
| Comment by Daniel Black [ 2023-12-17 ] | ||||||||||||||||||||||||||||||||||||||||
|
Cannot reproduce on latest 10.5 release:
| ||||||||||||||||||||||||||||||||||||||||
| Comment by Daniel Black [ 2023-12-17 ] | ||||||||||||||||||||||||||||||||||||||||
|
is fixed somewhere between 10.5.9 and 10.5.23. | ||||||||||||||||||||||||||||||||||||||||
| Comment by R S N Murthy [ 2023-12-18 ] | ||||||||||||||||||||||||||||||||||||||||
|
Thank you for providing the fix, Please help with version upgrade steps for a Master Slave environment. we have used mariadb-10.5.9-linux-x86_64.tar.gz tar ball extract in present setup. | ||||||||||||||||||||||||||||||||||||||||
| Comment by Daniel Black [ 2023-12-18 ] | ||||||||||||||||||||||||||||||||||||||||
|
JIRA is for bug reports and not support sorry. See https://mariadb.com/kb/en/getting-help-with-mariadb/ if below isn't sufficient. Basics steps are there as 10.5.23 tarball here. It needs to replace your existing instance. Keep in mind your data dir is within your current mariadb installation. Update Slave first and then master. Ensure current instance is stopped before new instance is started. Run mariadb-upgrade afterwards on both master and slave. Keep a backup. | ||||||||||||||||||||||||||||||||||||||||
| Comment by R S N Murthy [ 2023-12-18 ] | ||||||||||||||||||||||||||||||||||||||||
|
That certainly helps. Thank you very much |