I think you are getting confused about threads and children. In Linux, threads are sort-of processes. They have a pid (and show up in ps, yuk!), but they are not really separate processes. They share the same address space.
You will probably not be able to diagnose your problems 'from below' as you are trying to do. You will probably need to examine your ColdFusion CFML application. -- Tom Jordahl Macromedia -----Original Message----- From: chad [mailto:[EMAIL PROTECTED]] Sent: Monday, February 04, 2002 3:09 PM To: CF-Linux Subject: Re: cfserver getting sig 11. Hi, We just had another few segfaults. sever.log shows: "Fatal","9225","02/04/02","12:10:37",,"Caught a fatal signal (11) - Aborting" "Information","1024","02/04/02","12:10:38",,"The ColdFusion Application Server started." executive.log shows: "Warning","1026","02/04/02","12:10:37",,"Restarted ColdFusion Application Server." The kernel logs show the following as signal 6 's generated from user programs: First we see what I presume to be the signal handler for sig 11: Feb 4 12:10:37 pimp kernel: Sig: 6 from pid: 6726 (cfserver) to pid: 6726 (cfserver) Next it appears a parent notices a child has died (I am speculating, I don't have the relationships recorded). In response to this all of the children are signalled and die. Feb 4 12:10:37 pimp kernel: Sig: 6 from pid: 6717 (cfserver) to pid: 6725 (cfserver) Feb 4 12:10:37 pimp kernel: Sig: 6 from pid: 6717 (cfserver) to pid: 6724 (cfserver) Feb 4 12:10:37 pimp kernel: Sig: 6 from pid: 6717 (cfserver) to pid: 6723 (cfserver) Feb 4 12:10:37 pimp kernel: Sig: 6 from pid: 6717 (cfserver) to pid: 6722 (cfserver) Feb 4 12:10:37 pimp kernel: Sig: 6 from pid: 6717 (cfserver) to pid: 6721 (cfserver) Feb 4 12:10:37 pimp kernel: Sig: 6 from pid: 6717 (cfserver) to pid: 6720 (cfserver) Feb 4 12:10:37 pimp kernel: Sig: 6 from pid: 6717 (cfserver) to pid: 6718 (cfserver) Feb 4 12:10:37 pimp kernel: Sig: 6 from pid: 6717 (cfserver) to pid: 6716 (cfserver) Is there any way to set ColdFusion to only kill the child that got the sig 11 or must all of them be killed as the parent doesn't know which child generated the sig 11? This would be a nice temporary solution untill we can figure out what is causing the sig 11. Thanks, Chad < chad @ webcorelabs . com> Jr Sys Admin Webcore Labs Inc ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com ------------------------------------------------------------------------------ Archives: http://www.mail-archive.com/cf-linux%40houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_linux or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
