You should check the opensips logs to check for the ERROR/CRITICAL messages that comes with the failure of OpenSIPS to start.

Some similar to the CRITICAL you mentioned in the prev posts.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
  https://www.siphub.com

On 31.05.2024 12:01, Sasmita Panda wrote:
[opensips] <defunct>     this is a line I am getting in between the services of opensips when opensips is not listening  .

Attached the logs with mem Debug as you mentioned .

*/Thanks & Regards/*
/Sasmita Panda/
/Senior Network Testing and Software Engineer/
/3CLogic , ph:07827611765/


On Thu, May 30, 2024 at 9:21 PM Bogdan-Andrei Iancu <[email protected]> wrote:

    Hi,

    Try to start opensips is mem debugging support - add "|-a
    Q_MALLOC_DBG" to the startup cmd line of OpenSIPS - this will give
    more hints on that crashing point.

    Regards,
    |

    Bogdan-Andrei Iancu

    OpenSIPS Founder and Developer
       https://www.opensips-solutions.com
       https://www.siphub.com

    On 27.05.2024 12:46, Sasmita Panda wrote:
    Hi ,

    I am just facing the same issue again .

    /usr/local/sbin/opensips[3443]: CRITICAL:core:fm_free: freeing
    already freed shm pointer (0x7f3a59ddb4a0), first free: (null):
    (null)(0) - aborting!

    whenever I am starting opensips this is the last line I am
    getting in the logs and it wont listen on the specified port .


    As earlier suggested I was trying to run a trap with opensips-cli
    , but I am facing an issue with that . It says the trap module is
    not loaded .
    How do I load the trap module of opesnips-cli specifically ?

    Please help . This is a kind of blocker for me .





    */Thanks & Regards/*
    /Sasmita Panda/
    /Senior Network Testing and Software Engineer/
    /3CLogic , ph:07827611765/


    On Thu, Mar 21, 2024 at 10:01 PM Bogdan-Andrei Iancu
    <[email protected]> wrote:

        IF

        (a) it crashes, try to get a backtrace

        (b) it block on starting, try to do a "trap" via opensips-cli

        Regards,

        Bogdan-Andrei Iancu

        OpenSIPS Founder and Developer
           https://www.opensips-solutions.com
           https://www.siphub.com

        On 21.03.2024 08:24, Sasmita Panda wrote:
        Sometimes it crashes and sometimes while starting I get the
        warings of the timer . Same config  shows different issues .



        */Thanks & Regards/*
        /Sasmita Panda/
        /Senior Network Testing and Software Engineer/
        /3CLogic , ph:07827611765/


        On Wed, Mar 20, 2024 at 6:45 PM Bogdan-Andrei Iancu
        <[email protected]> wrote:

            Hi,

            How the two reports fit together here ? there are
            completely separate experiences on different runs?? or
            if you start opensips first you get the warnings and
            later it crashes ??
            For the crash part, I see a core file was generated -
            could you extract the backtrace and post here ? (see
            https://opensips.org/Documentation/TroubleShooting-Crash)

            Regards

            Bogdan-Andrei Iancu

            OpenSIPS Founder and Developer
               https://www.opensips-solutions.com
               https://www.siphub.com

            On 11.03.2024 15:04, Sasmita Panda wrote:
            Any update on this ?


            */Thanks & Regards/*
            /Sasmita Panda/
            /Senior Network Testing and Software Engineer/
            /3CLogic , ph:07827611765/


            On Mon, Mar 11, 2024 at 12:03 PM Sasmita Panda
            <[email protected]> wrote:

                With the same server configuration and opensips
                version I am getting below error as well .

                CRITICAL:core:fm_free: freeing already freed shm
                pointer (0x7fc110e0b408), first free: (null):
                (null)(0) - aborting!

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to