Massive memory drain on new install of FOP2

[mainenotarynet]

I had been toying with FOP2 and got the FULL license a few days ago, it works, but...

my application memory is now at 97% at all times -- I can get it back to 35% (where it always has been) by shutdown -r now for a reboot - but once FOP2 starts it jumps to 70% within seconds.

running latest fop2 with the FreePBXAdmin module, freePBX 2.9.0.7 Asterist (PBXinaFlash-Purple [*1.8.6-I think] with the IncrediblePBX feature set)

My memory has never been this high prior to FOP2. Any ideas on how to trace/fix this memory leak?

At about 90% you can't even log in anymore.

Kevin M Carman
Maine Notary Net

[nicolas]

Hi Kevin,

I have not experience that problem myself. Would you be able to let me access your server to investigate the issue? I am currently abroad, I will be back next friday, you can try to catch me on the live help.

[mainenotarynet]

After posting this issue I did a service fop2 stop and the memory went dow to 90% (from 97%) still way too high for normal then I did a amportal stop and checked in FreePBX and the memory was negligable. Then I did an amportal start (memory at 24% - usual norm) and restarted fop2 which increased memory to 31% this is OK but the memory creeps over time and when running the original fop the memory was usually steady around 35%.

I don't know enough of the intricacies of linux to track down the REAL cause but since the massive memory usage started when I began using the FULL version of FOP2 I figured this is the best place to start.

I will deal until I can catch you on LiveHelp as an amportal stop and start usually suffices to correct the problem in the meantime.

Also the FOP monitor shows WARN even though I did follow the instructions to monitor FOP2 instead - I must be doing something backwards.

Thanks again

[nicolas]

Hi,

Thanks for the feedback. You should disable FOP1 in /etc/amportal.conf and try not to change the amportal monitor scripts, modifying freepbx itself is not a good idea as it will break on any updates and you will have a really hard system in which to troubleshoot or work.

How are you starting fop2? From a modified amportal script? I strongly advice to revert your amportal script to the original and use fop2 init scripts to manage the service. I have seen some installations using the svc tool that are not well done, and they hammer your server trying to start fop2 every 5 seconds or so. I have no idea from where those instructions come from, but I have seen quite a few installations using that, and it does not really help.