After updating some modules recently (I can’t pinpoint exactly which ones because I did a few at a time) my FreePBX web GUI and asterisk system itself are slow. The GUI problem is self explanatory, but the phone system is slow to respond to call recording requests and remote extension pickups at a client level. Stopping and starting services also appears to happen much slower than it did before. At first I though it was an iSymphony/Java issue but now I’m finding that MySQL may be the culprit. I’m seeing a lot of processes in htop that look like this:
Definitely have rebooted multiple times. I have gone down multiple paths of troubleshooting, including updating SysAdmin, reinstalling node.JS, disabling unused modules, repairing all MySQL databases, and applying new updates that have come out since. There appears to be high CPU activity on this 8 core server
We do all of our development on “generally unimpressive” virtual machines with terrible specs to make sure we work everywhere. I have FreePBX running on an Intel Edison. So a more powerful server should be super happy. Can you pastebin the output of top
Yes, however I’ve tried stopping the service and the same slowness persists. The only thing I haven’t tried with iSymphony is stopping the service and then rebooting. iSymphony doesn’t believe it’s their issue (of course )s
researched my recent error and found that it’s a security feature:
"This is not a bug, it is a design issue. It is also possible to prevent your program being traced by using Linux specific prctl call and clear PR_SET_DUMPABLE flag, which OpenSSH agent in your system already does.
But, not many programmers aware of this behaviour. So, when looking at the Linux distributions perspective, it is good to activate additional protection mechanism on ptrace system call to make more secure system without need to change of any software code.
Newer Linux kernels has the Yama security module. When the Yama is built into the kernel, its behaviour can be changed through /proc/sys/kernel/yama/ptrace_scope file.
If you’re trying to use strace to attach another process which is also belongs to you but you’re not a parent of it and the value in ptrace_scope file greater than 0, it is normal to get “Operation not permitted” error.
Some recent Linux distributions sets ptrace_scope value to 1 in default. You can still use strace in this scenario with starting the programs with strace like below:
$ strace ./my_prog
but you can not attach a process which is already started and has different parent of your newly executed strace.
I wasn’t able to determine the root cause of events/0 hanging up, but I did research wanpipe issues on PRI cards and performance loss. I believe i resolved the performance issue by adding the following parameters to /etc/grub.conf: “apic=on” & “acpi=off” and installing/starting the IRQ Balance addon. The IRQ Balance addon appears to have increased buffered and cached disk reads on /dev/sda by 3-4 times. Thanks guys,
Well, in response to my own post I’m going to recommend that you NOT add “apic=on” and "acpi=off to your grub config file. The first reboot after adding this to the configuration resulted in kernel not loading. I’ve since removed it.