exec_avp issue

I have openSER calling scripts using exec_avp(), and setting AVPs using standard output from the script like this:

$avp(s:siaaID) = "0";
$avp(s:destAddr) = "0";
$avp(s:sStatus) = "0";

exec_avp("mono
/usr/local/src/openSERMono/openSER.exe start","$avp(s:siaaID),$avp(s:destAddr),$avp(s:sStatus)");


This works fine for 24 - 48 hours, after which the scripts continue to run fine but the AVPs are no longer set. The enviromental variables passed to the script are still being passed and the script is executing just fine, but the AVPs that were being set the first 24-48 hours remain "0"s.

I thought maybe it was the total open_files_limit but I changed its value to 10000 in both the command line and openser.cfg and it made no difference.

What could be causing exec_avp to stop functioning correctly after a certain period of time?

what output do you get with debug=9? How many open files at an OS level?

I set the OS open files limit to 10000 and openSER to 10000 and it didn't fix the issue or lengthen the time exec_avp() worked properly.

I'm setting it up to spit the debug output into a file so I can see. It takes about a day to stop working right.

Here is debug=9 output:

Apr 3 16:01:42 [1943] ERROR:core:pv_set_avp: error - cannot add AVP
Apr 3 16:01:42 [1943] ERROR:core:do_assign: setting PV failed
Apr 3 16:01:42 [1943] ERROR:core:do_assign: error at line: 90
Apr 3 16:01:42 [1943] ERROR:core:add_avp: no more shm mem

The issue looks to be that after 24 hours shm mem runs out and no more AVPs are created.

The fact that it works for 24-48 hours before showing these memory errors leads me to believe its a memory leak.

Right now I restarted openSER like this: 'openser -m 256'

This should increase the shared mem size to 256 megabytes.

What was the default shared memory size?

If this is a memory leak whats the best way to submit a bug report?

the default is 32 iirc. It does look like the memory isn't being released. I'd file a bugreport on the sourceforge site, stating as much info as you can collect (after searching existing bug reports first). Also, if you are not running the latest stable release, I'd check the changelogs for fixes to this problem.

x-console :

the default is 32 iirc. It does look like the memory isn't being released. I'd file a bugreport on the sourceforge site, stating as much info as you can collect (after searching existing bug reports first). Also, if you are not running the latest stable release, I'd check the changelogs for fixes to this problem.

I'll check sourceforge and post if I need to.

You said 32 iirc is the default - what does 32 iirc mean? Is that 32 megabytes?

iirc = if i recall correctly

yes 32 meant 32 meg.