Error replicating data to Cloud

[KEMBL]

Hello guys,

 

Server PlasticSCM-5.4.16.734-linux-server-binaries.zip

Client: Plastic SCM-5.4.16.734

 

I cannot replicate to Cloud I tried big branch and small branch and error the same like below (numbers are different):

 

2016-03-06 19:10:09,062  root at  INFO  ChannelCall - recb:   897|rect:  0|sentb:   481|sendt:  0|queuedt:       1|prt:       1|th:   14|dest:   0|mt:       1|sert:   0|zip:   0|cpu:       0|   189.128.65.136|GetStatus
2016-03-06 19:10:11,273  root at  INFO  ChannelCall - recb:   897|rect:  1|sentb:   481|sendt:  0|queuedt:       0|prt:       1|th:   14|dest:   0|mt:       0|sert:   0|zip:   1|cpu:       0|   189.128.65.136|GetStatus
2016-03-06 19:10:13,485  root at  INFO  ChannelCall - recb:   897|rect:  0|sentb:   481|sendt:  1|queuedt:       0|prt:       1|th:   14|dest:   0|mt:       0|sert:   0|zip:   0|cpu:       0|   189.128.65.136|GetStatus
2016-03-06 19:10:15,306  root at  ERROR Replication - Error replicating data. The data for revision 42177 (segment 0) cannot be written on rep 2708..   at Codice.CM.Common.Blobs.BlobHandler.Write (Codice.CM.Common.Blobs.BlobData data) [0x00000] in <filename unknown>:0
  at Codice.CM.Common.Blobs.ParallelBlobsWriter.a (System.Object A_0) [0x00000] in <filename unknown>:0
2016-03-06 19:10:15,698  root at  INFO  ChannelCall - recb:   897|rect:  0|sentb:  1482|sendt:  0|queuedt:       0|prt:       1|th:   14|dest:   0|mt:       0|sert:   1|zip:   0|cpu:       0|   189.128.65.136|GetStatus
2016-03-06 19:10:29,935  root at  ERROR Replication - Error processing replication operation. The data for revision 42177 (segment 0) cannot be written on rep 2708..   at Codice.CM.Common.Blobs.BlobHandler.Write (Codice.CM.Common.Blobs.BlobData data) [0x00000] in <filename unknown>:0
  at Codice.CM.Common.Blobs.ParallelBlobsWriter.a (System.Object A_0) [0x00000] in <filename unknown>:0
2016-03-06 19:10:29,936  root at  INFO  ChannelCall - recb:     0|rect:  0|sentb:     0|sendt:  0|queuedt:       0|prt:   96878|th:   54|dest:   0|mt:       0|sert:   0|zip:   0|cpu:       0|   189.128.65.136|RemotePushOperation
2016-03-06 19:10:29,937  root at  INFO  ChannelCall - recb:   803|rect:  0|sentb:   344|sendt:  1|queuedt:       0|prt:   14028|th:   14|dest:   0|mt:   14027|sert:   0|zip:   0|cpu:       0|   189.128.65.136|Cancel
2016-03-06 19:11:02,721 (null) root at (null) INFO  Channel - Connection    2 from 189.128.65.136 closed
 

Also I attached screenshot with replication error.

[manu]

Hi there!

 

can you please check the date setting you have at the Plastic SCM server machine? We've seen that error when the Plastic SCM client (Direct checkin mode) or the Plastic SCM server (pull/push mode) were having outdated settings.

 

Can you check the machine setting and post them here? Date and time and region should be enough.

[KEMBL]

Time settings seem normal, please look at the screenshot.

 

About region I am not sure, we rent the server in Digitalocean, according to GeoIP is situated in US, California, San Francisco. Should I switch server timezone from EST to San Francisco PST time?

[manu]

Hello we can't find errors related with your replica operation, we can't find data push operation either.

 

Is it possible you may have some sort of firewall (PC, router, enterprise) dropping the push operation to the Plastic SCM cloud?

 

Can you retry the operation giving us precise information about when it's started and when it fails? Local server log file will be also useful.

 

Thanks!

[KEMBL]

Thank you for an answer! I made new experiment:

 

* stopped server

* removed old log

* started server

* performed push of relatively small branch

* stopped server after the error

* sent log to you

 

so log file has only information related to replication try. I have sent that log file to your private mail in the forum (who knows what private info it could contain).

 

Also, I have 9.4Gb free on plastic server partition and time on my machine in EST (GMT -5)  is well synchronised, and no firewall rules at all during the experiment:

 

# iptables -t nat -nvL
Chain PREROUTING (policy ACCEPT 5 packets, 256 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain INPUT (policy ACCEPT 5 packets, 256 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 400 packets, 25513 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain POSTROUTING (policy ACCEPT 400 packets, 25513 bytes)
 pkts bytes target     prot opt in     out     source               destination
 

[manu]

Thanks, let follow up this issue using private messages.

[KEMBL]

I tested replication from Plastic server on my windows machine and it works fine.

But from Ubuntu I still cannot do it. I saw that windows tries to connect 168.61.57.206:443 and check this port accessibility from Ubuntu, it was opened without any problems.

What can I do to help solve this problem? Will remote access to our server and repo make the situation clearer for you?

 

P.S. at least one workaround I have now - try to move SQLite files to Windows server and push data from it.

[manu]

Do you think it's possible to create a VM with your Ubuntu machine, remove everything you won't to share and send the machine to us?

 

Also, If you tell me your Ubuntu version I can try to reproduce the issue.