Hi No connection could be made because the target machine actively refused it ::1:21234
sounds like a firewall setting to me check the firewall, and make sure that port 21234 (the one used by ccnet) is allowed to pass on all machines with kind regards Ruben Willems On Thu, Mar 19, 2009 at 10:28 AM, Matt Chatterley <[email protected] > wrote: > Hi all, > > My turn to have a problem now! > > Since the last batch of Vista updates installed on our buildservers > (believe this included .NET 3.5 SP1 but would have to check), we now get > this error in our logs: > > 2009-03-19 09:23:18,715 [MigrationDbs.ECom.Stage4.RestoreUATDb:ERROR] > INTERNAL ERROR: No connection could be made because the target machine > actively refused it ::1:21234 > ---------- > System.Net.Sockets.SocketException: No connection could be made because the > target machine actively refused it ::1:21234 > > Server stack trace: > at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, > SocketAddress socketAddress) > at System.Net.Sockets.Socket.Connect(EndPoint remoteEP) > at > System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(EndPoint > ipEndPoint) > at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket() > at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String > machinePortAndSid, Boolean openNew) > at > System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage > msg, ITransportHeaders requestHeaders, Stream requestStream) > at > System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage > msg, ITransportHeaders requestHeaders, Stream requestStream, > ITransportHeaders& responseHeaders, Stream& responseStream) > at > System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage > msg) > > 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 ThoughtWorks.CruiseControl.Remote.ICruiseManager.GetProjectStatus() > at > ThoughtWorks.CruiseControl.Core.Triggers.ProjectTrigger.GetCurrentProjectStatus() > at ThoughtWorks.CruiseControl.Core.Triggers.ProjectTrigger.Fire() > at ThoughtWorks.CruiseControl.Core.Triggers.MultipleTrigger.Fire() > at ThoughtWorks.CruiseControl.Core.ProjectIntegrator.PollTriggers() > at ThoughtWorks.CruiseControl.Core.ProjectIntegrator.Integrate() > at ThoughtWorks.CruiseControl.Core.ProjectIntegrator.Run() > ---------- > > > This seems to break some of the triggers, but otherwise has relatively > little impact - it's very annoying, and cycles the logs a lot though! > > Out of ideas on how to resolve, so any suggestions would be most welcome! > > > Cheers, > > -- > Matt Chatterley > Mattched IT Ltd > http://www.mattchedit.com > UK Registered Company: 05861949 > >
