Re: [Kamailio-Users] Can openser.cfg lead to pkg memory problem?

Hello, we have openser 1.3.3 running in production (current rev.: 4943). For 3 times in 50 days we had to restart openser to correct pkg memory problem.

After some time logging messages like this: /openser.log:Aug 19 10:39:18 ipx022 /usr/local/sbin/openser[16991]: ERROR:core:new_credentials: no pkg memory left, openser will eventually run out of pkg memory and refuse all subsequent requests. We are trying to recreate this in our lab so that we can follow memory troubleshooting instructions at http://kamailio.net/dokuwiki/doku.php/troubleshooting:memory, but so far we were unable to do it even when generating millions of calls and registration transactions (we are using SIPp to generate normal call flows and even abnormal call flows detected when reading openser.log, like 'invalid cseq for aor', malformed SIP messages etc).

And this is much more than in our production environment, with just 600 subscribers and about 2000 calls a day. The frequency the problem happens is increasing with the number of subscribers, so we are performing periodic restart of openser (actually, what we do is to switch over to the standby server). We already recompiled openser with pkg memory pool size set to 4MB so that this will not have to be done frequently. Since we cannot recreate this in our lab, we suspect there is a situation happening in production that might not be having been properly handled by openser.cfg. So my question is: would it be possible to an overlooked detail in openser.cfg to cause pkg memory problem? In case someone could take a look at it, here's our cfg file: