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

MariaDB crashes on startup

Details

    Description

      Hello,
      Server crashes on startup on a subset of hosts. The rest have been upgraded successfully.
      Attached is the startup log. I can't correlate the hosts environment, they are a bit different, but not fundamentally. I'm also not able to find the core file, although is says one has been written.

      Please, advise.

      Attachments

        1. core.23694.gz
          1.45 MB
        2. mariadb_10_4_28_crash_log.txt
          9 kB
        3. mdev22580_threads
          31 kB
        4. mdev22580_threads_full
          45 kB
        5. not_ok.cfg.tar.gz
          1 kB
        6. ok.cfg.tar.gz
          2 kB
        7. Selection_341.png
          Selection_341.png
          6 kB
        8. Selection_342.png
          Selection_342.png
          20 kB
        9. signature.asc
          0.8 kB
        10. startup_crash.txt
          6 kB

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-30826 Invalid data on mysql.host segfaults the server after an upgrade to 10.4

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 9 older comments
            danblack Daniel Black added a comment -

            Belatedly, it looks like the mysql.host table contained a db column with an entry, when retrieved, wasn't null terminated, possibly because it was right at the maximum length of the db column.

            danblack Daniel Black added a comment - Belatedly, it looks like the mysql.host table contained a db column with an entry, when retrieved, wasn't null terminated, possibly because it was right at the maximum length of the db column.
            bofh Georgi Sinapov added a comment -

            Hello,
            This is definitely not the case.

            bofh Georgi Sinapov added a comment - Hello, This is definitely not the case.
            serg Sergei Golubchik added a comment -

            This is likely the same bug as in MDEV-30826

            serg Sergei Golubchik added a comment - This is likely the same bug as in MDEV-30826
            bofh Georgi Sinapov added a comment -

            Unfortunately, the problem is still there.

            bofh Georgi Sinapov added a comment - Unfortunately, the problem is still there.
            serg Sergei Golubchik added a comment -

            Still where? You have attached mariadb_10_4_28_crash_log.txt, it says

            Mar 12 13:02:18 localhost mysqld: 2023-03-12 13:02:18 0 [Note] Starting MariaDB 10.4.28-MariaDB source revision c8f2e9a5c0ac5905f28b050b7df5a9ffd914b7e7 as process 14549

            while the bug was fixed in 10.4.29 (see Fix Version/s field above) in the commit 8145b308b02ee7ee657851c1faee49c7b7ebf511 (see the [Git Commits] tab of the linked bug).

            As a workaround you can try 

            UPDATE mysql.host SET db='%' WHERE db=''

            serg Sergei Golubchik added a comment - Still where? You have attached mariadb_10_4_28_crash_log.txt , it says Mar 12 13:02:18 localhost mysqld: 2023-03-12 13:02:18 0 [Note] Starting MariaDB 10.4.28-MariaDB source revision c8f2e9a5c0ac5905f28b050b7df5a9ffd914b7e7 as process 14549 while the bug was fixed in 10.4.29 (see Fix Version/s field above) in the commit 8145b308b02ee7ee657851c1faee49c7b7ebf511 (see the [Git Commits] tab of the linked bug). As a workaround you can try UPDATE mysql.host SET db= '%' WHERE db= ''

            People

              serg Sergei Golubchik
              bofh Georgi Sinapov
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.