Ovidiu Sas wrote: > Yes, it seems that you are running out of SHM memory. > Check with top how much memory are you using right after the server is > started and the when it is loaded. > Also check if the memory utilization is increasing in time. If yes, > then you are edaling with a memory leak.
If openser's leaks shared memory you can not see it with top. AFAIK openser allocates all the shared memory on startup. klaus > > Regards, > Ovidiu Sas > > On Tue, Nov 18, 2008 at 7:31 PM, joy yue <[EMAIL PROTECTED]> wrote: >> >> On 11/18/08, Ovidiu Sas <[EMAIL PROTECTED]> wrote: >>> I ran on 32bits with 1G and 4k simultaneous transactions. >>> Most of the memory is taken by the carrierroute module (big routing >>> tables). >>> 2G should be more then enough for what you need. >>> >>> You didn't specified what kind of "out of memory" do you get: SHM or PKG? >> How can I check the memory usage in openser? >> In my case, it looks openser is out of SHM to me. Here is the error message >> I got: >> >> Nov 18 17:21:12 paecongo /opt/openser/sbin/openser[2548]: >> ERROR:tm:t_newtran: new_t failed >> Nov 18 17:21:12 paecongo /opt/openser/sbin/openser[2570]: >> ERROR:tm:relay_reply: no more share memory >> Nov 18 17:21:12 paecongo /opt/openser/sbin/openser[2568]: >> ERROR:tm:relay_reply: no more share memory >> Nov 18 17:21:12 paecongo /opt/openser/sbin/openser[2578]: ERROR:tm:new_t: >> out of mem >> Nov 18 17:21:12 paecongo /opt/openser/sbin/openser[2554]: ERROR:tm:new_t: >> out of mem >> Nov 18 17:21:12 paecongo /opt/openser/sbin/openser[2579]: ERROR:tm:new_t: >> out of mem >> Nov 18 17:21:12 paecongo /opt/openser/sbin/openser[2573]: ERROR:tm:new_t: >> out of mem >> Nov 18 17:21:12 paecongo /opt/openser/sbin/openser[2578]: >> ERROR:tm:t_newtran: new_t failed >> >> Thanks, >> -Joy >> >>> Regards, >>> Ovidiu Sas >>> >>> On Tue, Nov 18, 2008 at 5:52 PM, Klaus Darilion >>> >>> <[EMAIL PROTECTED]> wrote: >>>> joy yue wrote: >>>>> >>>>> On 11/18/08, *Klaus Darilion* <[EMAIL PROTECTED] >>>>> <mailto:[EMAIL PROTECTED]>> wrote: >>>>> >>>>> joy yue wrote: >>>>> >>>>> >>>>> >>>>> >>>>> On 11/18/08, *Klaus Darilion* <[EMAIL PROTECTED] >>>>> <mailto:[EMAIL PROTECTED]> >>>>> <mailto:[EMAIL PROTECTED] >>>>> <mailto:[EMAIL PROTECTED]>>> wrote: >>>>> >>>>> joy yue wrote: >>>>> >>>>> >>>>> Hi Folks, >>>>> >>>>> I get out-of-memory error with openser1.3 version. As I >>>>> already >>>>> increase the share memory size to 2G, looks like the >>>>> only >>>>> choice >>>>> is to compile openser as 64-bit binary. Before I go >>>>> further, I'd >>>>> like to check if anyone has experience in this. Does >>>>> OPenser >>>>> work with 64-bit binary? >>>>> >>>>> >>>>> >>>>> Maybe you are triggering a bug in openser and leaking >>>>> memory. I >>>>> think it would be better to debug why you are running out of >>>>> memory. >>>>> http://kamailio.org/dokuwiki/doku.php/troubleshooting:memory >>>>> >>>>> >>>>> It doesn't look like memory leak. With lower load, openser runs >>>>> fine without the out-of-memory error. >>>>> >>>>> >>>>> Hi! >>>>> >>>>> (please cc the list) >>>>> >>>>> So how much traffic is on your openser? (registrations per seconds, >>>>> transactions per seconds ...) >>>>> >>>>> Maybe it leaks only under heavy load? (e.g.race conditions?) >>>>> >>>>> >>>>> The traffic is around 18k transaction/sec. How much memory is needed >>>>> for one transaction? >>>> Thats really heavy load - maybe someone of the core guys knows how many >>>> memory is needed per transaction >>>> >>>> klaus >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> [email protected] >>>> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >>>> >> _______________________________________________ Users mailing list [email protected] http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
