Friday, August 11th, 2017
Yes we do have a couple Solaris servers around and I had a case of a zombie preventing a user from accessing it. How do I kill those again?
A zombie is the slang identifier for what is called a defunct process. The child processes are gone but the image remains.
How to find them:
ps -ef | grep -i defunt
The preap command is needed to kill it. Find the one that is causing your problem and enter:
It should give you a message with status code 0 to show it worked. You can also verify by entering:
ps -ef | grep 11111
The only thing that should be seen is the grep command.
Friday, August 8th, 2014
A trouble call reported an old server running Solaris 10 with a full root partition.
Looking around I noticed the FMD log files were quite large and the active file was growing. To ease the space condition, I deleted the rotated files (ie .0, .1, etc.) and started looking into what was the problem.
The Solaris Fault Management Facility was created to provide a self-healing capability. It through the fmd daemon monitors various aspects of system health and as in this case, logged many messages for system issues.
The first obvious check was to use the fmadm faulty command to see if anything was flagged as faulty. In this situation; there was a bad dimm.
This wasn’t enough to fill log files so I had a look at /var/fm/fmd file and it had several entries for a processor.
The fmstat command which will report statistics logged by fmd and it’s modules confirmed the log activity.
Since it was an old server with no warranty; the hardware people were notified to look at the server and retire it if they couldn’t repair it.