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

mariadb galera cluster db services went off with signal 6,11 received by mariadb

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Server
    • Labels:

      Description

      Please consider 3 node galera cluster setup and all 3 db services at same time stopped.
      Kindly help us point to the right direction why it happened. (is it os/db/network/application issue )?

      Server version: 10.5.12-MariaDB-log
      /var/log/mariadb/mariadb.log

      2022-01-19 17:30:05 2 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
      2022-01-19 17:30:05 2 [Note] WSREP: Lowest cert index boundary for CC from group: 4883927
      2022-01-19 17:30:05 2 [Note] WSREP: Min available from gcache for CC from group: 4738743
      2022-01-19 17:30:07 0 [Note] WSREP: cleaning up fe929552-a12a (tcp://130.100.145.100:4567)
      terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::system_error> >'
      what(): remote_endpoint: Transport endpoint is not connected
      220119 17:30:16 [ERROR] mysqld got signal 6 ;
      This could be because you hit a bug.

      something went
      terribly wrong...
      stack_bottom = 0x0 thread_stack 0x49000
      ??:0(my_print_stacktrace)[0x5620aef4640e]
      ??:0(handle_fatal_signal)[0x5620ae949547]
      sigaction.c:0(__restore_rt)[0x7f90e0748630]
      :0(__GI_raise)[0x7f90dfb93387]
      :0(__GI_abort)[0x7f90dfb94a78]
      ??:0(_gnu_cxx::_verbose_terminate_handler())[0x7f90e028da95]
      ??:0(std::rethrow_exception(std::__exception_ptr::exception_ptr))[0x7f90e028ba06]
      ??:0(std::terminate())[0x7f90e028ba33]
      ??:0(__cxa_throw)[0x7f90e028bc53]
      /usr/lib64/galera-4/libgalera_smm.so(+0x197ab4)[0x7f90dc923ab4]
      4.8.2/stdexcept:112(runtime_error)[0x7f90dc923b5c]
      impl/throw_error.ipp:49(asio::detail::do_throw_error(std::error_code const&, char const*))[0x7f90dc92fcbf]
      detail/throw_error.hpp:41(throw_error)[0x7f90dc9322e2]
      src/gu_asio_stream_react.cpp:880(gu::AsioAcceptorReact::accept_handler(std::shared_ptr<gu::AsioStreamReact> const&, std::shared_ptr<gu::AsioAcceptorHandler> const&, std::error_code const&))[0x7f90dc936533]
      detail/gcc_x86_fenced_block.hpp:80(asio::detail::gcc_x86_fenced_block::sbarrier())[0x7f90dc922eeb]
      impl/task_io_service.ipp:373(asio::detail::task_io_service::do_run_one(asio::detail::scoped_lock<asio::detail::posix_mutex>&, asio::detail::task_io_service_thread_info&, std::error_code const&))[0x7f90dc91ed81]
      impl/task_io_service.ipp:148(asio::detail::task_io_service::run(std::error_code&))[0x7f90dc84b599]
      src/asio_protonet.cpp:104(gcomm::AsioProtonet::event_loop(gu::datetime::Period const&))[0x7f90dc8325d7]
      src/gu_mutex.hpp:50(gu::Mutex::lock() const)[0x7f90dc832989]
      pthread_create.c:0(start_thread)[0x7f90e0740ea5]
      ??:0(__clone)[0x7f90dfc5b96d]
      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:

      Fatal signal 11 while backtracing
      220119 17:30:18 mysqld_safe Number of processes running now: 0
      220119 17:30:18 mysqld_safe WSREP: not restarting wsrep node automatically

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            abhishek.mitra.in abhishek mitra
            Votes:
            1 Vote for this issue
            Watchers:
            1 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.