that refreshing the connections regularly is a good thing. Your
platform/software might have very different outcomes.
Robert
-Original Message-
From: Roland Dumas [mailto:[EMAIL PROTECTED]
Sent: Friday, March 05, 2004 5:54 PM
To: [EMAIL PROTECTED]
Subject: Re: Witango-Talk: Crashes on OS
My second urgent problem is increase in frequency of witango crashes.
It is crashing now 4-6 times a day. Needless to say, all the variables
are dumped as it restarts, losing user sessions, etc.
The crash log is very consistent. Always an IODBC thing going on. I
look and there is absolutely
Crashes occur on regular base, if something in the JDBC envirmonment is
changed and you do not restart the server. Sometimes even if just a new
field was added... (for mysql)
Christian
Am 10.02.2004 2:44 Uhr schrieb "MJPinckard" unter <[EMAIL PROTECTED]>:
> Just chiming in to say that Timbuktu
I also don't think TB2 is a suspect. On the two servers I'm running,
both have TB2, and the #1 server had zero witango crashes for a long
time, despite frequent TB2 "control" sessions.
On Feb 9, 2004, at 5:44 PM, MJPinckard wrote:
Just chiming in to say that Timbuktu causes no problem for me.
Just chiming in to say that Timbuktu causes no problem for me. I have it
installed, and typically Timbuktu into the server, and leave the window to
the server open all day (e.g same connection for hours on end),
periodically
looking over the server logs for problems...
My server is a dual G5 10.3
d to pair up in. The machine worked up right up until it tried to
address the first bit that wasn't actually there.
Robert
-Original Message-
From: Roland Dumas [mailto:[EMAIL PROTECTED]
Sent: Monday, February 09, 2004 11:34 AM
To: [EMAIL PROTECTED]
Subject: Re: Witango-Talk: Crashes on
Can anyone tell me if this is evidence of RAM problems? The crashed
thread records tend to be rather consistent in what they're writing and
where they are writing it, as far as my uneducated eyes can tell.
On Feb 6, 2004, at 10:05 AM, Ben Johansen wrote:
Disclaimer: Not a Mac Guy ;-)
This so
Pardon me if you have already looked at this BUT-
Do you have Timbuktu loaded on these machines? My machines are quite
stable UNLESS-
1) I TB2 into the box.
2) Database records are empty. (database there but no records)
Either is a recipe to have witangod crash for me.
So I don't Timbuktu an
number :)
Ben Johansen - http://www.pcforge.com
Authorized Witango & MDaemon Reseller
Available for Witango Developement
-Original Message-
From: Roland Dumas [mailto:[EMAIL PROTECTED]
Sent: Friday, February 06, 2004 12:58 PM
To: [EMAIL PROTECTED]
Subject: Re: Witango-Talk: Crashes on OS X
On F
On Feb 6, 2004, at 10:05 AM, Ben Johansen wrote:
Disclaimer: Not a Mac Guy ;-)
This sounds a lot like a RAM module going bad.
This can be intermittent for several reasons
-the ram chip is fail intermittently
-the failed location on the ram chip is in a high mem address and only
is reached under
le for Witango Developement
-Original Message-
From: Roland Dumas [mailto:[EMAIL PROTECTED]
Sent: Friday, February 06, 2004 12:58 PM
To: [EMAIL PROTECTED]
Subject: Re: Witango-Talk: Crashes on OS X
On Feb 6, 2004, at 9:29 AM, Jason Pamental wrote:
Roland,
Have you tried the 'standard
number :)
Ben Johansen - http://www.pcforge.com
Authorized Witango & MDaemon Reseller
Available for Witango Developement
-Original Message-
From: Roland Dumas [mailto:[EMAIL PROTECTED]
Sent: Friday, February 06, 2004 12:58 PM
To: [EMAIL PROTECTED]
Subject: Re: Witango-Talk: Crashes on OS X
On Feb 6
ent funny number :)
Ben Johansen - http://www.pcforge.com
Authorized Witango & MDaemon Reseller
Available for Witango Developement
-Original Message-
From: Roland Dumas [mailto:[EMAIL PROTECTED]
Sent: Friday, February 06, 2004 12:58 PM
To: [EMAIL PROTECTED]
Subject: Re: Witango-Talk: Cr
you
see a consistent funny number :)
Ben Johansen - http://www.pcforge.com
Authorized Witango & MDaemon Reseller
Available for Witango Developement
-Original Message-
From: Roland Dumas [mailto:[EMAIL PROTECTED]
Sent: Friday, February 06, 2004 12:58 PM
To: [EMAIL PROTECTED]
Subject
Johansen - http://www.pcforge.com
Authorized Witango & MDaemon Reseller
Available for Witango Developement
-Original Message-
From: Roland Dumas [mailto:[EMAIL PROTECTED]
Sent: Friday, February 06, 2004 12:58 PM
To: [EMAIL PROTECTED]
Subject: Re: Witango-Talk: Crashes on OS X
On Feb 6, 2004,
8 PM
To: [EMAIL PROTECTED]
Subject: Re: Witango-Talk: Crashes on OS X
On Feb 6, 2004, at 9:29 AM, Jason Pamental wrote:
> Roland,
>
> Have you tried the 'standard Mac OS X voodoo' of running the 'repair
> permissions' bit in the disk utility (applications/utilitie
Yes, and it does not require a restart either.
On Feb 6, 2004, at 12:58 PM, Roland Dumas wrote:
On Feb 6, 2004, at 9:29 AM, Jason Pamental wrote:
Roland,
Have you tried the 'standard Mac OS X voodoo' of running the 'repair
permissions' bit in the disk utility (applications/utilities)?
can you
On Feb 6, 2004, at 9:29 AM, Jason Pamental wrote:
Roland,
Have you tried the 'standard Mac OS X voodoo' of running the 'repair
permissions' bit in the disk utility (applications/utilities)?
can you run the disk utility to fix permissions while server is in
operation?
__
I'm really not sure - it could be a file that gets touched only occasionally and now can't be read or written to. Another thing to look at is the Witango logs to see if it's a common file that was the last thing executed before the crash each time. That might tell you a little more.
On Feb 6, 200
I'll give a try, but if permissions is a problem, would it be crashing a lot? Like every time the particular piece of code was loaded?
On Feb 6, 2004, at 9:29 AM, Jason Pamental wrote:
Roland,
Have you tried the 'standard Mac OS X voodoo' of running the 'repair permissions' bit in the disk utilit
Roland,
Have you tried the 'standard Mac OS X voodoo' of running the 'repair permissions' bit in the disk utility (applications/utilities)?
The 'bad_access' bit seems to indicate a permissions problem, which sometimes seem to just get set wrong with no apparent reason... I'd try that first. There
I have 2 witango licenses on two machines that are essentially identical.
Server 1 never crashed for a long time
Server 2 started crashing (witango crash) about once a day. Those crashes abated for about a month and returned. the crash log always indicates it's an odbc issue, though I can't figur
22 matches
Mail list logo
