astenios Posted January 26, 2013 Report Share Posted January 26, 2013 Hola!! Our small team uses Plastic (4.1.10.378) since year ago. All works fine in the office but now I need to connect mi laptop to work from home. When I try to sync my laptop with the remote server I have a timeout error. The server log says: 2013-01-26 07:58:41,721 00000000-0000-0000-0000-000000000000 XAVI-VAIO INFO Operations - Get repository info 1 2013-01-26 07:58:41,722 INFO ChannelCall - recb: 750|rect: 0|sentb: 545|sendt: 0|prt: 2|th:141794192|dest: 0|mt: 0|sert: 1|zip: 0| 172.20.1.223|GetRepositoryInfo 2013-01-26 07:58:51,776 (null) (null) INFO Channel - Tcp transport error. ReceiveMessageStatus Connection closed 2013-01-26 07:58:51,777 (null) (null) INFO Channel - conn 27697 Tcp transport error. Connection closed Link to comment Share on other sites More sharing options...
calbzam Posted January 28, 2013 Report Share Posted January 28, 2013 Hola!! The server log is not relevant I'm afraid. This message is just the socket log, it logs each time a conn gets closed. Are you using "sync view"? Does it get the outgoing changes? Can you try to ping the server from your home to be sure it is accessible? Thanks, Best regards, Carlos Link to comment Share on other sites More sharing options...
astenios Posted February 11, 2013 Author Report Share Posted February 11, 2013 Hi Carlos! I can connect to the server using "sync view". I see all the branches that are pending sync, but when I start the synchronization, after a while I get an error that can not connect to the server or has received an unexpected response. In the log all I see is that the connection has been closed. Xavi Link to comment Share on other sites More sharing options...
manu Posted February 11, 2013 Report Share Posted February 11, 2013 Hi Astenios, in order to debug the issue can you please try a single branch replication from the command line? The command is: cm replicate You can use the "--help" parameter to retrieve examples. Link to comment Share on other sites More sharing options...
astenios Posted February 15, 2013 Author Report Share Posted February 15, 2013 This is my console output: D:\Apps\Console2>cm replicate br:/main/2013.02@rep:J2EE@repserver:172.20.1.39:8087 rep:feina@xavi-vaio:8087 --trmode=name OperationStartingFetch OperationStartingFetch OperationStartingFetch OperationStartingFetch OperationStartingFetch OperationStartingFetch OperationStartingFetch OperationStartingFetch OperationStartingFetch OperationStartingFetch CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset CalculatingInitialChangeset Error Error: Se produjo un error durante el intento de conexión ya que la parte conectada no respondió adecuadamente tras un periodo de tiempo, o bien se produjo un error en la conexión establecida ya que el host conectado no ha podido responder 172.20.1.39:8087: 172.20.1.39:8087 Could it be the VPN acces adapter?? Link to comment Share on other sites More sharing options...
manu Posted February 18, 2013 Report Share Posted February 18, 2013 Hi! It seems that the issue is with the connection, I guess that it's fine for short connections but it breaks the long ones. Link to comment Share on other sites More sharing options...
astenios Posted February 18, 2013 Author Report Share Posted February 18, 2013 I'll wait to next 4.2 release and then I'll try the solution posted here: PlasticSCM @work -> Private Bitbucket Repo -> PlasticSCM @home Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.