John, As I'm also running 065 on Linux (Redhat 9) this is of interest to me. I've just gone thru the last two months of witangoevents.log and I only have 3 START events: two manual restarts because I don't have a taf implemented to reload cached tafs, and a system reboot at the first of the year to apply Redhat security patches. My system isn't heavily stressed though.
>I'm running 065 on a Linux box, and now that I've put this machine into >production, the witango service keeps crashing on me. (every few >hours) I am running the server with a processmonitor, so the pid is >checked every few seconds and if it crashes the server starts up right >away again, but I need to figure out why this thing is crashing. I've >got logging level set to 2 right now, and i know exactly what times it >crashes, because the process monitor keeps a log of every restart (plus >that would be in the witango log file too) > >So, my questions to you folks are. > >Have you ever had to debug a server crash, and if so how were you able >to identify the offending taf/tcf? > >Is the log file usefull when the server crashes, or does it not >typically show an entry in the log for the offending taf/tcf? > >Thanks for any help. > >/John > >________________________________________________________________________ >TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > Bill Conlon To the Point 345 California Avenue Suite 2 Palo Alto, CA 94306 office: 650.327.2175 fax: 650.329.8335 mobile: 650.906.9929 e-mail: mailto:[EMAIL PROTECTED] web: http://www.tothept.com ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
