Connective issues while connecting with bitbucket

[mani]

HI Team,

We are seeing continues timeouts while pushing from our jenkins to bitbucket. This is causing lot of issues and blocking our releases. Please let us know the solution to overcome the same.

Error:

Fatal error: Can not push to origin:
To ssh://git@bitbucket.org/belk_ecom/xxxxxx.git
45909f0..a098d4d feature-mtl -> feature-xxxxx
packet_write_wait: Connection to 104.192.141.1 port 22: Broken pipe
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly

Regards,

Manikanta A

[Fabio Racobaldo _Herzum_ · Accepted solution]

Hi @mani ,

it seems to be not related to a bitbucket issue. Please review the connection settings :

• https://askubuntu.com/questions/127369/how-to-prevent-write-failed-broken-pipe-on-ssh-connection
• http://thomas-cokelaer.info/blog/2017/05/packet_write_wait-connection-to-xxx-broken-pipe/
• https://communities.vmware.com/t5/VMware-Workstation-Player/SSH-connections-dropped-due-to-QoS-flags/m-p/1408691

Hope this helps,

Fabio

[Nithinraj Mohanraj]

Hi @Fabio Racobaldo _Herzum_ ,

I have the same issue on my laptop (Ubuntu 18.04) as well as my desktop machine. I had been committing changes to my bitbucket repo regularly from the same machines but they starting throwing this error today, and this is the first time I am facing this issue. Note, I have not altered any of my system settings.

Error:

--------------

Counting objects: 8, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (8/8), done.
Writing objects: 100% (8/8), 364.36 KiB | 3.09 MiB/s, done.
Total 8 (delta 5), reused 0 (delta 0)
packet_write_wait: Connection to 104.192.141.1 port 22: Broken pipe
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly

--------------

I tried changing the connection settings as mentioned in your previous reply but it did not solve the problem. The workarounds suggested in those posts are related to setting the SSH client changes, but I dont think this change is required especially that my laptop & desktop had been working fine with code commits all this while without those SSH config changes. It looks like some kind of server side issue.