Wiki source code of High CPU Usage or Call Quality Issues
Last modified by Scott Gagan on 2021/09/10 22:40
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | == Problem == | ||
2 | |||
3 | If iSymphony is using excessive amounts of CPU time, or is affecting call quality on the system it's installed on, here are a few things to check before opening a ticket with us. | ||
4 | |||
5 | == Troubleshooting == | ||
6 | |||
7 | 1. Ensure that the hardware installed in the system running iSymphony is reasonably close to our [[Hardware Requirements>>doc:ISYMDOCS.iSymphony Requirements]]. It doesn't need to exactly meet the recommendations, due to the inherent variability in requirements, but it should be close. | ||
8 | 1. If you are using call detail records in MySQL, ensure that you have applied the [[index fix for the CDR database>>doc:iSymphony Knowledge Base.Browse Articles by Page Tree Hierarchy.Crashes and Performance Issues.High CPU Usage or Call Quality Issues.Missing MySQL CDR Index.WebHome]]. | ||
9 | 1. Check the iSymphony log files for errors that may be related. See [[doc:iSymphony Knowledge Base.Browse Articles by Page Tree Hierarchy.Error Messages In Logs.WebHome]] for details on checking the iSymphony logs, and look for one of these specific messages that may cause high CPU usage: | ||
10 | 11. [[doc:iSymphony Knowledge Base.Browse Articles by Page Tree Hierarchy.Error Messages In Logs.java\.lang\.OutOfMemoryError\: Java heap space.WebHome]] | ||
11 | 11. [[doc:iSymphony Knowledge Base.Browse Articles by Page Tree Hierarchy.Error Messages In Logs.java\.lang\.OutOfMemoryError\: unable to create new native thread.WebHome]] | ||
12 | |||
13 | == Further Support == | ||
14 | |||
15 | If you've checked the above items, and you're still having resource usage or call quality issues, feel free to open a ticket including the following information: | ||
16 | |||
17 | 1. The symptoms you're experiencing (e.g. high cpu usage, high network traffic, call quality issues, etc), including how frequently they happen. | ||
18 | 1. ((( | ||
19 | The output of the following commands: | ||
20 | |||
21 | {{code}} | ||
22 | $ cat /proc/cpuinfo | ||
23 | $ free -m | ||
24 | $ ps aux | grep -e "java.*isymphony3" | ||
25 | {{/code}} | ||
26 | ))) | ||
27 | 1. All files in /opt/isymphony3/server/log. | ||
28 | 1. All files in /opt/isymphony3/server/conf. | ||
29 | 1. Approximately how much call traffic does this phone system handle (calls per day, simultaneous calls, etc)? | ||
30 | 1. If you are using queues on this phone system, | ||
31 | 11. How many queues are running on the system (even if they aren't licensed in iSymphony)? | ||
32 | 11. How many agents are logging into queues at a time? | ||
33 | 11. What ring strategy are you using for your queues? | ||
34 | 1. If you can catch the system while it is lagging for additional information, include the following as well: | ||
35 | 11. A screenshot of the top command while the issue is occurring. | ||
36 | 11. ((( | ||
37 | The output of these commands: | ||
38 | |||
39 | {{code}} | ||
40 | $ netstat -lanp | grep 5038 | ||
41 | $ netstat -lanp | grep 50000 | ||
42 | $ cat /proc/`cat /opt/isymphony3/server/iSymphonyServer.pid`/stat | ||
43 | {{/code}} | ||
44 | ))) | ||
45 | |||
46 | == Related articles == | ||
47 | |||
48 | |||
49 | |||
50 | {{contentbylabel spaces="" showLabels="false" reverse="true" sort="modified" max="5" labels="kb-troubleshooting-article" showSpace="false" type="page"/}} |