We started rolling out SNG7/FBX14 systems recently and have noticed that so far, the few we’ve rolled out all have extreme lag (5-10 minutes or so) when doing a rebuild the extensions in EPM. This has been observed on systems with 5 extension and 15 extensions. The system appears to be “locked up” during the rebuild, and then after time passes it will “finish” and everything back to normal.
If I do the rebuild via CLI (fwconsole epm rebuildupdate TEMPLATENAME) it rebuilds in a normal amount of time.
I’ve had TOP running in a SSH session when doing the above laggy rebuilds and see that Apache consumes almost all the CPU during this entire “lag session”. When doing the rebuild via command line, top only shows PHP using about 2/3 CPU for the “normal” amount of time to rebuild (5-10 seconds).
I do NOT have Extension Mapping IP or Status enabled in Globals.
This does not happen on any of the FPBX 13 systems I have out there. It does happen on all of the 4 systems on FBX 14 I have out there. All of these systems were clean installs, not in-place upgrades nor were they “migrated” or restored systems using the tool/backups.
100% Sure. I did some digging in the forums here first and saw a thread with that mentioned and thought it was my salvation, when I went to check, i saw they were both already marked disabled anyway (on all systems in discussion).
That’s not strange at all. When you are doing things via the CLI you are running them at the system level. When you are going them via the GUI you have the browser and the web server “in between” so the browser is going to send the request, deal with any of the JS or client side code execution while Apache is going to take that information and pass it through to the system (PHP parser, etc). If the script takes longer than the browser would like for a response back to its request it can lag out or be unresponsive.