Windows I think is a little nicer, it usually reports the action (as well as the TAF/TCF) that it failed on. However we don't get SIGSEGVs on Windows.
I would max the logging, 3 should be enough, maybe 2. Then take the timestamp in the witangoevents.log and cross reference it with the log. You'll either see that one thing was running alone, and you know something. Or perhaps there was a combination of things trying to occur at the same time. You're getting some config errors, most notably for /usr/local/witango/configuration/applications.ini you should set applicationswitch=OFF in Witango.ini if you don't use them. Robert -----Original Message----- From: John McGowan [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 21, 2004 3:28 PM To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: Crashing App Server witangoevents.log doesn't give me any information that I can work with... (no taf or tcf references) Here is a snippet of the witangoevents.log showing it starting up, running for about 50 minutes or so, and then crashing. It's definitly looks like it a typical segfault, which i'm sure Witango would like to be able to track down. Robert, when you've seen crashes like this (even on windows) has the witango logging showed the hit to the server that caused the problem? [18473] 2004-01-21 10:49:40 CONFIG ERROR [No such file or directory] could not open file /usr/local/witango/configuration/applications.ini [18473] 2004-01-21 10:49:40 RUNTIME INFO There were no applications defined. Application scope is disabled. [18473] 2004-01-21 10:49:40 START INFO Witango daemon started with configuration stanza 'WitangoServer' [18473] 2004-01-21 10:49:40 VERSION INFO Version 5.0.1.065 Chimera (Linux) [Standard Edition] [18473] 2004-01-21 10:49:40 LICENSE ERROR A serious error occurred while enforcing the license [18473] 2004-01-21 10:49:40 START INFO Maximum heap size 100000000 bytes [18473] 2004-01-21 10:49:40 START INFO Attempting to load Java VM: /usr/local/j2re1.4.1_03/lib/i386/server/libjvm.so [18473] 2004-01-21 10:49:41 START INFO Java VM service is enabled [18473] 2004-01-21 10:49:41 START INFO JavaScript-C 1.5 pre-release 5a 2003-05-29 [18473] 2004-01-21 10:49:41 START WARNING Cannot initialize ODBC environment [18473] 2004-01-21 10:49:41 START INFO Initialized JDBC environment [18473] 2004-01-21 10:49:41 START WARNING Cannot initialize Oracle Call Interface (OCI) environment [18473] 2004-01-21 10:49:41 START INFO Listener Address: Any; Listener Port: 18100 [18473] 2004-01-21 10:49:41 START INFO Allocated 20 worker threads [18473] 2004-01-21 10:49:42 RUNTIME INFO Skipped empty startup URL [18473] 2004-01-21 10:49:43 RUNTIME INFO Started accepting user requests [18473] 2004-01-21 10:50:01 RUNTIME INFO No existing connection to the data source found, creating a new connection. DSN: jdbc.erube; User: ; [18473] 2004-01-21 10:51:06 RUNTIME INFO No existing connection to the data source found, creating a new connection. DSN: jdbc.nyf; User: ; [18473] 2004-01-21 10:52:37 RUNTIME INFO No existing connection to the data source found, creating a new connection. DSN: jdbc.erube; User: ; [18473] 2004-01-21 10:57:43 RUNTIME INFO No existing connection to the data source found, creating a new connection. DSN: ; User: ; [18473] 2004-01-21 11:14:53 RUNTIME INFO No existing connection to the data source found, creating a new connection. DSN: jdbc.wildheartland; User: ; [18473] 2004-01-21 11:24:30 CONFIG ERROR [No such file or directory] could not open file /usr/local/witango/configuration/applications.ini [18473] 2004-01-21 11:24:30 RUNTIME INFO There were no applications defined. Application scope is disabled. [18473] 2004-01-21 11:26:26 RUNTIME INFO No existing connection to the data source found, creating a new connection. DSN: jdbc.nyf; User: ; [18473] 2004-01-21 11:38:23 RUNTIME FATAL Caught fatal signal 11 (SIGSEGV); thread id = 1309739200; code: 1; address: 00000036; value: 00000000; errno: 0; status: 0; [19285] 2004-01-21 11:38:26 CONFIG ERROR [No such file or directory] could not open file /usr/local/witango/configuration/applications.ini Robert Shubert wrote: >Read through witangoevents.log it should shed some light on the problem. >And yes, I debug Witango system crashes all the time, on Win32, however. > >Robert > >-----Original Message----- >From: John McGowan [mailto:[EMAIL PROTECTED] >Sent: Wednesday, January 21, 2004 10:14 AM >To: [EMAIL PROTECTED] >Subject: Witango-Talk: Crashing App Server > >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 > >_______________________________________________________________________ _ >TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
