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

mysqld.exe hangs after upgrade

    XMLWordPrintable

Details

    Description

      After upgrading from 5.5.47 to 5.5.48 MariaDB Server hangs.

      When our application hangs connecting with MariaDB using MySQL Workbench is not possible anymore.

      Our own application hangs waiting for a response from MariaDB but it doesn't get anything. After 1 hour of waiting it gets a timeout.

      Attached is the minidump from MariaDB. (mysqld.001 - mysqld.015 --> mysqld.dmp)

      And here is the stacktrace from our application:

      14  Id: d4c.d54 Suspend: 0 Teb: 00007ff6`86286000 Unfrozen
      		 
      Child-SP          RetAddr           Call Site
      		 
      00000000`02e4ec58 00007fff`48f9298f ntdll!ZwWaitForSingleObject+0xa
      		 
      00000000`02e4ec60 00007fff`48f96a08 mswsock!SockWaitForSingleObject+0x152
      		 
      00000000`02e4ece0 00007fff`4ad82707 mswsock!WSPRecv+0x622
      		 
      *** WARNING: Unable to verify checksum for libmariadb.dll
      		 
      *** ERROR: Symbol file could not be found.  Defaulted to export symbols for libmariadb.dll - 
      00000000`02e4ede0 00007fff`2d2c9996 ws2_32!recv+0x197
      		 
      00000000`02e4ee80 00007fff`2d2c9a58 libmariadb!mysql_ssl_set+0x8059
      		 
      00000000`02e4eec0 00007fff`2d2ca36e libmariadb!mysql_ssl_set+0x811b
      		 
      00000000`02e4eef0 00007fff`2d2ca49d libmariadb!mysql_ssl_set+0x8a31
      		 
      00000000`02e4ef30 00007fff`2d2d1212 libmariadb!mysql_ssl_set+0x8b60
      		 
      00000000`02e4ef80 00007fff`2d2d2b9b libmariadb!mysql_ssl_set+0xf8d5
      		 
      *** WARNING: Unable to verify checksum for sqlapi.dll
      		 
      00000000`02e4efb0 00007fff`3006bf18 libmariadb!mysql_ssl_set+0x1125e
      		 
      00000000`02e4eff0 00007fff`3001ce16 sqlapi!ImyCursor::Execute+0x7f8
      		 
      00000000`02e4f160 00000000`60faa03e sqlapi!SACommand::Execute+0x56
      		 
      00000000`02e4f1d0 00007ff6`86f2c381 dllsqlapiext!C_SACommand::Execute+0x7e [e:\ziscvs_b5810_x64\all\all_os\sqlapiext\c_sacommand.cpp @ 152]
      		 
      00000000`02e4f240 00007ff6`869fec08 zis_data!db_select_zis_object_group_def_which_contains_zisoid+0x111 [e:\ziscvs_b5810_x64\all\all_os\datenbank\dbzisobjectgroupdef.cpp @ 2140]
      		 
      00000000`02e4f350 00007ff6`868720c9 zis_data!C_DBQuery::GetZISObjectGroupDefWhichContainsZISOid+0x48 [e:\ziscvs_b5810_x64\all\all_os\data\c_dbquery.cpp @ 555]
      		 
      00000000`02e4f3f0 00007ff6`86a99490 zis_data!C_DataView::DeleteZISOidFromAllZISObjectGroupDefs+0x79 [e:\ziscvs_b5810_x64\all\all_os\data\c_dataview.cpp @ 1346]
      		 
      00000000`02e4f4e0 00007ff6`86839265 zis_data!C_SessionDefDataView::GetInsertDBCommandList+0x190 [e:\ziscvs_b5810_x64\all\all_os\data\c_sessiondefdataview.cpp @ 71]
      		 
      00000000`02e4f600 00007ff6`86aa50bf zis_data!C_SessionManager::InsertSessionIntoDB+0x1c5 [e:\ziscvs_b5810_x64\all\all_os\data\c_sessionmanager.cpp @ 2743]
      		 
      00000000`02e4f740 00007ff6`86aa550f zis_data!C_SessionManagerWorker::CommandInsertSessionIntoDB+0x5f [e:\ziscvs_b5810_x64\all\all_os\data\c_sessionmanagerworker.cpp @ 216]
      		 
      00000000`02e4f850 00007ff6`86aa614e zis_data!C_SessionManagerWorker::ExecuteCommand+0x5f [e:\ziscvs_b5810_x64\all\all_os\data\c_sessionmanagerworker.cpp @ 187]
      		 
      00000000`02e4f930 00007ff6`86b4601c zis_data!C_SessionManagerWorker::Run+0x2fe [e:\ziscvs_b5810_x64\all\all_os\data\c_sessionmanagerworker.cpp @ 127]
      		 
      00000000`02e4fad0 00007fff`334fe5e1 zis_data!C_ACETask<ACE_Refcounted_Auto_Ptr_With_Single_Mutex<C_MigrateEUStatusTablesCommand,ACE_Thread_Mutex>,long>::svc+0x11c [e:\ziscvs_b5810_x64\all\all_os\tools\c_acetask.h @ 1214]
      		 
      00000000`02e4fb60 00007fff`334feec1 ACE!ACE_Task_Base::svc_run+0x41 [e:\ziscvs_b5810_x64\all\vendor\ace_wrappers\ace\task.cpp @ 275]
      		 
      00000000`02e4fb90 00007fff`334fee14 ACE!ACE_Thread_Adapter::invoke_i+0x71 [e:\ziscvs_b5810_x64\all\vendor\ace_wrappers\ace\thread_adapter.cpp @ 161]
      		 
      00000000`02e4fbe0 00000000`65111d9f ACE!ACE_Thread_Adapter::invoke+0xd4 [e:\ziscvs_b5810_x64\all\vendor\ace_wrappers\ace\thread_adapter.cpp @ 96]
      		 
      00000000`02e4fc20 00000000`65111e3b msvcr100!_callthreadstartex+0x17
      		 
      00000000`02e4fc50 00007fff`4a9b13d2 msvcr100!_threadstartex+0x7f
      		 
      00000000`02e4fc80 00007fff`4c645454 kernel32!BaseThreadInitThunk+0x22
      		 
      00000000`02e4fcb0 00000000`00000000 ntdll!RtlUserThreadStart+0x34

      Attachments

        1. windbg_output2_1b20_2016-05-20_19-33-35-246.txt
          39 kB
        2. windbg_output.txt
          40 kB
        3. mysqld.zip
          1.08 MB
        4. mysqld.crc
          0.1 kB
        5. mysqld.015
          1.17 MB
        6. mysqld.014
          1.39 MB
        7. mysqld.013
          1.39 MB
        8. mysqld.012
          1.39 MB
        9. mysqld.011
          1.39 MB
        10. mysqld.010
          1.39 MB
        11. mysqld.009
          1.39 MB
        12. mysqld.008
          1.39 MB
        13. mysqld.007
          1.39 MB
        14. mysqld.006
          1.39 MB
        15. mysqld.005
          1.39 MB
        16. mysqld.004
          1.39 MB
        17. mysqld.003
          1.39 MB
        18. mysqld.002
          1.39 MB
        19. mysqld.001
          1.39 MB

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13635 MariaDB Server 10.2.6 hangs up during shutdown

          • Major - Major loss of function.
          • Open

          Activity

            People

              sanja Oleksandr Byelkin
              eidbadr Eid Badr
              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.