Sorry to say it, but I'm back after a hectic day yesterday. We've upgraded to RedHat 7.3 (and replaced a broken drive in the RAID array, but that's another story), and we've still got the frequent crashing problem.
So far we've tried this: 1. All our session/application variables are locked for writing, and using Auto read locking. 2. The ODBC drivers were updated to the latest version (interbase easysoft) 3. The Client variables are now stored in a DB 4. Upgraded server to RedHat v7.3 [Disk was found to be faulty in the Raid array and was replaced] 5. Ran server for a while with a single processor kernel - no better. 6. Registry still looked big so purged all remaining client variables. 7. Moved the app's database from application variable to request variable. 8. CF 5 Hot Fixes applied If anyone can suggest *anything* else I can try I'd be very grateful. Thanks, Simon --- [EMAIL PROTECTED] Applications Development Manager Warwick Business School >>> [EMAIL PROTECTED] 10/07/2002 14:48:15 >>> Ew. Red Hat 7.0, to be honest, Red Hat 7.0 has more compiler/Library issues than ever known by mankind. Even Red Hat disowned it. However. What you need to do is get strace to dump the PID files into /tmp instead of traying to grab the running PID. The Pause is a child thread waiting for a response > -----Original Message----- > From: Simon Harper [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, July 10, 2002 9:45 AM > To: CF-Linux > Subject: RE: Client vs Session variables > > Thanks again Jesse: > > However, what distro/version are you running for 1. > > RedHat 7.0: > Linux stanley 2.2.19-7.0.12smp #1 SMP Fri Oct 26 15:17:55 EDT 2001 i686 > unknown > > > Number 2, you've checked the variable locking, right? > > We've locked all the writes and used auto read locking > > > Number 3: Strace: the output is not human readable, but if you can get > the output from the thread > > that died, you should be able to figure out where the error was > generated. > > If I type strace -p 1234 for a cfserver it just sits there saying "pause(" > until I hit CTRL-C. > > > Number 4: Are you using cfmail? Have you checked the spool? > > Yes, we do use it but I can't see any problems there (FWIW in the past I > changed the permission in that directory accidently and the server crashed > every time it tried to send mail). > > Cheers, > > Simon > > Jesse Noller > [EMAIL PROTECTED] > Macromedia Server Development > Unix/Linux "special guy" > > > -----Original Message----- > > From: Simon Harper [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, July 10, 2002 9:34 AM > > To: CF-Linux > > Subject: RE: Client vs Session variables > > > > Thanks for getting back to me. Is there any way of working out where > that > > someplace else is ? > > > > Ta > > > > Simon > > > > --- > > [EMAIL PROTECTED] > > Applications Development Manager > > Warwick Business School > > > > >>> [EMAIL PROTECTED] 10/07/2002 14:30:54 >>> > > Actually, you're probably NOT seeing an error from SIG11s Sig11s are > > generic errors which generally don't bring CF down. > > > > The error is going to lie someplace else in the system > > > > Jesse Noller > > [EMAIL PROTECTED] > > Macromedia Server Development > > Unix/Linux "special guy" > > > > > -----Original Message----- > > > From: Simon Harper [mailto:[EMAIL PROTECTED]] > > > Sent: Wednesday, July 10, 2002 4:08 AM > > > To: CF-Linux > > > Subject: Client vs Session variables > > > > > > I've been trying to track down a 'SIG11' error that's bringing our > site > > > down every half an hour (on a good day). I'm really not getting > > anywhere > > > so I thought I might try a different approach ... > > > > > > The users' experience is that when CF crashes their session is lost. > > Our > > > site uses session variables heavily for navigation. We allow people > to > > > post messages to a dicussion board in one area of the site, so when > they > > > post their carefully crafted message they'll often find that their > > session > > > is already toast and that the app has no idea what to do with their > > > message (so throws it away). > > > > > > On the other hand, the crashes per se are not that disruptive (if > you're > > > unlucky to see the error message you can usually 'refresh' to get > going > > > again). > > > > > > So my question is, can we convert all our session variable into client > > > variable which will be nicely maintained in the database, and should > > > survive a restart ? > > > > > > Thanks for any advice you may have, > > > > > > Cheers, > > > > > > Simon. > > > > > > > > > --- > > > [EMAIL PROTECTED] > > > Applications Development Manager > > > Warwick Business School > > > > > > > > > > > > ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm ------------------------------------------------------------------------------ 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.
