saposcol

Symptom We have an alert from our solution manager regarding the os collector where the Alert text shows the above message “Saposcol: data collection not up to date” Solution On AIX, this usually means the saposcol program has crashed, but the shared memory has not been released. Most of the time this can be corrected by running saposcol -f (force option). Another way to release shared memory I describe in post Problem with stop/start saposcol

Sometimes it may be impossible to stop saposcol either by “saposcol -d” –> kill or by “saposcol -k”. The system produces messages similar to: ======================================== can’t kill process 99687. kill: No such process ERROR:No reaction from collecting process 99687! Please kill collecting process. ======================================== Although no process with PID 99687  exists, the output of command “saposcol -s” shows that saposcol is running and shared memory is attached. In this case, stop the collector running by removing the shared memory key of saposcol. For this, execute command “ipcs -ma” and note the line that contains saposcol key “4dbe”. You need the shared memory … Continue Reading →