OTRS Jumpbox - Apache

Jumpbox Version 1.1.15
JumpBox Platform Version: 1.1-247
OTRS Version: 2.4.7

Today our OTRS Jumpbox has been running quite slowly - often taking 10's of seconds to load a new page when a link is clicked.
I logged in via SSH and ran "top"
There is a process that is using 97% or more CPU (it fluctuates).

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4984 www-data 20 0 401m 175m 4792 S 99.7 8.6 76:50.65 apache2

Any ideas on the cause? Or a solution?

I should note that I've

I should note that I've rebooted the server 3 times today, and each time, it quickly goes back into this state - within 5 minutes.

OTRS Jumpbox - Apache

Have you checked log files? Apache has logfiles in /var/log/apache2/ and there may be OTRS specific logs elsewhere, perhaps in /var/log/SOMETHING. It doesn't look like there should be OTRS logs elsewhere, though its possible.

Does it look like MySQL is busy too?

Austin

MySQL was not among the top

MySQL was not among the top items in the "top" display.

The OTRS SysLog (available through the OTRS interface) was showing no errors while the problem was happening. I'm wondering if perhaps it was simply internet traffic attempting to access the server.

I can't see any major errors in the Apache error log. And the condition is not happening right now. If I see it again, I'll have to dive into the logs as it's happening.

Looking at the Apache error log, I see a lot of this warning:
[warn] RSA server certificate CommonName (CN) `jumpbox.local' does NOT match server name!?

Can you change the "It just works" SSL setting so we can change the CommonName of the certificate? Is that even possible?

MySQL was not among the top

This issue is one of those that will just take a lot of looking. Its possible that there is a query thats taking a longtime or something. You can look at the active queries once you get a MySQL username and password (http://wiki.jumpbox.com/doc/runtime/faq/access_mysql)

mysqladmin -u USER -pPASSWORD processlist

Other than that, its just going to be checking logs. I dont know how well constrained your user population is, but you could write firewall rules to prevent malicious IPs from accessing you.

Austin