Checking a slow server.

[Down2TheC]

Everything on my VPS server is running slower than norm.
- I checked the forums and neither have a lot of connections.
- SSHed in and the login was slow as well
- checked the stats page in Plesk and saw this under load average...

Last 1 minute 0.82
Last 5 minutes 0.83
Last 15 minutes 1.00

doesn't look good.

- in the ssh ran ps -ef and got

[root@sg ~]# ps -ef
UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  0 Jan28 ?        00:00:12 init [3]
root      1499     1  0 Jan28 ?        00:00:14 /usr/sbin/sshd
root      1591     1  0 Jan28 ?        00:00:02 crond
root      1601     1  0 Jan28 ?        00:00:00 /usr/sbin/saslauthd -m /var/run/
root      1602  1601  0 Jan28 ?        00:00:00 /usr/sbin/saslauthd -m /var/run/
root     26332     1  0 Jan28 ?        00:00:41 syslogd -m 0
root      6134     1  0 Jan28 ?        00:00:00 /bin/sh /usr/bin/mysqld_safe --d
mysql     7221  6134  2 Jan28 ?        23:07:42 /usr/libexec/mysqld --basedir=/u
root     11740     1  0 Jan28 ?        00:00:00 /usr/local/psa/admin/bin/httpsd
root     21951     1  0 Jan28 ?        00:01:33 /usr/sbin/httpd
root     11834     1  0 Feb05 ?        00:00:00 /usr/lib/courier-imap/couriertcp
root     11836     1  0 Feb05 ?        00:00:00 /usr/sbin/courierlogger imapd
root     11854     1  0 Feb05 ?        00:00:00 /usr/lib/courier-imap/couriertcp
root     11856     1  0 Feb05 ?        00:00:00 /usr/sbin/courierlogger imapd-ss
root     11862     1  0 Feb05 ?        00:00:00 /usr/lib/courier-imap/couriertcp
root     11864     1  0 Feb05 ?        00:00:00 /usr/sbin/courierlogger pop3d
root     11873     1  0 Feb05 ?        00:00:00 /usr/lib/courier-imap/couriertcp
root     11875     1  0 Feb05 ?        00:00:00 /usr/sbin/courierlogger pop3d-ss
named    19786     1  0 Feb05 ?        00:00:27 /usr/sbin/named -u named -c /etc
root     11957     1  0 Feb08 ?        00:00:00 xinetd -stayalive -pidfile /var/
psaadm    3414 11740  0 Feb20 ?        00:00:01 /usr/local/psa/admin/bin/httpsd
psaadm   21908 11740  0 Feb21 ?        00:00:01 /usr/local/psa/admin/bin/httpsd
qmails   16203     1  0 Feb21 ?        00:00:03 qmail-send
qmaill   16205 16203  0 Feb21 ?        00:00:00 splogger qmail
root     16206 16203  0 Feb21 ?        00:00:00 qmail-lspawn | /usr/bin/deliverq
qmailr   16207 16203  0 Feb21 ?        00:00:00 qmail-rspawn
qmailq   16208 16203  0 Feb21 ?        00:00:00 qmail-clean
psaadm   13575 11740  0 Feb23 ?        00:00:00 /usr/local/psa/admin/bin/httpsd
apache   26614 21951  0 Feb27 ?        00:00:02 /usr/sbin/httpd
apache   11884 21951  0 Feb27 ?        00:00:01 /usr/sbin/httpd
root     13449  1499  0 Feb27 ?        00:00:00 sshd: root@pts/1
root     13572 13449  0 Feb27 pts/1    00:00:00 -bash
apache   16320 21951  0 Feb27 ?        00:00:00 /usr/sbin/httpd
apache   19498 21951  0 Feb27 ?        00:00:00 /usr/sbin/httpd
apache   19515 21951  0 Feb27 ?        00:00:00 /usr/sbin/httpd
root     26184 13572  0 Feb27 pts/1    00:00:00 ps -ef

Seems to be nominal. Next to nothing using CPU.

- Checked network status and my server was absent from the list.

So should I assume the physical server is being crunched down/maxed out? What else should be checked in such a situation? Or would you just be putting in a support ticket? Just submitted one but I'm still curious what the rest of you would check.

[Down2TheC]

Wow... creating a ticket really helps.
Last 1 minute 0.08
Last 5 minutes 0.21
Last 15 minutes 0.41
Within a minute of submitting, the problem cleared up and everything's fast again. Now support will think I'm nuts (unless they get a warning or have logs for a maxed out proc.)

[RickWeb]

That what support is there for?