Fop2 crashes apache/asterisk

[bosticka]

Hi,

I have been using fop2 for a couple weeks now and it is a great product for sure.

My company runs a call center and we use the panel to monitor calling queue size, wait times, etc.

However, I recently enabled more users to view the panel so everyone can monitor the queue themselves. We at most will have 4 or 5 agents logged in to one queue and on the fop2 panel as well, plus 1 or 2 managers watching the panel.

On Monday, our freepbx installation hung hard twice in the same day for the first time ever. This is a server that has been rock solid for over 6 months. Tuesday it hung twice again. A quick restart brings everything back to normal.

I disabled the fop2 panel today and we are back to running without problems.

The asterisk logs don't show anything crazy from what I can tell. However, for two of the 4 crashes I saw this message in the apache error_log:

server reached MaxClients setting, consider raising the MaxClients setting

The http MaxClients is set to the default 256 for Centos 5. Also when the crash occurs, FreePBX shows Error next to Web Server on the System Status home page.

Has anyone experienced anything similar? How much stress does fop2 place on a system with 40 to 50 ip phones registered and 20 to 25 active calls? Is 5 to 6 ppl on the panel too many?

Any guidance would be great!

Thanks,
Aaron Bostick

[nicolas]

Hi Aaron,

FOP2 does not hit on apache in any particular way, as it does not use http for retrieving status but its own socket connection.

It seems you have an issue with the FreePBX monitoring daemon that is perhaps hitting apache more than it needs to?

Check your apache log and see WHAT files are being requested, what is the referrer, etc. That will give you more ideas on what to check/look for. You might want to disable FOP1 for example, FreePBX has a check for it and if you go with fop2 you do not need fop1 nor the freepbx checks anymore.

Best regards,