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

'aio write' returned OS error 222. Cannot continue operation

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Incomplete
    • 10.7
    • N/A
    • None

    Description

      Our environment have three DB replication cluster including 2 master nodes and 1 slave. [When writer points to 1st database 2nd one will behave like a slave]. The issue is on both the slave nodes mysqld is getting crashed with the following error in /var/log/messages

      Aug 24 10:55:18 ALEPO-DB2-ILB NetworkManager[1266]: <info>  [1692856518.8257] dhcp4 (enp9s0): canceled DHCP transaction
      Aug 24 10:59:13 ALEPO-DB2-ILB systemd[1]: Started Process Core Dump (PID 128368/UID 0).
      Aug 24 10:59:13 ALEPO-DB2-ILB systemd-coredump[128369]: Resource limits disable core dumping for process 4079310 (mariadbd).
      Aug 24 10:59:13 ALEPO-DB2-ILB systemd-coredump[128369]: Process 4079310 (mariadbd) of user 993 dumped core.
      Aug 24 10:59:13 ALEPO-DB2-ILB systemd[1]: systemd-coredump@10-128368-0.service: Succeeded.
      Aug 24 10:59:14 ALEPO-DB2-ILB systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
      Aug 24 10:59:14 ALEPO-DB2-ILB systemd[1]: mariadb.service: Failed with result 'signal'.
      Aug 24 10:59:19 ALEPO-DB2-ILB systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
      Aug 24 10:59:19 ALEPO-DB2-ILB systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 2.
      Aug 24 10:59:19 ALEPO-DB2-ILB systemd[1]: Stopped MariaDB 10.7.4 database server.
      Aug 24 10:59:19 ALEPO-DB2-ILB systemd[1]: Starting MariaDB 10.7.4 database server...
      Aug 24 10:59:19 ALEPO-DB2-ILB mariadbd[128596]: 2023-08-24 10:59:19 0 [Note] /usr/sbin/mariadbd (server 10.7.4-MariaDB-log) starting as process 128596 ...
      Aug 24 10:59:19 ALEPO-DB2-ILB mariadbd[128596]: 2023-08-24 10:59:19 0 [Warning] Could not increase number of max_open_files to more than 32768 (request: 33629)
      
      

      And at the same time, mysqld log shows this issue:

      2023-08-24 10:59:13 0 [ERROR] InnoDB: Operating system error number 22 in a file operation.
      2023-08-24 10:59:13 0 [ERROR] InnoDB: Error number 22 means 'Invalid argument'
      2023-08-24 10:59:13 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
      2023-08-24 10:59:13 0 [ERROR] InnoDB: File ./aaadb/authenticationlog#P#p202308.ibd: 'aio write' returned OS error 222. Cannot continue operation
      230824 10:59:13 [ERROR] mysqld got signal 6 ;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.
       
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs
       
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed,
      something is definitely wrong and this may fail.
       
      Server version: 10.7.4-MariaDB-log
      key_buffer_size=67108864
      read_buffer_size=131072
      max_used_connections=8
      max_threads=802
      thread_count=15
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1831745 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 0x0 thread_stack 0x49000
      ??:0(my_print_stacktrace)[0x55f4b120e31e]
      ??:0(handle_fatal_signal)[0x55f4b0d09755]
      ??:0(__restore_rt)[0x7f387467dcf0]
      :0(__GI_raise)[0x7f38739d8aff]
      :0(__GI_abort)[0x7f38739abea5]
      ??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x55f4b0968add]
      ??:0(std::pair<std::_Rb_tree_iterator<std::pair<unsigned int const, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, bool> std::_Rb_tree<unsigned int, std::pair<unsigned int const, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::_Select1st<std::pair<unsigned int const, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, std::less<unsigned int>, std::allocator<std::pair<unsigned int const, std::__cxx??:0(std::thread::thread<void (&)(), , void>(void (&)()))[0x55f4b114262e]
      ??:0(std::pair<std::_Rb_tree_iterator<std::pair<unsigned long const, bool> >, bool> std::_Rb_tree<unsigned long, std::pair<unsigned long const, bool>, std::_Select1st<std::pair<unsigned long const, bool> >, std::less<unsigned long>, std::allocator<std::pair<unsigned long const, bool> > >::_M_emplace_unique<unsigned long&, bool>(unsigned long&, bool&&))[0x55f4b1102ad2]
      ??:0(std::thread::thread<void (&)(), , void>(void (&)()))[0x55f4b1142abc]
      ??:0(std::pair<std::_Rb_tree_iterator<std::pair<unsigned int const, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, bool> std::_Rb_tree<unsigned int, std::pair<unsigned int const, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::_Select1st<std::pair<unsigned int const, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, std::less<unsigned int>, std::allocator<std::pair<unsigned int const, std::__cxx??:0(tpool::task_group::execute(tpool::task*))[0x55f4b11a333c]
      ??:0(tpool::thread_pool_generic::worker_main(tpool::worker_data*))[0x55f4b11a220f]
      ??:0(std::error_code::default_error_condition() const)[0x7f3874194ba3]
      ??:0(start_thread)[0x7f38746731ca]
      :0(__GI___clone)[0x7f38739c3e73]
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /var/lib/mysql
      Resource Limits:
      Limit                     Soft Limit           Hard Limit           Units
      Max cpu time              unlimited            unlimited            seconds
      Max file size             unlimited            unlimited            bytes
      Max data size             unlimited            unlimited            bytes
      Max stack size            8388608              unlimited            bytes
      Max core file size        0                    unlimited            bytes
      Max resident set          unlimited            unlimited            bytes
      Max processes             2061710              2061710              processes
      Max open files            32768                32768                files
      Max locked memory         65536                65536                bytes
      Max address space         unlimited            unlimited            bytes
      Max file locks            unlimited            unlimited            locks
      Max pending signals       2061710              2061710              signals
      Max msgqueue size         819200               819200               bytes
      Max nice priority         0                    0
      Max realtime priority     0                    0
      Max realtime timeout      unlimited            unlimited            us
      Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e
      
      

      Attachments

        1. screenshot-1.png
          screenshot-1.png
          12 kB
        2. screenshot-2.png
          screenshot-2.png
          5 kB
        3. screenshot-3.png
          screenshot-3.png
          5 kB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              mansi mansi dadheech
              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.