Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

SSH connection client_loop: send disconnect: Broken pipe

Mauro Ciancio
Mauro Ciancio April 26, 2022

Hi, I'm having intermittent errors when pulling from bitbucket.

It fails with

client_loop: send disconnect: Broken pipe

 

It's kind of random, sometimes it works, sometimes it doesnt.

 

This is the ouput when running

ssh -Tvvvv git@bitbucket.org

 

OpenSSH_8.2p1 Ubuntu-4ubuntu0.4, OpenSSL 1.1.1f 31 Mar 2020
debug1: Reading configuration data /home/jenkins/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 18: Applying options for *
debug2: resolving "bitbucket.org" port 22
debug2: ssh_connect_direct
debug1: Connecting to bitbucket.org [104.192.141.1] port 22.
debug1: Connection established.
debug1: identity file /home/jenkins/.ssh/id_rsa type 0
debug1: identity file /home/jenkins/.ssh/id_rsa-cert type -1
debug1: identity file /home/jenkins/.ssh/id_dsa type -1
debug1: identity file /home/jenkins/.ssh/id_dsa-cert type -1
debug1: identity file /home/jenkins/.ssh/id_ecdsa type -1
debug1: identity file /home/jenkins/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/jenkins/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/jenkins/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/jenkins/.ssh/id_ed25519 type -1
debug1: identity file /home/jenkins/.ssh/id_ed25519-cert type -1
debug1: identity file /home/jenkins/.ssh/id_ed25519_sk type -1
debug1: identity file /home/jenkins/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/jenkins/.ssh/id_xmss type -1
debug1: identity file /home/jenkins/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.4
debug1: Remote protocol version 2.0, remote software version conker_daf2fe3bd1 e20c704b8464
debug1: no match: conker_daf2fe3bd1 e20c704b8464
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to bitbucket.org:22 as 'git'
debug3: hostkeys_foreach: reading file "/home/jenkins/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /home/jenkins/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from bitbucket.org
debug3: order_hostkeyalgs: prefer hostkeyalgs: rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c
debug2: host key algorithms: rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ecdsa-sha2-nistp256@openssh.com,ssh-ed25519,sk-ssh-ed25519@openssh.com
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,ext-info-s
debug2: host key algorithms: ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss
debug2: ciphers ctos: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,chacha20-poly1305@openssh.com
debug2: ciphers stoc: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,chacha20-poly1305@openssh.com
debug2: MACs ctos: hmac-sha2-256-etm@openssh.com,hmac-sha2-256,hmac-sha1,hmac-sha1-96
debug2: MACs stoc: hmac-sha2-256-etm@openssh.com,hmac-sha2-256,hmac-sha1,hmac-sha1-96
debug2: compression ctos: none
debug2: compression stoc: none
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug1: kex: algorithm: curve25519-sha256@libssh.org
debug1: kex: host key algorithm: rsa-sha2-512
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: Server host key: ssh-rsa SHA256:zzXQOXSRBEiUtuE8AikJYKwbHaxvSc0ojez9YXaGp1A
debug3: hostkeys_foreach: reading file "/home/jenkins/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /home/jenkins/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from bitbucket.org
debug3: hostkeys_foreach: reading file "/home/jenkins/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /home/jenkins/.ssh/known_hosts:2
debug3: load_hostkeys: loaded 1 keys from 104.192.141.1
debug1: Host 'bitbucket.org' is known and matches the RSA host key.
debug1: Found key in /home/jenkins/.ssh/known_hosts:1
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: /home/jenkins/.ssh/id_rsa RSA SHA256:z/bGYI+ZZ+HGxBnDSB731QE2eJHn+ikMO0NsOyFUfJg
debug1: Will attempt key: /home/jenkins/.ssh/id_dsa 
debug1: Will attempt key: /home/jenkins/.ssh/id_ecdsa 
debug1: Will attempt key: /home/jenkins/.ssh/id_ecdsa_sk 
debug1: Will attempt key: /home/jenkins/.ssh/id_ed25519 
debug1: Will attempt key: /home/jenkins/.ssh/id_ed25519_sk 
debug1: Will attempt key: /home/jenkins/.ssh/id_xmss 
debug2: pubkey_prepare: done
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-rsa,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp521,ssh-dss-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred gssapi-with-mic,publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /home/jenkins/.ssh/id_rsa RSA SHA256:z/bGYI+ZZ+HGxBnDSB731QE2eJHn+ikMO0NsOyFUfJg
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 60
debug1: Server accepts key: /home/jenkins/.ssh/id_rsa RSA SHA256:z/bGYI+ZZ+HGxBnDSB731QE2eJHn+ikMO0NsOyFUfJg
debug3: sign_and_send_pubkey: RSA SHA256:z/bGYI+ZZ+HGxBnDSB731QE2eJHn+ikMO0NsOyFUfJg
debug3: sign_and_send_pubkey: signing using rsa-sha2-512 SHA256:z/bGYI+ZZ+HGxBnDSB731QE2eJHn+ikMO0NsOyFUfJg
debug3: send packet: type 50
debug3: receive packet: type 52
debug1: Authentication succeeded (publickey).
Authenticated to bitbucket.org ([104.192.141.1]:22).
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug3: send packet: type 90
debug1: Entering interactive session.
debug1: pledge: network
debug3: receive packet: type 91
debug2: channel_input_open_confirmation: channel 0: callback start
debug2: fd 3 setting TCP_NODELAY
debug3: ssh_packet_set_tos: set IP_TOS 0x08
debug2: client_session2_setup: id 0
debug1: Sending environment.
debug3: Ignored env SHELL
debug3: Ignored env SUDO_GID
debug1: Sending env LC_ADDRESS = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug1: Sending env LC_NAME = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env SUDO_COMMAND
debug1: Sending env LC_MONETARY = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env SUDO_USER
debug3: Ignored env PWD
debug3: Ignored env LOGNAME
debug3: Ignored env HOME
debug1: Sending env LC_PAPER = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug1: Sending env LANG = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env LS_COLORS
debug3: Ignored env LESSCLOSE
debug1: Sending env LC_IDENTIFICATION = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env TERM
debug3: Ignored env LESSOPEN
debug3: Ignored env USER
debug3: Ignored env SHLVL
debug1: Sending env LC_TELEPHONE = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug1: Sending env LC_MEASUREMENT = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug1: Sending env LC_TIME = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env PATH
debug3: Ignored env SUDO_UID
debug3: Ignored env MAIL
debug1: Sending env LC_NUMERIC = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env OLDPWD
debug3: Ignored env _
debug2: channel 0: request shell confirm 1
debug3: send packet: type 98
debug2: channel_input_open_confirmation: channel 0: callback done
debug2: channel 0: open confirm rwindow 2097152 rmax 32768
debug3: send packet: type 1
client_loop: send disconnect: Broken pipe

 

Same command, when seconds after, it works:

OpenSSH_8.2p1 Ubuntu-4ubuntu0.4, OpenSSL 1.1.1f 31 Mar 2020
debug1: Reading configuration data /home/jenkins/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 18: Applying options for *
debug2: resolving "bitbucket.org" port 22
debug2: ssh_connect_direct
debug1: Connecting to bitbucket.org [104.192.141.1] port 22.
debug1: Connection established.
debug1: identity file /home/jenkins/.ssh/id_rsa type 0
debug1: identity file /home/jenkins/.ssh/id_rsa-cert type -1
debug1: identity file /home/jenkins/.ssh/id_dsa type -1
debug1: identity file /home/jenkins/.ssh/id_dsa-cert type -1
debug1: identity file /home/jenkins/.ssh/id_ecdsa type -1
debug1: identity file /home/jenkins/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/jenkins/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/jenkins/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/jenkins/.ssh/id_ed25519 type -1
debug1: identity file /home/jenkins/.ssh/id_ed25519-cert type -1
debug1: identity file /home/jenkins/.ssh/id_ed25519_sk type -1
debug1: identity file /home/jenkins/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/jenkins/.ssh/id_xmss type -1
debug1: identity file /home/jenkins/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.4
debug1: Remote protocol version 2.0, remote software version conker_daf2fe3bd1 cd14b4b1fb3b
debug1: no match: conker_daf2fe3bd1 cd14b4b1fb3b
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to bitbucket.org:22 as 'git'
debug3: hostkeys_foreach: reading file "/home/jenkins/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /home/jenkins/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from bitbucket.org
debug3: order_hostkeyalgs: prefer hostkeyalgs: rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c
debug2: host key algorithms: rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ecdsa-sha2-nistp256@openssh.com,ssh-ed25519,sk-ssh-ed25519@openssh.com
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,ext-info-s
debug2: host key algorithms: ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss
debug2: ciphers ctos: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,chacha20-poly1305@openssh.com
debug2: ciphers stoc: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,chacha20-poly1305@openssh.com
debug2: MACs ctos: hmac-sha2-256-etm@openssh.com,hmac-sha2-256,hmac-sha1,hmac-sha1-96
debug2: MACs stoc: hmac-sha2-256-etm@openssh.com,hmac-sha2-256,hmac-sha1,hmac-sha1-96
debug2: compression ctos: none
debug2: compression stoc: none
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug1: kex: algorithm: curve25519-sha256@libssh.org
debug1: kex: host key algorithm: rsa-sha2-512
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: Server host key: ssh-rsa SHA256:zzXQOXSRBEiUtuE8AikJYKwbHaxvSc0ojez9YXaGp1A
debug3: hostkeys_foreach: reading file "/home/jenkins/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /home/jenkins/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from bitbucket.org
debug3: hostkeys_foreach: reading file "/home/jenkins/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /home/jenkins/.ssh/known_hosts:2
debug3: load_hostkeys: loaded 1 keys from 104.192.141.1
debug1: Host 'bitbucket.org' is known and matches the RSA host key.
debug1: Found key in /home/jenkins/.ssh/known_hosts:1
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: /home/jenkins/.ssh/id_rsa RSA SHA256:z/bGYI+ZZ+HGxBnDSB731QE2eJHn+ikMO0NsOyFUfJg
debug1: Will attempt key: /home/jenkins/.ssh/id_dsa 
debug1: Will attempt key: /home/jenkins/.ssh/id_ecdsa 
debug1: Will attempt key: /home/jenkins/.ssh/id_ecdsa_sk 
debug1: Will attempt key: /home/jenkins/.ssh/id_ed25519 
debug1: Will attempt key: /home/jenkins/.ssh/id_ed25519_sk 
debug1: Will attempt key: /home/jenkins/.ssh/id_xmss 
debug2: pubkey_prepare: done
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ssh-rsa,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ssh-dss-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred gssapi-with-mic,publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /home/jenkins/.ssh/id_rsa RSA SHA256:z/bGYI+ZZ+HGxBnDSB731QE2eJHn+ikMO0NsOyFUfJg
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 60
debug1: Server accepts key: /home/jenkins/.ssh/id_rsa RSA SHA256:z/bGYI+ZZ+HGxBnDSB731QE2eJHn+ikMO0NsOyFUfJg
debug3: sign_and_send_pubkey: RSA SHA256:z/bGYI+ZZ+HGxBnDSB731QE2eJHn+ikMO0NsOyFUfJg
debug3: sign_and_send_pubkey: signing using rsa-sha2-512 SHA256:z/bGYI+ZZ+HGxBnDSB731QE2eJHn+ikMO0NsOyFUfJg
debug3: send packet: type 50
debug3: receive packet: type 52
debug1: Authentication succeeded (publickey).
Authenticated to bitbucket.org ([104.192.141.1]:22).
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug3: send packet: type 90
debug1: Entering interactive session.
debug1: pledge: network
debug3: receive packet: type 91
debug2: channel_input_open_confirmation: channel 0: callback start
debug2: fd 3 setting TCP_NODELAY
debug3: ssh_packet_set_tos: set IP_TOS 0x08
debug2: client_session2_setup: id 0
debug1: Sending environment.
debug3: Ignored env SHELL
debug3: Ignored env SUDO_GID
debug1: Sending env LC_ADDRESS = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug1: Sending env LC_NAME = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env SUDO_COMMAND
debug1: Sending env LC_MONETARY = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env SUDO_USER
debug3: Ignored env PWD
debug3: Ignored env LOGNAME
debug3: Ignored env HOME
debug1: Sending env LC_PAPER = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug1: Sending env LANG = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env LS_COLORS
debug3: Ignored env LESSCLOSE
debug1: Sending env LC_IDENTIFICATION = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env TERM
debug3: Ignored env LESSOPEN
debug3: Ignored env USER
debug3: Ignored env SHLVL
debug1: Sending env LC_TELEPHONE = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug1: Sending env LC_MEASUREMENT = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug1: Sending env LC_TIME = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env PATH
debug3: Ignored env SUDO_UID
debug3: Ignored env MAIL
debug1: Sending env LC_NUMERIC = C.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env OLDPWD
debug3: Ignored env _
debug2: channel 0: request shell confirm 1
debug3: send packet: type 98
debug2: channel_input_open_confirmation: channel 0: callback done
debug2: channel 0: open confirm rwindow 2097152 rmax 32768
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
authenticated via ssh key.

You can use git to connect to Bitbucket. Shell access is disabled
debug3: receive packet: type 98
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug3: receive packet: type 96
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug2: channel 0: obuf empty
debug2: channel 0: chan_shutdown_write (i0 o1 sock -1 wfd 5 efd 6 [write])
debug2: channel 0: output drain -> closed
debug3: receive packet: type 97
debug2: channel 0: rcvd close
debug2: channel 0: chan_shutdown_read (i0 o3 sock -1 wfd 4 efd 6 [write])
debug2: channel 0: input open -> closed
debug3: channel 0: will not send data after close
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug3: send packet: type 97
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
#0 client-session (t4 r0 i3/0 o3/0 e[write]/0 fd -1/-1/6 sock -1 cc -1)

debug3: send packet: type 1
debug3: fd 1 is not O_NONBLOCK
Transferred: sent 4024, received 2404 bytes, in 0.0 seconds
Bytes per second: sent 134912.9, received 80599.1
debug1: Exit status 0





any ideas?
Answer
Watch
Like Be the first to like this
4531 views

1 answer

0 votes
Ben
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 26, 2022

G'day Mauro!

Based on the output you have provided, this appears to be a local network issue - where the connection is intermittently dropping out when attempting to connect to Bitbucket.

Please run and provide the following output from these commands (you may redact sensitive info):

tracert bitbucket.org (or traceroute bitbucket.org)
nslookup bitbucket.org (or dig bitbucket.org)
ping bitbucket.org

We have further local network troubleshooting instructions here also:
https://confluence.atlassian.com/bbkb/troubleshooting-network-issues-389778693.html

Cheers!

- Ben (Bitbucket Cloud Support)

View More Comments
Mauro Ciancio
Mauro Ciancio April 27, 2022

Hey, thanks, here's the output!

$ traceroute bitbucket.org
traceroute to bitbucket.org (104.192.141.1),
30 hops max,
60 byte packets
1 * * *
2 10.74.196.71 (10.74.196.71) 0.950 ms 10.74.196.69 (10.74.196.69) 1.127 ms 10.74.196.77 (10.74.196.77) 1.007 ms
3 138.197.248.228 (138.197.248.228) 1.261 ms 138.197.248.230 (138.197.248.230) 1.253 ms 138.197.251.8 (138.197.251.8) 1.477 ms
4 138.197.248.14 (138.197.248.14) 1.237 ms 138.197.248.16 (138.197.248.16) 1.458 ms 1.451 ms
5 138.197.244.38 (138.197.244.38) 1.444 ms 138.197.244.46 (138.197.244.46) 1.436 ms 138.197.244.38 (138.197.244.38) 1.426 ms
6 99.83.89.106 (99.83.89.106) 1.891 ms 1.164 ms 1.126 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
$ dig bitbucket.org

; <<>> DiG 9.16.1-Ubuntu <<>> bitbucket.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9211
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;bitbucket.org. IN A

;; ANSWER SECTION:
bitbucket.org. 60 IN A 104.192.141.1

;; Query time: 19 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Apr 27 15: 07: 23 -03 2022
;; MSG SIZE rcvd: 58

$ ping bitbucket.org
PING bitbucket.org (104.192.141.1) 56(84) bytes of data.
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=1 ttl=118 time=1.65 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=2 ttl=118 time=1.02 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=3 ttl=118 time=1.00 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=4 ttl=118 time=1.01 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=5 ttl=118 time=1.07 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=6 ttl=118 time=1.02 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=7 ttl=118 time=1.01 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=8 ttl=118 time=1.01 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=9 ttl=118 time=1.01 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=10 ttl=118 time=1.03 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=11 ttl=118 time=1.01 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=12 ttl=118 time=1.04 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=13 ttl=118 time=1.04 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=14 ttl=118 time=1.01 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=15 ttl=118 time=1.00 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=16 ttl=118 time=1.02 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=17 ttl=118 time=1.05 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=18 ttl=118 time=1.04 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=19 ttl=118 time=1.03 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=20 ttl=118 time=1.03 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=21 ttl=118 time=1.03 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=22 ttl=118 time=1.32 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=23 ttl=118 time=1.07 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=24 ttl=118 time=1.06 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=25 ttl=118 time=1.08 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=26 ttl=118 time=1.07 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=27 ttl=118 time=1.02 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=28 ttl=118 time=1.03 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=29 ttl=118 time=1.06 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=30 ttl=118 time=1.05 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=31 ttl=118 time=1.02 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=32 ttl=118 time=1.02 ms
64 bytes from 104.192.141.1 (104.192.141.1): icmp_seq=33 ttl=118 time=1.02 ms
^C
--- bitbucket.org ping statistics ---
33 packets transmitted,
33 received,
0% packet loss, time 32037ms
rtt min/avg/max/mdev = 1.003/1.059/1.649/0.117 ms
Like
Ben
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 27, 2022

Hey Mauro,

Thank you for providing the output.

I am unable to reproduce this issue on my end, therefore it appears that this may be a local network issue.
Are you able to try to perform SSH operations on a different network and monitor to see if you receive the same result?

Cheers!

- Ben (Bitbucket Cloud Support)

Like
Mauro Ciancio
Mauro Ciancio April 28, 2022

That's right, it only fails in a specific network (digital ocean). From different networks it works great.

I wasnt sure to raise a ticket with digitalocean, but it's seems its their issue, right?

Any hint in how to raise an issue with them?

Like
Ben
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 28, 2022

Hi Mauro,

If the connectivity is fine when using other networks - I believe that this is a fairly safe assumption.  
I am not too familiar with DigitalOcean to be honest, however I have found a support contact page that may be of assistance to you:
https://www.digitalocean.com/products/support

Cheers!

- Ben (Bitbucket Cloud Support)

Like
Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
TAGS
AUG Leaders

Atlassian Community Events

    See all events