Hi all,
Downloaded SNG7-FPBX-64bit-1710-1 (Release Date: October 2017 FreePBX 14.0.1.20 • Linux 7.4 • Asterisk 13, 14 or 15) and had it running around a week but noticing that it gets slower and slower by the day.
A few days ago I noticed that logging into the web interface was slow, taking around 60 seconds, checking the system with top and I could see http and php processes hitting 100% CPU utilisation for a while, so previous system load was around 0.10 and after a few minutes trying to login load went up and got as high as 10.0 which then started to affect calls, jittering, etc.
I rebooted the box and immediately it was fine once again, load stayed low, web interface responsive, etc.
Move forward to now (after the weekend) and again very slow, logging into the web interface took a long time, too long as I then got a DHTML warning banner saying it couldn’t connect to the backend, checking the server and load was climbing rapidly and calls were timing out (I tried dialling voicemail and my handset just hung trying to get a reply from the server).
Again I rebooted and all was fine once again, low load, web interface fine and calls fine. Right now after around 1hr the system still looks good, load at 0.02, 0.04, 0.05 and calls processing happily.
This system was replacing a much older trixbox/freepbx system, so load, etc, hasn’t gone up and resources almost identical.
I suspected hardware issues also, this runs under vmware esxi (5.5.0, 2068190) on a Dell PowerEdge R310 4x2.393Ghz Xenon CPUs, 16Gb RAM.
The VM running SNG7 has all 4 CPUs and 10Gb RAM allocated to it, there is only one other machine on the vm box running less resources and that does NOT have the same issues, so I suspect ruling out hardware (Disk arrays fine, all disks fine, etc)
I’ve allocated 2x200Gb disks to the VM and the SNG7 install automatically has put those into a raid array:
md0 : active raid1 sda1[0] sdb1[1]
2046976 blocks super 1.2 [2/2] [UU]
bitmap: 0/1 pages [0KB], 65536KB chunk
md1 : active raid1 sda2[0] sdb2[1]
207535104 blocks super 1.2 [2/2] [UU]
bitmap: 1/2 pages [4KB], 65536KB chunk
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/SangomaVG-root 193G 5.5G 188G 3% /
devtmpfs 4.8G 0 4.8G 0% /dev
tmpfs 4.9G 16K 4.9G 1% /dev/shm
tmpfs 4.9G 8.6M 4.8G 1% /run
tmpfs 4.9G 0 4.9G 0% /sys/fs/cgroup
/dev/md0 1.9G 62M 1.8G 4% /boot
tmpfs 984M 0 984M 0% /run/user/0
BUT when there are issues with high CPU, etc, the processes aren’t in “D” state so it doesn’t appear to be the disk array/raid slowing it down.
I’m a bit stumped to be honest what is causing the slowdown as it doesn’t appear to be physical, nor resources on the machine but it just keeps slowing down.
I’ve checked the modules update and it is saying a module update:
sangoma-pbx.noarch 1710-2.sng7 1710.1.sng7
sangoma-release.x86_64 7-4.1710.02.el7.sangoma 7.4.1710.01.el7.sangoma
But I can’t find any release info on 1710-2.sng7 to find what difference there is or bug fixes, etc, so I’m reluctant to do the upgrade without more info (BTW this box is now live unfortunately so I need to figure the fix out quick!)
Can anyone suggest other diagnostic steps, how to resolve, etc please?
Thank you!