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

Shutdown take indefinitely when /tmp is full.

    XMLWordPrintable

Details

    • Bug
    • Status: In Review (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.6.16
    • 10.5, 10.6
    • None
    • None

    Description

      The customer rebooted the VM due to /tmp reached 100%. But MariaDB server shutdown took a very long time(refer to the error log attached) . It doesn't have any info about when the shutdown completed. There is no info InnoDB: Starting Shutdown and [Note] /usr/sbin/mariadbd: Shutdown complete was logged in the error log.

      2024-07-18 10:33:06 553 [ERROR] mariadbd: Disk full (/mariadb/tmp/#sql-temptable-b73-229-2349f1.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
      2024-07-18 10:33:07 973590463 [ERROR] mariadbd: Disk full (/mariadb/tmp/#sql-temptable-b73-3a07cfbf-2700d.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
      2024-07-18 10:33:07 0 [Note] /usr/sbin/mariadbd (initiated by: unknown): Normal shutdown
       
      2024-07-18 10:33:08 1 [Note] Stopping ack receiver thread
      2024-07-18 10:33:28 0 [Warning] /usr/sbin/mariadbd: Thread 973538290 (user : 'monuser') did not exit
      2024-07-18 10:33:28 0 [Warning] /usr/sbin/mariadbd: Thread 973327102 (user : 'monuser') did not exit
       
      2024-07-18 10:33:28 0 [Warning] /usr/sbin/mariadbd: Thread 973315593 (user : 'monuser') did not exit
       
      2024-07-18 10:33:28 0 [Warning] /usr/sbin/mariadbd: Thread 973260285 (user : 'monuser') did not exit
       
      2024-07-18 10:33:28 0 [Warning] /usr/sbin/mariadbd: Thread 973250296 (user : 'casadb_user') did not exit
       
      2024-07-18 10:33:28 0 [Warning] /usr/sbin/mariadbd: Thread 973230937 (user : 'casadb_user') did not exit
      2024-07-18 10:33:28 0 [Warning] /usr/sbin/mariadbd: Thread 973230894 (user : 'casadb_user') did not exit
       
      .......
      .......
       
      2024-07-18 10:34:02 973214855 [ERROR] mariadbd: Disk full (/mariadb/tmp/#sql-temptable-b73-3a021487-3426d.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
      2024-07-18 10:34:02 973214855 [Warning] Sort aborted, host: 10.219.245.102, user: casadb_user, thread: 973214855, query: Select func.FUNCTION_NAME as function, txn.product_type as productType, PRODUCT_ID as productId, REQ_DATE as requestDate,REQ_DATE_TIME as requestDateTimeStr, req_time as requestTime, COUNTRYCODE as country, DOC_STAGE as stage, txn.ID as txnRefNumber, txn.sub_stage as subStage, channel as channel, customer_name as customerName, coalesce(nullif(txn.cif_id,''), txn.customerid) as cifId, branch_code as branchCode, originals as originals, bu as bu, txn.priority  as priority, branch_name as branchName, txn.status as status, sub_status as subStatus, assignee as assignee, txn.sub_product_type  as subProductType , txn.CASE_NUM as caseNum, txn.DOC_REF_NUM as docRefNum, IF (st.stage_name LIKE '%RPA%', 'RPA', st.stage_name) as stageDesc, txn.skill as skill, txn.segment as segment , txn.biz_field1 as bizfield1, txn.biz_field2 as bizfield2, txn.biz_field3 as bizfield3, txn.biz_field4 as bizfield4,txn.acted_by as actedBy, txn.modified_date as 
      2024-07-18 10:48:42 937893309 [Note] Stop semi-sync binlog_dump to slave (server_id: 1)
      2024-07-18 10:48:42 937893309 [Warning] Aborted connection 937893309 to db: 'unconnected' user: 'repuser' host: '10.219.235.178' (Got an error writing communication packets)
      
      

      Attachments

        Issue Links

          Activity

            People

              danblack Daniel Black
              pandi.gurusamy Pandikrishnan Gurusamy
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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