Database Reference
In-Depth Information
this point in time (to measure I/O) are 2 and 16, respectively (extremely low!),
and the CPU is 96 percent idle (no problem here!):
root@soahost1:/root> vmstat -S m
procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu------
r b swpd free buff cache si so bi bo in cs us sy id wa st
0 0 0 59 402 15055 0 0 2 16 0 0 2 2 96 1 0
Checking operating system resources and logs
For example, in Linux, the
/var/log/messages
log reveals critical events at
the operating system level. This log file can reveal errors that may have a dir-
ect impact on the stability, behavior, and/or performance of the SOA Infrastruc-
ture. In the following example, it appears that we have exceeded certain ulimit
resources.
root@soahost1:/root> cat /var/log/messages
Aug 31 20:53:22 uslx286 sshd[22480]: fatal: setresuid 10000: Resource temporarily unavailable
The
lsof
command in Linux can list the number of open files. Too many may
exhaust operating system resources:
root@soahost1:/root> lsof | wc -l
6064
The
ps
command in Linux can list the number of running processes. Ultimately,
too many of them may also exhaust operating system resources:
root@soahost1:/root> ps -A | wc -l
297
