asterisk crashing with latest version

› VitalPBX Community Support › General Discussion › asterisk crashing with latest version

  • Post
    • January 18, 2019 at 11:13 am
    dsmagghe
    Participant
    Up
    0
    Down

    Hello multiple times a day we have an asterisk restart.

    Following message to be found in /var/log/messages

    Jan 18 11:16:46 voip01 kernel: asterisk[10235]: segfault at 30 ip 00007f9a98087d38 sp 00007f99e36f9a90 error 4 in libasteriskpj.so.2[7f9a98012000+152000]
    Jan 18 11:16:47 voip01 systemd: asterisk.service: main process exited, code=killed, status=11/SEGV
    Jan 18 11:16:47 voip01 systemd: Unit asterisk.service entered failed state.
    Jan 18 11:16:47 voip01 systemd: asterisk.service failed.
    Jan 18 11:16:47 voip01 vpbx: The Asterisk Manager Connection was closed
    Jan 18 11:16:47 voip01 vpbx: Shutting down server on port 0.0.0.0:3000
    Jan 18 11:16:47 voip01 vpbx: Shutting down server on port 0.0.0.0:3005
    Jan 18 11:16:48 voip01 systemd: asterisk.service holdoff time over, scheduling restart.
    Jan 18 11:16:48 voip01 systemd: Starting Asterisk PBX…
    Jan 18 11:16:48 voip01 asterisk: Setting max files open to 20000
    Jan 18 11:16:50 voip01 vpbx: Restoring connection to Asterisk
    Jan 18 11:16:50 voip01 vpbx: Server up and running at host 0.0.0.0 and port 3000
    Jan 18 11:16:50 voip01 vpbx: Secure Server up and running at host 0.0.0.0 and port 3005
    Jan 18 11:16:51 voip01 asterisk: #033[0mUnable to load config file ‘stasis.conf’
    Jan 18 11:16:51 voip01 asterisk: Could not load Stasis configuration; using defaults

     

    running vital version 2.1.1-1

    asterisk 13.23.1 on centos 7.4

    this machine didn’t have the issue on the previous version of vital , so I’m guessing it has to do with the latest update. We currently not use pjsip so I wonder if we could turn it off somewhere to avoid restarting the PBX .. ?

    0
Viewing 3 replies - 1 through 3 (of 3 total)
  • Replies
    • January 18, 2019 at 2:49 pm
    Jose Miguel Rivera
    Keymaster
    NI
    Up
    0
    Down

    I just want to clarify that this issues is not related to the latest version of VitalPBX, we have the same version in our company and others, and we don’t have any inconvenience.

    Now, regarding to your issue, try to do the following:

    • Stop VPBX Monitor service: systemctl stop vpbx-monitor.service
    • Try to install any other update of asterisk: yum update asterisk*
    • Restart the asterisk: systemctl restart asterisk
    • Start VPBX Monitor: systemctl start vpbx-monitor.service
    0
    • January 21, 2019 at 10:21 am
    dsmagghe
    Participant
    Up
    0
    Down

    Hello

     

    did that

    still getting:

    asterisk[18155]: segfault at 30 ip 00007f6ab66dcd38 sp 00007f6a0268ba90 error 4 in libasteriskpj.so.2[7f6ab6667000+152000]

    it stops and restarts within a couple of seconds , but it is a hell since all queues are emptied.

    I saw hardware errors on different forums, but since it is a virtual pachine I don’t think that is causing the error. Could I somehow disable pjsip get back to chan_sip since it is always in this module that asterisk crashes? If so, how can I do that?

    0
    • January 21, 2019 at 1:57 pm
    Jose Miguel Rivera
    Keymaster
    NI
    Up
    0
    Down

    I think this procedure may fix the issue:

    • rm -rf /usr/lib64/asterisk/modules
    • yum reinstall asterisk*
    • systemctl restart asterisk

    Let me know if that fixed the issue

    0
Viewing 3 replies - 1 through 3 (of 3 total)
  • The forum ‘General Discussion’ is closed to new topics and replies.