1. Continua version number and edition:
v1.6.0.256 64 bit
2. Operating system for Continua and agents:
Windows 7 64 bits - 1 Agent on same machine as server
3. Database platform:
bundled PostgreSQL
4. How much CPU / RAM / Diskspace do you have free on the Continua server, agents, and database:
eg. 50% free cpu, 90% free RAM (10gig), 10% free hard disk (10 gig)
5. A detailed description of the issue:
Recently almost all our nightly builds (time triggered builds) fails with the following errors:
Web
The web server reported the following error:
System.ServiceModel.CommunicationException: There was an error reading from the pipe: Unrecognized error 109 (0x6d). —> System.IO.PipeException: There was an error reading from the pipe: Unrecognized error 109 (0x6d).
at System.ServiceModel.Channels.PipeConnection.FinishSyncRead(Boolean traceExceptionsAsErrors)
at System.ServiceModel.Channels.PipeConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
— End of inner exception stack trace —
Server stack trace:
at System.ServiceModel.Channels.PipeConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
at System.ServiceModel.Channels.SessionConnectionReader.Receive(TimeSpan timeout)
at System.ServiceModel.Channels.SynchronizedMessageSource.Receive(TimeSpan timeout)
at System.ServiceModel.Channels.TransportDuplexSessionChannel.Receive(TimeSpan timeout)
at System.ServiceModel.Channels.TransportDuplexSessionChannel.TryReceive(TimeSpan timeout, Message& message)
at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Continua.Modules.Builds.Common.Services.IBuildUIService.GetConfigStatistics(String slug, String configName)
at Continua.Web.Builds.Controllers.ConfigurationsController.<>c__DisplayClass28.b__26(IBuildUIService x)
at Continua.Web.ContinuaController.With[TService](Action`1 action, ServiceEndpointOptions options) in s:\CI_WS\Ws\720138\Source\CT_Source\Source\Continua.Web\Controllers\ContinuaController.cs:line 839
at Continua.Web.Builds.Controllers.ConfigurationsController.ConfigInfo(String slug, String id)
After this we must reset almost all of our repositories.
Thanks in advance.
Hi,
Thanks for reporting this error. It points to a communication problem between the web server and Continua Server service which should only affect the data displayed in the web browser. This type of error can usually be traced to server or database overload. On its own, It does not give any indication of the cause of an issue with failing build triggers.
Are there any further errors in the event log? Can you look at the timeline and logs for each build to see when they failed? We’re not sure why you needed to reset the repositories - were they showing an error status?
Also, how many triggers were set to run? It would be interesting to know the memory and CPU usage of the Continua Server service when this happened. If this type of failure happens more than once, it would be useful to enable debug logging overnight and then send the debug log and a diagnostics report (downloaded from the event log page) to support@finalbuilder.com so we can troubleshoot further.
Thank Dave, let me check if the errors persists, the repositories were showing an Error status.