Mark, I can't help you on the Mac OS X side, but I can tell you about the logs...
The primary thing you want to do is read the witangoevents.log, it's in the configuration folder by default. The details of the crash or exception should be listed there. It all depends on how much Witango was able to do before it was quit or locked up. You should, as often as possible, email the chunk of the log containing the error and few lines before and after to [EMAIL PROTECTED] It's always helpful for them to see it. The request log is only partially helpful, it usually only points to what was happening at the time of the crash - helpful if you need to send the offending TAF to WT for testing. For example, I recently saw a bug in the user scope expiry by noting that a crash always occurred right after the user expiry entry in the log. Level 1 logging is usually enough to get this kind of information without impacting your service. You should up it to 3 if you are looking for some nitty-gritty price of information around a bug, crash or particular execution, but don't leave it there. When trying to isolate the reason for the crash, try to determine if it was Witango on its own, or caused by an external problem. I've found that many of the crashes that occur are caused by identifiable external reasons, perhaps the mail server crashed, or a shell script balked. Sometimes it's that Witango doesn't handle a particular error or situation well and you can simply avoid it. Whatever you can find, you should pass it on to WT so they know. It might not get fixed tomorrow, but it helps make the product better. Mac OS X seems to have its own special brand of problems thanks to Apple. I suppose it's getting better with time, but they seem to have made ODBC into a four letter word. Best, Robert -----Original Message----- From: Mark Weiss [mailto:[EMAIL PROTECTED] Sent: Thursday, May 19, 2005 1:34 AM To: [email protected] Subject: Witango-Talk: OSX 5.5 questions First Question I have experienced several app server crashes. So I am wanting to have something that polls the app server and if it doesn't' respond, restarts it. Like a cron function or something like that. I have searched the archives and I haven't found anything, although I thought I would find something. Second Question: What lines to I type in terminal, to stop and restart the witango app server? If I am trying to find the reason why the app server is crashing, which level would I want to set the logging level to? I had it on 0 and not have it set to 2. Thanks for your help.. Mark Weiss ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
