Uploaded image for project: 'HPCC'
  1. HPCC
  2. HPCC-16521

Thor slave death in CMemoryUsageReporter

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 6.2.2, 6.0.12
    • Component/s: JLib
    • Labels:
      None

      Description

      Sporadic abrupt thor slave termination have been happening in 5.6.8-1 builds, the stack is always the same:

      #0  0x00007fb1dcddc5f7 in raise () from /lib64/libc.so.6
      #1  0x00007fb1dcdddce8 in abort () from /lib64/libc.so.6
      #2  0x00007fb1dce1c327 in __libc_message () from /lib64/libc.so.6
      #3  0x00007fb1dce24053 in _int_free () from /lib64/libc.so.6
      #4  0x00007fb1de0c4fa6 in CMemoryUsageReporter::run() () from /opt/HPCCSystems/lib/libjlib.so
      #5  0x00007fb1de16adcc in Thread::begin() () from /opt/HPCCSystems/lib/libjlib.so
      #6  0x00007fb1de16c5be in Thread::_threadmain(void*) () from /opt/HPCCSystems/lib/libjlib.so
      #7  0x00007fb1dd170dc5 in start_thread () from /lib64/libpthread.so.0
      #8  0x00007fb1dce9dced in clone () from /lib64/libc.so.6
      

      It looks like this may coincide with the introduction of the UDP and SNMP /proc monitoring.

      Looking at the code involved, a couple of minor (possibly impossible to hit) issues were found, see: HPCC-16518

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                mckellyln Mark Kelly
                Reporter:
                jakesmith Jake Smith
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: