Hi Brett,
Brett Nemeroff wrote: > Hello all, > I'm running out of shared mem in my opensips config. It runs fine for > a while with the exception that it spits out the following quite a > bit: > > Dec 14 16:41:42 opensips-a /usr/local/sbin/opensips[18058]: > CRITICAL:dialog:log_next_state_dlg: bogus event 8 in state 2 for dlg > 0x2af1d07f7208 [3823:215449753] with clid > '[email protected]' and tags > '141240091642563652734' '' > This means a non-ACK request was received for a dialog which was still in early state... > (same event and state for many many calls) > > Occasionally I also get: > Dec 14 15:17:42 opensips-a /usr/local/sbin/opensips[261217]: > ERROR:dialog:unset_dlg_profile: dialog was not yet created - script > error > And this one says you called "unset_dlg_profile()" for a request that has no dialog created. Looks more like a script error. > Dec 14 15:17:42 opensips-a /usr/local/sbin/opensips[261217]: > ERROR:dialog:w_unset_dlg_profile: failed to unset profile > Dec 14 15:17:43 opensips-a /usr/local/sbin/opensips[261220]: > ERROR:dialog:unset_dlg_profile: dialog was not yet created - script > error > Dec 14 15:17:43 opensips-a /usr/local/sbin/opensips[261220]: > ERROR:dialog:w_unset_dlg_profile: failed to unset profile > Dec 14 15:17:44 opensips-a /usr/local/sbin/opensips[261217]: > ERROR:dialog:unset_dlg_profile: dialog was not yet created - script > error > Dec 14 15:17:44 opensips-a /usr/local/sbin/opensips[261217]: > ERROR:dialog:w_unset_dlg_profile: failed to unset profile > Dec 14 15:17:46 opensips-a /usr/local/sbin/opensips[261219]: > CRITICAL:dialog:log_next_state_dlg: bogus event 8 in state 2 for dlg > 0x2b97849be698 [2558:1184219894] with clid > 'GW036bc28f221c2f127b6b40c257e > [email protected] and tags '141217091537558667203' '' > > Which I'm looking to resolve with some better checking of the dialog > before I unset it. > > > after running for some time (this box is running around 50-200 cps), I > eventually get out of memory errors.. first they look like: > Dec 14 15:17:28 opensips-a /usr/local/sbin/opensips[261219]: > ERROR:tm:sip_msg_cloner: no more share memory > Dec 14 15:17:28 opensips-a /usr/local/sbin/opensips[261219]: > ERROR:tm:new_t: out of mem > Dec 14 15:17:28 opensips-a /usr/local/sbin/opensips[261219]: > ERROR:tm:t_newtran: new_t failed > Dec 14 15:17:32 opensips-a /usr/local/sbin/opensips[261219]: > ERROR:tm:new_t: out of mem > (all of these messages repeat quite a bit) > > i have a core dump, but I'm not sure how useful it is for this kind of > problem. I'm not really sure where to troubleshoot, especially > considering the system load. > Enable the mem debugger (see http://www.opensips.org/Resources/DocsTsMem) and set memlog = 8 # we do not want mem logs memdump = 1 # we want to get the dumps. This conf will not produce any extra logging at runtime, but at SIGUSR1 or shutdown will generate a dump of memory status. Get this dump (via SIGUSR1 to the proc that reported the mem problem) and send it to me. Thanks and regards, Bogdan > Any ideas? > > Thanks, > Brett > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -- Bogdan-Andrei Iancu www.voice-system.ro _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
