Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-7644

Crash when using Tee filter under load

    XMLWordPrintable

Details

    • MXS-SPRINT-281
    • Can result in hang or crash
    • Fixed a crash where readconnroute would somtimes crash if used with the tee filter.

    Description

      Crash log output below; no core file could be found:

      2026-10-13 12:48:03   alert  : (84881518) (RW-Service); MaxScale 25.10.2 received fatal signal 11. Commit ID: b3ec15083910892bebabb23f2e80e49df6860421, System name: Linux, Release string: Rocky Linux 9.7 (Blue Onyx), Thread: Worker-00
      2026-10-13 12:48:03   alert  : (84881518) (RW-Service); Last systemd watchdog notification was 18.31s ago, notification interval is 30s. Last 5 notifications: ["2026-10-13T12:45:45+0000", "2026-10-13T12:46:15+0000", "2026-10-13T12:46:45+0000", "2026-10-13T12:47:15+0000", "2026-10-13T12:47:45+0000"]
      2026-10-13 12:48:03   alert  : (84881518) (RW-Service); Statement currently being classified: none/unknown
      2026-10-13 12:48:03   alert  : (84881518) (RW-Service); Session: 84881518 Service: Fran-RW-Service
      2026-10-13 12:48:03   notice : (84881518) (RW-Service); For a more detailed stacktrace, install GDB.
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0 (maxbase::dump_stacktrace(std::function<void (char const*)>)): maxutils/maxbase/src/stacktrace.cc:190
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0 (std::_Function_base::~_Function_base()): /usr/include/c++/11/bits/std_function.h:243
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0 ((anonymous namespace)::sigfatal_handler(int)): server/core/process.cc:301
        /lib64/libc.so.6 (__restore_rt): ??:?
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0 (std::__atomic_base<long>::fetch_sub(long, std::memory_order)): /usr/include/c++/11/bits/atomic_base.h:628
        /usr/lib64/maxscale/libreadconnroute.so (RCRSession::clientReply(GWBUF&&, maxscale::ReplyRoute const&, maxscale::Reply const&)): maxutils/maxbase/include/maxbase/log.hh:256
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0 (maxbase::LogScope::~LogScope()): maxutils/maxbase/include/maxbase/log.hh:586
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0 (maxbase::LogScope::~LogScope()): maxutils/maxbase/include/maxbase/log.hh:586
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0 (std::vector<std::vector<std::basic_string_view<char, std::char_traits<char> >, std::allocator<std::basic_string_view<char, std::char_traits<char> > > >, std::allocator<std::vector<std::basic_string_view<char, std::char_traits<char> >, std::allocator<std::basic_string_view<char, std::char_traits<char> > > > > >::clear()): /usr/include/c++/11/bits/stl_vector.h:1499
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0 (std::__shared_ptr<maxscale::Session, (__gnu_cxx::_Lock_policy)2>::get() const): /usr/include/c++/11/bits/shared_ptr_base.h:1296
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0 (DCB::handle_poll_events(maxbase::Worker*, unsigned int)): server/core/dcb.cc:1367
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0 (maxbase::Worker::poll_waitevents()): maxutils/maxbase/src/worker.cc:1031
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0 (maxbase::Worker::run(maxbase::Semaphore*)): maxutils/maxbase/src/worker.cc:790
        /lib64/libstdc++.so.6 (std::error_code::default_error_condition() const): ??:?
        /lib64/libc.so.6 (start_thread): ??:?
        /lib64/libc.so.6 (__clone3): :?
      MaxScale 25.10.2 received fatal signal 11. Commit ID: b3ec15083910892bebabb23f2e80e49df6860421, System name: Linux, Release string: Rocky Linux 9.7 (Blue Onyx), Thread: Worker-00Not writing core dump.
      

      Attachments

        Activity

          People

            markus makela markus makela
            hholzgra Hartmut Holzgraefe
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 2d
                2d
                Remaining:
                Remaining Estimate - 0d
                0d
                Logged:
                Time Spent - 1d Time Not Required
                1d

                Git Integration

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