Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.6.11
    • Fix Version/s: None
    • Component/s: Packaging-Debian
    • Security Level: public
    • Labels:
      None
    • Environment:
      quad socket 80 core monster
      3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux
    • CPU Architecture:
      x86-64
    • Kernel:
      Linux
    • uname:
      3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux
    • Userland:
      GNU/Linux
    • Distribution:
      Debian
    • Distribution Version:
      Debian 8 jessie
    • lsb_release:
      Hide
      # lsb_release -a
      No LSB modules are available.
      Distributor ID: Debian
      Description: Debian GNU/Linux 8.6 (jessie)
      Release: 8.6
      Codename: jessie
      Show
      # lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 8.6 (jessie) Release: 8.6 Codename: jessie
    • Compiler Version:
      packages 1.6.1
    • FreeSWITCH GIT Revision:
      packages 1.6.11
    • GIT Master Revision hash::
      Git who?
    • FSS Support Agreement Customer Number and Company name:
      CounterPath

      Description

      Freeswitch restarted / restarts without core or other indication irratically once in a while over various times with minimal load at any point.

      Team suspects that systemd may be killing and restarting the process (because we cannot see anything else that is and this is not a core/crash).

        Activity

        Hide
        jimdoesvoip Jim OBrien added a comment -
        Suggestion from Dr Ken is to edit a line in /etc/systemd/system/multi-user.target.wants/freeswitch.service

        Steps:

        1) backup file to ~ or another director
        2) edit file to replace this line:

        LimitRTTIME=7000000

        with this line:

        LimitRTTIME=infinity

        3) Restart systemctl daemon

        systemctl daemon-reload

        4) Restart FreeSWTICH

        service freeswitch restart

        5) Wait to see if it is restarted.

        Show
        jimdoesvoip Jim OBrien added a comment - Suggestion from Dr Ken is to edit a line in /etc/systemd/system/multi-user.target.wants/freeswitch.service Steps: 1) backup file to ~ or another director 2) edit file to replace this line: LimitRTTIME=7000000 with this line: LimitRTTIME=infinity 3) Restart systemctl daemon systemctl daemon-reload 4) Restart FreeSWTICH service freeswitch restart 5) Wait to see if it is restarted.
        Hide
        jimdoesvoip Jim OBrien added a comment -
        Symptoms were:

        1) 3-5-7 minute gap in freewitch.log before restart

        2) all calls ended / hung / dropped

        3) freeswitch service restarted

        In journalctl logging you can see the evidence of the process being killed (by something??) and restarted:

        #journalctl | grep freeswitch

        Oct 12 11:27:25 fs1 systemd[1]: freeswitch.service: main process exited, code=killed, status=9/KILL
        Oct 12 11:27:25 fs1 systemd[1]: Unit freeswitch.service entered failed state.
        Oct 12 11:27:25 fs1 systemd[1]: freeswitch.service holdoff time over, scheduling restart.
        Oct 12 11:27:25 fs1 systemd[1]: Stopping freeswitch...
        Oct 12 11:27:25 fs1 systemd[1]: Starting freeswitch...
        Oct 12 11:27:25 fs1 freeswitch[7862]: 7863 Backgrounding.
        Oct 12 11:27:28 fs1 freeswitch[7862]: FreeSWITCH[7862] Waiting for background process pid:7863 to be ready.....
        Oct 12 11:27:28 fs1 freeswitch[7862]: FreeSWITCH[7862] System Ready pid:7863
        Show
        jimdoesvoip Jim OBrien added a comment - Symptoms were: 1) 3-5-7 minute gap in freewitch.log before restart 2) all calls ended / hung / dropped 3) freeswitch service restarted In journalctl logging you can see the evidence of the process being killed (by something??) and restarted: #journalctl | grep freeswitch Oct 12 11:27:25 fs1 systemd[1]: freeswitch.service: main process exited, code=killed, status=9/KILL Oct 12 11:27:25 fs1 systemd[1]: Unit freeswitch.service entered failed state. Oct 12 11:27:25 fs1 systemd[1]: freeswitch.service holdoff time over, scheduling restart. Oct 12 11:27:25 fs1 systemd[1]: Stopping freeswitch... Oct 12 11:27:25 fs1 systemd[1]: Starting freeswitch... Oct 12 11:27:25 fs1 freeswitch[7862]: 7863 Backgrounding. Oct 12 11:27:28 fs1 freeswitch[7862]: FreeSWITCH[7862] Waiting for background process pid:7863 to be ready..... Oct 12 11:27:28 fs1 freeswitch[7862]: FreeSWITCH[7862] System Ready pid:7863
        Hide
        silik0n Ken Rice added a comment -
        Commited to master (1.9) and 1.6 branch for inclusion in coming releases
        Show
        silik0n Ken Rice added a comment - Commited to master (1.9) and 1.6 branch for inclusion in coming releases

          People

          • Assignee:
            silik0n Ken Rice
            Reporter:
            jimdoesvoip Jim OBrien
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development