• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 270
  • Last Modified:

Linux TOP Command processes - Normal or not?

Hi all - I am trying to troubleshoot a problem with 1 web server (Linux/Apache/MySql/PHP). Having isolated the issue,
I setup a test server to duplicate the problem, and added just the 1 user that runs php scripts and a MySQL DB. (that user does *not* have access to this test server). I ran some of his scripts, then stopped them, then Rebooted this test server.

Attached is a screen-shot of a Linux "top" command that I did *after* rebooting the Server.
I am not sure how to troubleshoot from here. What I am questioning on the "top" command is:
- mysql/mysqld is running ... and says "194% of CPU Utilization
- Multiple occurances of that user named "romancer" that keep appearing & disappearing. "romancer" is a legitimate customer, but after a Reboot, per the attached "top" command, seems to still be using server resources.
(FYI, that "dd-agent" is from DataDog server monitor that I added after the problem occurred to help me troubleshoot)

Any suggestions anyone? Thanks all in advance !!
- B
0
bleggee
Asked:
bleggee
  • 2
1 Solution
 
Jan SpringerCommented:
I don't see the attachments but that certainly doesn't sound normal.
0
 
gr8gonzoConsultantCommented:
1. Does romancer have any cron jobs set up that might start a process automatically, even after a reboot?

2. Sounds like a script or a query that isn't optimized. You could enable slow query logs and see whether he's running a bad or unindexed heavy query.

3. Spikes of 194% CPU usage aren't unusual. Hyperthreading and multiple virtual cores can easily lead to CPU usage over 100%, but if it's occurring all the time to the point of impacting other customers or other server applications, then it may be a problem.
0
 
bleggeeAuthor Commented:
Here's that Screen Shot attachement ...
top-for-ee.jpg
0
 
gr8gonzoConsultantCommented:
So it definitely looks like a correlation between a script running and the database usage. I'd definitely enable the slow query log, check the web server access log, and try to trace back the queries to a particular script to see what's going on.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now