Stupidly, one of the users decided to try and kill oninit. When this
failed, they did stop the app properly and it attempted to switch to
its standby machine.
This standby machine failed (for various reasons) and has now been
switched off. After restarting the main machine, it works OK apart
from oninit taking up so much CPU.
Any ideas?
eg onstat-c
onstat -u
onstat -p
onstat -g iov
?
"BertieB...@gmail.com" <bertieb...@gmail.com> wrote in message
news:9d5aa313-c97a-478a...@j21g2000yqe.googlegroups.com...
A "user" has the power to kill oninit? I can just see Mr. Leffler
beating his head against the keyboard now.
I take it you are back online, fast recovery was unremarkable, and
now,you have no idea what's running hot?
A couple of quick questions that might shed some light
- Do you have any older onstats that you can compare your current
usage pattern with?
- Has the ONCONFIG changed? If the user can kill oninit, I am sure
they can hack up the onconfig?
- Any sar data? Double check that to see if this high cpu usage is
something new or have you been running like this for a while and this
event opened your eyes to it?
- What version of Solaris and Version of IDS?
- What does ps -eaux ( or the Solaris equivelant say) - Anything
waiting on resources?
HTH
Russ
Secondary is still down. Primary is now up and running fine. CPU back
to normal.