Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.8
    • Component/s: core
    • Security Level: public
    • Labels:
      None
    • CPU Architecture:
      x86-64
    • Kernel:
      Linux
    • Userland:
      GNU/Linux
    • Distribution:
      Debian
    • Distribution Version:
      Debian 8 jessie
    • Compiler:
      gcc
    • FreeSWITCH GIT Revision:
      35ee4ee593e729dd0bc5d672fac5ef35928b68aa
    • GIT Master Revision hash::
      35ee4ee593e729dd0bc5d672fac5ef35928b68aa

      Description

      I had an event that caused a leak/exhaustion of sessions. The problem is - I had NO way to determine from logs where/when they were created - such as accumulation or a sudden flood/burst.

      This patch (adding PR shortly) adds DEBUG level logging of session creation to correspond with the Session X (...) Ended logging output that currently exists at NOTICE level.

        Activity

        Hide
        mikej Mike Jerris added a comment -
        why not just add the count to the new/init logs out of the state machine instead of adding more log lines?
        Show
        mikej Mike Jerris added a comment - why not just add the count to the new/init logs out of the state machine instead of adding more log lines?
        Hide
        nneul Nathan Neulinger added a comment -
        That would work - but then it would also break anything that anyone else had already written that looked at those log lines for State Change. That seems far more likely to be rejected as a PR. If you think that would be preferred/approved, I can resubmit. Suggested content/format?
        Show
        nneul Nathan Neulinger added a comment - That would work - but then it would also break anything that anyone else had already written that looked at those log lines for State Change. That seems far more likely to be rejected as a PR. If you think that would be preferred/approved, I can resubmit. Suggested content/format?
        Hide
        mikej Mike Jerris added a comment -
        if someone is using log lines and parsing them instead of using a state hook or event, thats their problem. I don't have any specific suggestions on format, other than least obtrusive.
        Show
        mikej Mike Jerris added a comment - if someone is using log lines and parsing them instead of using a state hook or event, thats their problem. I don't have any specific suggestions on format, other than least obtrusive.
        Hide
        nneul Nathan Neulinger added a comment -
        Updated:

        0f84aa76-9801-4f94-8e18-4a0def0cc0de 2016-07-19 13:04:27.274964 [DEBUG] switch_core_state_machine.c:543 (SKINNY/internal/SEP00115C0F6B2B:1/1) Running State Change CS_NEW (Cur 1 Tot 6)
        Show
        nneul Nathan Neulinger added a comment - Updated: 0f84aa76-9801-4f94-8e18-4a0def0cc0de 2016-07-19 13:04:27.274964 [DEBUG] switch_core_state_machine.c:543 (SKINNY/internal/SEP00115C0F6B2B:1/1) Running State Change CS_NEW (Cur 1 Tot 6)
        Hide
        nneul Nathan Neulinger added a comment -
        Cur = now, Tot = since startup
        Show
        nneul Nathan Neulinger added a comment - Cur = now, Tot = since startup

          People

          • Assignee:
            mikej Mike Jerris
            Reporter:
            nneul Nathan Neulinger
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development