Hi Duane,

actually, checking the dump you sent, I see no trace of a leak - the pkg dump shows only script and DB conn mem, while the shm is empty.

So, in your case, you may have a memory overload because because of runtime issues (but not a leak). If dialogs are not removed by BYEs, I guess you end up with TONS of dialogs in memory... dialog stuff is not releated to USRLOC at all....maybe the BYEs are not going trough loose_route() in script and not pushed for dialog matching

Regards,
Bogdan

Duane Larson wrote:
After looking a little more do you think this would cause the memory issue...

Looks like my SIPP test starts the call, does whatever I want and sends the BYE, but the dialog is still in the database after the call has ended between the UAS and UAC. I am currently using USRLOC db_mode = 2, so I am wondering if the dialogs are all just staying in memory. Not sure why my SIPP xmls or OpenSIPS config is not allowing the dialog to end in OpenSIPS

On Thu, Jan 20, 2011 at 2:07 PM, Duane Larson <[email protected] <mailto:[email protected]>> wrote:

    I do have some memory stuff in syslog.  I have posted the output here
    http://paste.ubuntu.com/556285/




    On Thu, Jan 20, 2011 at 4:13 AM, Bogdan-Andrei Iancu
    <[email protected] <mailto:[email protected]>> wrote:

        Hi Duane,

        with

             mem_log=10
             mem_dump=1
             debug=3

        do you see at runtime any logs related to memory ?? (alloc,
        dealloc logs, no error) . Normally you shouldn't see
        any....only when a me dump is done (at shutdown for example).

        Regards,
        Bogdan

        Duane Larson wrote:

            I am trying to stress test my opensips config with SIPP
            but was seeing that after running it for a while I would
            start getting failed calls and eventually opensips would
            die.  I recompiled opensips by following

            http://www.opensips.org/Resources/DocsTsMem

            I also added the following to the config
                  mem_log=10
                  mem_dump=1
                  debug=3


            Now when I try and start OpenSIPS it dumps a TON of stuff
            to syslog.  I do a ps -ef and there is one opensips
            process running for a while and then it dies.  Before I
            started opensips my memory was at about
            1500000k
            then when I started opensips it started going down to
            1400000k

            When the single opensips process finally dies the memory
            never comes back.  I am not sure what I need to do next in
            order to find out where the issue is.
            
------------------------------------------------------------------------

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


-- Bogdan-Andrei Iancu
        OpenSIPS Event - expo, conf, social, bootcamp
        2 - 4 February 2011, ITExpo, Miami,  USA
        OpenSIPS solutions and "know-how"


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




-- --
    *--*--*--*--*--*
    Duane
    *--*--*--*--*--*
    --




--
--
*--*--*--*--*--*
Duane
*--*--*--*--*--*
--
------------------------------------------------------------------------

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


--
Bogdan-Andrei Iancu
OpenSIPS Event - expo, conf, social, bootcamp
2 - 4 February 2011, ITExpo, Miami,  USA
OpenSIPS solutions and "know-how"


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

Reply via email to