On 13 April 2011 21:06, Florin Andrei flo...@andrei.myip.org wrote:
Running v5 64bit on a Dell 1950.
/var/log/messages was full of ntpd[7313]: frequency error -1707 PPM
exceeds tolerance 500 PPM messages. There was a lot of messages about
the system limit for the maximum number of semaphore
I was wondering if you have normal internet access on that machine. I
found out that somehow systems I set up just freeze and are horribly
slow when there is no internet access. Terminnal would take few minutes
to open, and if I try several terminals all would open at once once
system is
Running v5 64bit on a Dell 1950.
A cluster of 3 DB machines, identical hardware. One of them suddenly
became slower 2 weeks ago.
tar -zxf with a large file on this machine takes 1.5 minutes, but takes
only 10 seconds on any of its siblings. CPU usage seems high while
untarring, with lots of
centos-boun...@centos.org wrote:
Running v5 64bit on a Dell 1950.
A cluster of 3 DB machines, identical hardware. One of them suddenly
became slower 2 weeks ago.
snip proof the overall system is slow
snip proof that the CPU is not the problem
/var/log/messages was full of ntpd[7313]:
On Wed, 2011-04-13 at 13:06 -0700, Florin Andrei wrote:
Running v5 64bit on a Dell 1950.
A cluster of 3 DB machines, identical hardware. One of them suddenly
became slower 2 weeks ago.
tar -zxf with a large file on this machine takes 1.5 minutes, but takes
only 10 seconds on any of its
On 04/13/2011 01:34 PM, Cal Webster wrote:
tar -zxf with a large file on this machine takes 1.5 minutes, but takes
only 10 seconds on any of its siblings. CPU usage seems high while
untarring, with lots of user and sys cycles being used, but almost no
wait cycles. It doesn't matter whether I
On 04/13/2011 01:55 PM, Benjamin Franz wrote:
1) Are you untarring from *and* to the SAN volume or is the source on
the local volume?
Source on SAN, destination on SAN. Still slow.
--
Florin Andrei
http://florin.myip.org/
___
CentOS mailing list
On 04/13/2011 01:16 PM, Brunner, Brian T. wrote:
Any RAID setups go into self-repair mode?
No RAID here, just LVM - not too different from the default redhat-style
setup of the system drives (except the additional SAN stuff and DB).
Anyway, if the drives are the cause, then riddle me this:
Maybe check /proc/interrupts ?
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
9 matches
Mail list logo
