You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Julien Stern <ju...@cryptolog.com> on 2007/10/05 15:34:13 UTC
1.1-beta-3 crashes and corrupts database ?
Hi list,
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.
Regards,
--
Julien
Re: 1.1-beta-3 crashes and corrupts database ?
Posted by Julien Stern <ju...@cryptolog.com>.
On Fri, Oct 05, 2007 at 06:44:28AM -0700, Wendy Smoak wrote:
> On 10/5/07, Julien Stern <ju...@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
Re: 1.1-beta-3 crashes and corrupts database ?
Posted by Wendy Smoak <ws...@gmail.com>.
On 10/5/07, Julien Stern <ju...@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.
--
Wendy
Re: 1.1-beta-3 crashes and corrupts database ?
Posted by Emmanuel Venisse <em...@venisse.net>.
I don't know why sequence aren't updated correctly by jpox, probably because when the tool import datas, it use object IDs from the xml file so jpox don't know it need to update the NEXT_VAL
Emmanuel
Julien Stern a écrit :
> On Fri, Oct 05, 2007 at 03:48:15PM +0200, Emmanuel Venisse wrote:
>> I think it's a problem with NEXT_VAL values in SEQUENCE_TABLE. Look at the
>> end of
>> http://maven.apache.org/continuum/guides/mini/guide-data-management.html
>> for informations.
>
> Many thanks for the link. It took a bit of time as the server is
> headless, but it now works again.
>
> However, I believe there is a fairly major bug that needs to be fixed.
> Indeed, the error did not occur after an import, but simply during
> the normal course of continuum...
>
> Well, to be quite precise, if you're interested, here is what happened:
>
> 1) I imported the continuum db from beta-2 with the data mngt tool
> 2) I started beta-3 (no problem)
> 3) It ran for a week or so
> 4) It crashed for some unknown reason
> 5) It would not restart because of this db problem
>
> So, maybe the DB was corrupted from step 1, but if that is not the case,
> there is a big problem :)
>
> Regards,
>
> --
> Julien
>
>> Emmanuel
>>
>> Julien Stern a écrit :
>>> Hi list,
>>>
>>> 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.
>>>
>>> Regards,
>>>
>>> --
>>> Julien
>>>
>
>
Re: 1.1-beta-3 crashes and corrupts database ?
Posted by Julien Stern <ju...@cryptolog.com>.
On Fri, Oct 05, 2007 at 03:48:15PM +0200, Emmanuel Venisse wrote:
> I think it's a problem with NEXT_VAL values in SEQUENCE_TABLE. Look at the
> end of
> http://maven.apache.org/continuum/guides/mini/guide-data-management.html
> for informations.
Many thanks for the link. It took a bit of time as the server is
headless, but it now works again.
However, I believe there is a fairly major bug that needs to be fixed.
Indeed, the error did not occur after an import, but simply during
the normal course of continuum...
Well, to be quite precise, if you're interested, here is what happened:
1) I imported the continuum db from beta-2 with the data mngt tool
2) I started beta-3 (no problem)
3) It ran for a week or so
4) It crashed for some unknown reason
5) It would not restart because of this db problem
So, maybe the DB was corrupted from step 1, but if that is not the case,
there is a big problem :)
Regards,
--
Julien
>
> Emmanuel
>
> Julien Stern a écrit :
> >Hi list,
> >
> >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.
> >
> >Regards,
> >
> >--
> >Julien
> >
>
Re: 1.1-beta-3 crashes and corrupts database ?
Posted by Emmanuel Venisse <em...@venisse.net>.
I think it's a problem with NEXT_VAL values in SEQUENCE_TABLE. Look at the end of http://maven.apache.org/continuum/guides/mini/guide-data-management.html for informations.
Emmanuel
Julien Stern a écrit :
> Hi list,
>
> 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.
>
> Regards,
>
> --
> Julien
>