continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julien Stern" <julien.st...@cryptolog.com>
Subject Re: 1.1-beta-3 crashes and corrupts database ?
Date Fri, 05 Oct 2007 13:55:36 GMT
On Fri, Oct 05, 2007 at 06:44:28AM -0700, Wendy Smoak wrote:
> On 10/5/07, Julien Stern <julien.stern@cryptolog.com> wrote:
> 
> > Our continumm 1.1-beta-3 had been running smoothly for several weeks,
> > and this morning it crashed, apparently attempted to automatically
> > restart and failed because of an SQL Error.
> >
> > I've stopped it, but now it does not restart.
> >
> > I've attached a stack trace. Any help would be highly appreciated
> > as we cannot restart continumm at present.
> 
> I assume that's the stack trace from attempting to restart.  The log
> files from around the time of the crash would also be interesting to
> see.

Unfortunately, there is almost nothing in the log regarding the crash.
Nothing in continuum.log and in the wrapper.log there is only:

------------------------------------
INFO   | jvm 1    | 2007/10/05 11:00:32 | 2007-10-05 10:00:32,194
[pool-1-thread-1] INFO  BuildController:default        - Performing
action check-working-directory
INFO   | jvm 1    | 2007/10/05 11:00:32 | 2007-10-05 10:00:32,212
[pool-1-thread-1] INFO  BuildController:default        - Performing
action update-working-directory-from-scm
INFO   | jvm 1    | 2007/10/05 11:00:48 | 2007-10-05 10:00:48,457
[pool-1-thread-1] INFO  ContinuumScm:default           - Updating
project: id: '117', name 'XXX'.
INFO   | jvm 1    | 2007/10/05 11:00:51 | 2007-10-05 10:00:51,215
[pool-1-thread-1] INFO  ScmManager:default             - Executing:
/bin/sh -c "cd /drive/continuum-1.1-beta-3/work/117 && cvs -z3 -f -q
update -d"
INFO   | jvm 1    | 2007/10/05 11:00:51 | 2007-10-05 10:00:51,215
[pool-1-thread-1] INFO  ScmManager:default             - Working
directory: /drive/continuum-1.1-beta-3/work/117
ERROR  | wrapper  | 2007/10/05 11:01:44 | JVM appears hung: Timed out
waiting for signal from JVM.
ERROR  | wrapper  | 2007/10/05 11:01:44 | JVM did not exit on request,
terminated
INFO   | wrapper  | 2007/10/05 11:01:44 | JVM exited on its own while
waiting to kill the application.
STATUS | wrapper  | 2007/10/05 11:01:44 | JVM exited in response to
signal SIGKILL (9).
STATUS | wrapper  | 2007/10/05 11:01:48 | Launching a JVM...
------------------------------------

So, I can only assume that something weird happened during a cvs update,
but that's pretty much all... :(

--
Julien

Mime
View raw message