Good morning,
Does anyone have any idea's why "steamd", the daemon for the Storage
Works Command Console 2.0, would repeatedly go haywire and consume all
available CPU cycles? This phenomenon is occuring almost daily on one
of our two Alphas, but not the other. The systems are in a cluster. We
run LSM, AdvFs. I believe we have the "disks.ignore" correctly
configured. Additionally, there's usually no one even logged into the
system, although people could be hitting the database that's running on
it.
Here's what I see when steamd is going crazy:
# uptime
09:49 up 5 days, 21:34, 1 user, load average: 3.75, 3.62, 3.62
These are the steamd processes:
root 1778 1 9.3 12:03:28 ?? 1:51.54
/usr/opt/SWCC200/bin/steamd -SF
root 27893 1778 0.0 09:49:35 ?? 0:00.00
/usr/opt/SWCC200/bin/steamd -SF
If I kill it everything settles down. initd restarts it automatically
as soon as it's killed.
# kill -9 1778
root 30007 1 0.3 09:50:03 ?? 0:00.10
/usr/opt/SWCC200/bin/steamd -SF
# uptime
09:50 up 5 days, 21:35, 1 user, load average: 0.06, 1.89, 2.62
Thanks,
Pete
Received on Thu Feb 11 1999 - 15:03:59 NZDT