continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <Manuel.R...@t-systems.com>
Subject AW: CVS checkout fails: "Terminated with fatal signal 11"
Date Mon, 12 Nov 2007 09:30:25 GMT
Can you give me a hint what to do to fix this problem?
Or do you need more information?

-----Ursprüngliche Nachricht-----
Von: Renz, Manuel 
Gesendet: Donnerstag, 8. November 2007 12:59
An: continuum-users@maven.apache.org
Betreff: AW: CVS checkout fails: "Terminated with fatal signal 11"

It is planned to do a clean checkout once a day  

-----Ursprüngliche Nachricht-----
Von: Emmanuel Venisse [mailto:emmanuel@venisse.net]
Gesendet: Mittwoch, 7. November 2007 20:19
An: continuum-users@maven.apache.org
Betreff: Re: CVS checkout fails: "Terminated with fatal signal 11"

It seems a kill was sent to the cvs client.

How many time is used to do a checkout?

Emmanuel

Manuel.Renz@t-systems.com a écrit :
>  
> Hi togehter,
> I'm using continuum 1.1 beta 3 at the moment. I have set up 2 Projects 
> which work just fine.
> 
> Now I'm in the process of setting up my third project, which is quite 
> large (clean checked out working copy round about ~260MB ), with which 
> I have massive problems.
> 
> 
> Here is a short snippet from the logs:
> 
> [SocketListener0-1] INFO  FreemarkerManager      - Instantiating
> Freemarker ConfigManager!,
> com.opensymphony.webwork.views.freemarker.FreemarkerManager
> [SocketListener0-0] INFO  Continuum:default      - Enqueuing 'My-App'
> (Build definition id=6).
> [pool-1-thread-1] INFO  BuildController:default  - Initializing build 
> [pool-1-thread-1] INFO  BuildController:default  - Starting build of 
> My-App [pool-1-thread-1] INFO  BuildController:default  - Updating 
> working dir [pool-1-thread-1] INFO  BuildController:default  - 
> Performing action check-working-directory [pool-1-thread-1] INFO 
> BuildController:default  - Performing action checkout-project
> [pool-1-thread-1] INFO  ContinuumScm:default     - Checking out project:
> 'My-App', id: '63' to 'D:\buildserver\data\working\63'.
> [pool-1-thread-1] INFO  ScmManager:default       - Executing: cmd.exe /X
> /C '"cvs -z3 -f -d :pserver:user@server:/CVS -q checkout -d 63 my-app"'
> [pool-1-thread-1] INFO  ScmManager:default       - Working directory:
> D:\buildserver\data\working
> ...
> [pool-1-thread-1] WARN  ContinuumScm:default     - Error while checking
> out the code for project: 'My-App', id: '63' to 
> 'D:\buildserver\data\working\63'.
> [pool-1-thread-1] WARN  ContinuumScm:default     - Command output:
> Terminated with fatal signal 11
> [pool-1-thread-1] WARN  ContinuumScm:default     - Provider message: The
> cvs command failed.
> [pool-1-thread-1] INFO  BuildController:default  - Merging SCM results 
> [pool-1-thread-1] INFO  BuildController:default  - Error updating from 
> SCM, not building [pool-1-thread-1] INFO  BuildController:default  - 
> Initializing build [pool-1-thread-1] INFO  BuildController:default  - 
> Starting build of parent [pool-1-thread-1] INFO 
> BuildController:default  - Updating working dir [pool-1-thread-1] INFO 
> BuildController:default  - Performing action check-working-directory 
> [pool-1-thread-1] INFO  BuildController:default  - Performing action 
> update-working-directory-from-scm
> 
> 
> In the build logs via the web UI I get just following information and 
> nothing more:
> 
> 	Provider message: The cvs command failed.
> 	Command output: 
> 	
> ----------------------------------------------------------------------
> --
> -------
> 	Terminated with fatal signal 11
> 	
> ----------------------------------------------------------------------
> --
> -------
> 
> When I run "cvs -z3 -f -d :pserver:user@server:/CVS -q checkout -d 63 
> my-app" manually on the commandline it works like a charme, so I think 
> the problem is on some layer between cvs.exe and continuum...
> 
> I googled and found this:
> ------------------------------------------------
> Terminated with fatal signal 11
> 
> This message usually indicates that CVS (the server, if you're using 
> client/server mode) has run out of (virtual) memory. Although CVS 
> tries to catch the error and issue a more meaningful message, there 
> are many circumstances where that is not possible. If you appear to 
> have lots of memory available to the system, the problem is most 
> likely that you're running into a system-wide limit on the amount of 
> memory a single process can use or a similar process-specific limit. 
> The mechanisms for displaying and setting such limits vary from system 
> to system, so you'll have to consult an expert for your particular 
> system if you don't know how to do that.
> ------------------------------------------------
> 
> But since the command works if it is run outside of continuum I think 
> this is not a memory problem on the server.
> 
> 
> Hopefully somebody can give me a hint...
> 
> Greetings
> Manuel Renz
> --
> Notice: This transmittal and/or attachments may be privileged 
> orconfidential. If you are not the intended recipient, you are hereby 
> notified that you have received this transmittal in error; any review, 
> dissemination, or copying is strictly prohibited. If you received this 
> transmittal in error, please notify us immediately by reply and 
> immediately delete this message and all its attachments. Thank you.
> 
> 


Mime
View raw message