Finding Killed Process

Harlin · 11-01-2007, 12:06 PM

We use DB2 on Redhat. An instance of DB2 was running and then died unexpectedly for seemingly no reason. The DB2 support person told us that the reason the instance died was because a kill -9 was issued against a db2 process. I've searched all of the user's history files and was not able to find the issuer. Is there any way to track down a kill -9 issuance from the past few days on the system?

Thanks

bsdunix · 11-01-2007, 12:55 PM

Intresting, how did the DB2 support person know kill -9 was issued since you can't find it in the users command history files? The system log files are usually located in /var/log or /var/adm. I don't recall any typical system log file recording user commands other than a service starting/stopping. Finding when the process was logged as stopped might help to narrow down your search?

Harlin · 11-01-2007, 01:24 PM

It wasn't difficult to find in the db2diag.log file:

2007-10-31-23.24.50.920652-240 E6455446G877 LEVEL: Severe
PID : 22016 TID : 3086423744 PROC : db2gds 0
INSTANCE: expinst1 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloEDUSIGCHLDHandler, probe:50
DATA #1 : <preformatted>
Detected the death of an EDU with process id 22565
The signal number that terminated this process was 9
Look for trap files (t22565.*) in the dump directory

Any ideas after reading this?

Thanks!

bsdunix · 11-01-2007, 03:04 PM

You may already know this information, if not:

Analyzing trap files

http://publib.boulder.ibm.com/infoce...d/c0020711.htm

Look at your trap file for any clues:

Quote:

Look for trap files (t22565.*) in the dump directory

and

Common signals and exceptions that cause trap file generation

SIGKILL. This Signal #9 can be caused by someone manually (or through a script) killing a DB2(R) process, in which case, no trap file is generated.

http://publib.boulder.ibm.com/infoce...d/c0020711.htm

So, since you have a trap file then termination might not have been caused by someone issuing kill.