Randell, have you checked the Server log to see if there are any clues there? From my experience these sorts of errors usually relate to memory corruption issues. If we are to try and help it would be good to know the following. Operating System, Web Server, Version of CF (SPacks etc).
Kind Regards - Mike Brunt, CTO Webapper http://www.webapper.com Downey CA Office 562.243.6255 AIM - webappermb "Webapper - Making the NET work" -----Original Message----- From: Randell B Adkins [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 10:33 AM To: CF-Talk Subject: RE: CF Application Logs Nope... The only other messages are the ones indicating that CF is restarting.. >>> [EMAIL PROTECTED] 10/02/02 01:22PM >>> Randell, are there any other messages directly before this in the Application log? Kind Regards - Mike Brunt, CTO Webapper http://www.webapper.com Downey CA Office 562.243.6255 AIM - webappermb "Webapper - Making the NET work" -----Original Message----- From: Randell B Adkins [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 9:16 AM To: CF-Talk Subject: CF Application Logs Has anyone seen this error in the server.log file from the CF Administrator? Caught a fatal signal (4) - Aborting OR Caught a fatal signal (11) - Aborting After receiving this error, CF Executive (I imagine) initates a call for restarting the CF Application Server Services. If so, any ideas what it means as well as possible causes? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com
