Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-33040

MariaDB restarted [ERROR] mysqld got signal 11

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • 10.5.9
    • N/A
    • Red Hat Enterprise Linux 8.5 (Ootpa)
      10.5.9-MariaDB

    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 .

      MariaDB [(none)]> status;
      --------------
      mysql  Ver 15.1 Distrib 10.5.9-MariaDB, for Linux (x86_64) using readline 5.1
       
      Connection id:          18415
      Current database:
      Current user:           unm@localhost
      SSL:                    Not in use
      Current pager:          stdout
      Using outfile:          ''
      Using delimiter:        ;
      Server:                 MariaDB
      Server version:         10.5.9-MariaDB-log MariaDB Server
      Protocol version:       10
      Connection:             Localhost via UNIX socket
      Server characterset:    utf8
      Db     characterset:    utf8
      Client characterset:    utf8
      Conn.  characterset:    utf8
      UNIX socket:            /tmp/mysql.sock
      *Uptime:                 3 hours 8 min 24 sec*
       
      Threads: 700  Questions: 562457  Slow queries: 0  Opens: 1016  Open tables: 1009  Queries per second avg: 49.757
      --------------
       
      MariaDB [(none)]> exit
      Bye
      $ ps -ewf|grep mysqld
      unm 2459083 2458709  0 09:48 pts/0    00:00:00 grep --color=auto mysqld
      *unm 3438211       1  0 Jul19 ?        *00:00:00 /bin/sh <PATH>/mysqld_safe --datadir=/<PATH>
      $
      

      Attachments

        Activity

          danblack Daniel Black added a comment -

          Cannot reproduce on latest 10.5 release:

          MariaDB [testdb]> CREATE TABLE `denodo_camp_promo_view` ( `ID` decimal(15,0) DEFAULT NULL,   `name` varchar(80) DEFAULT NULL,   `startdate` date DEFAULT NULL,   `enddate` date DEFAULT NULL,  `ownerid` varchar(18) DEFAULT NULL, `promotion_code__c` varchar(255) DEFAULT NULL,  `PROMOCODE_DETAILS` varchar(321) DEFAULT NULL );
          Query OK, 0 rows affected (0.018 sec)
           
          MariaDB [testdb]> 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';
          Query OK, 1 row affected (0.003 sec)
          Records: 1  Duplicates: 0  Warnings: 0
           
          MariaDB [testdb]> \s
          --------------
          mariadb  Ver 15.1 Distrib 10.5.23-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
           
          Connection id:		28000
          Current database:	testdb
          Current user:		root@localhost
          SSL:			Not in use
          Current pager:		stdout
          Using outfile:		''
          Using delimiter:	;
          Server:			MariaDB
          Server version:		10.5.23-MariaDB-1:10.5.23+maria~ubu2004 mariadb.org binary distribution
          Protocol version:	10
          Connection:		Localhost via UNIX socket
          Server characterset:	utf8mb4
          Db     characterset:	utf8mb4
          Client characterset:	utf8
          Conn.  characterset:	utf8
          UNIX socket:		/run/mysqld/mysqld.sock
          Uptime:			4 days 14 hours 34 min 33 sec
           
          Threads: 22  Questions: 56142  Slow queries: 0  Opens: 27  Open tables: 20  Queries per second avg: 0.141
          --------------
           
          MariaDB [testdb]> select version();
          +-----------------------------------------+
          | version()                               |
          +-----------------------------------------+
          | 10.5.23-MariaDB-1:10.5.23+maria~ubu2004 |
          +-----------------------------------------+
          1 row in set (0.001 sec)
          

          danblack Daniel Black added a comment - Cannot reproduce on latest 10.5 release: MariaDB [testdb]> CREATE TABLE `denodo_camp_promo_view` ( `ID` decimal(15,0) DEFAULT NULL, `name` varchar(80) DEFAULT NULL, `startdate` date DEFAULT NULL, `enddate` date DEFAULT NULL, `ownerid` varchar(18) DEFAULT NULL, `promotion_code__c` varchar(255) DEFAULT NULL, `PROMOCODE_DETAILS` varchar(321) DEFAULT NULL ); Query OK, 0 rows affected (0.018 sec)   MariaDB [testdb]> 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'; Query OK, 1 row affected (0.003 sec) Records: 1 Duplicates: 0 Warnings: 0   MariaDB [testdb]> \s -------------- mariadb Ver 15.1 Distrib 10.5.23-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2   Connection id: 28000 Current database: testdb Current user: root@localhost SSL: Not in use Current pager: stdout Using outfile: '' Using delimiter: ; Server: MariaDB Server version: 10.5.23-MariaDB-1:10.5.23+maria~ubu2004 mariadb.org binary distribution Protocol version: 10 Connection: Localhost via UNIX socket Server characterset: utf8mb4 Db characterset: utf8mb4 Client characterset: utf8 Conn. characterset: utf8 UNIX socket: /run/mysqld/mysqld.sock Uptime: 4 days 14 hours 34 min 33 sec   Threads: 22 Questions: 56142 Slow queries: 0 Opens: 27 Open tables: 20 Queries per second avg: 0.141 --------------   MariaDB [testdb]> select version(); +-----------------------------------------+ | version() | +-----------------------------------------+ | 10.5.23-MariaDB-1:10.5.23+maria~ubu2004 | +-----------------------------------------+ 1 row in set (0.001 sec)
          danblack Daniel Black added a comment -

          is fixed somewhere between 10.5.9 and 10.5.23.

          danblack Daniel Black added a comment - is fixed somewhere between 10.5.9 and 10.5.23.
          MurthyRamachandrula R S N Murthy added a comment -

          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.

          MurthyRamachandrula R S N Murthy added a comment - 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.
          danblack Daniel Black added a comment -

          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.

          danblack Daniel Black added a comment - 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.
          MurthyRamachandrula R S N Murthy added a comment -

          That certainly helps. Thank you very much

          MurthyRamachandrula R S N Murthy added a comment - That certainly helps. Thank you very much

          People

            danblack Daniel Black
            MurthyRamachandrula R S N Murthy
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.