They installed a system snapshot script to monitor the services, I then reported at the moment the spikes were happening. They used this information to check which service has been causing the issues.
Here's a ~15 minutes output
Code: Select all
00.log:Sat Jun 8 01:00:29 BST 2013 01 00 --> load: 0.57 0.41 0.41 1/311 546562
01.log:Sat Jun 8 01:01:38 BST 2013 01 01 --> load: 1.36 0.66 0.49 1/312 546911
02.log:Sat Jun 8 01:02:48 BST 2013 01 02 --> load: 5.20 1.69 0.85 1/359 547144
03.log:Sat Jun 8 01:03:57 BST 2013 01 03 --> load: 14.67 5.25 2.14 1/419 547273
05.log:Sat Jun 8 01:05:06 BST 2013 01 05 --> load: 9.61 5.83 2.58 1/356 547470
06.log:Sat Jun 8 01:06:16 BST 2013 01 06 --> load: 9.04 6.47 3.04 1/428 547687
07.log:Sat Jun 8 01:07:25 BST 2013 01 07 --> load: 10.28 7.34 3.58 1/537 547921
08.log:Sat Jun 8 01:08:43 BST 2013 01 08 --> load: 8.51 7.51 3.93 1/452 548095
11.log:Sat Jun 8 01:11:31 BST 2013 01 11 --> load: 22.58 17.20 8.37 1/558 548564
12.log:Sat Jun 8 01:12:41 BST 2013 01 12 --> load: 20.72 17.32 9.02 8/610 548797
13.log:Sat Jun 8 01:13:52 BST 2013 01 13 --> load: 7.25 13.97 8.46 1/453 548993
15.log:Sat Jun 8 01:15:01 BST 2013 01 15 --> load: 2.31 11.08 7.85 1/408 549170
16.log:Sat Jun 8 01:16:10 BST 2013 01 16 --> load: 1.15 8.89 7.33 1/380 549450
17.log:Sat Jun 8 01:17:19 BST 2013 01 17 --> load: 1.40 7.40 6.91 1/390 549709
Code: Select all
[root@417873901]cPs# grep lfd 02.log | wc -l
19
[root@417873901]cPs# grep lfd 03.log | wc -l
35
[root@417873901]cPs# grep lfd 05.log | wc -l
19
[root@417873901]cPs# grep lfd 06.log | wc -l
19
[root@417873901]cPs# grep lfd 07.log | wc -l
6
[root@417873901]cPs# grep lfd 08.log | wc -l
1
[root@417873901]cPs# grep lfd 11.log | wc -l
27
[root@417873901]cPs# grep lfd 12.log | wc -l
6
Does anyone have an idea as to what the issue might be?
Thank you,
Piers