SSH receiving kill signal while attempting to connect

Build Environment
1

Hi – I’m trying to have a docker circleci/node container copy a file to another server, and it just hangs and quits in the middle of any type of ssh connection. I have the keys added and an ssh_add_keys step, and this tends to happen:

OpenSSH_6.7p1 Debian-5+deb8u7, OpenSSL 1.0.1t  3 May 2016

debug1: Reading configuration data /home/circleci/.ssh/config

debug1: /home/circleci/.ssh/config line 1: Applying options for *

debug1: Reading configuration data /etc/ssh/ssh_config

debug1: /etc/ssh/ssh_config line 19: Applying options for *

debug1: Executing proxy command: exec ssh -q -A circleci@xx.xx.xx.xxx

debug1: permanently_drop_suid: 3434

debug1: key_load_public: No such file or directory

debug1: identity file /home/circleci/.ssh/id_rsa type -1

debug1: key_load_public: No such file or directory

debug1: identity file /home/circleci/.ssh/id_rsa-cert type -1

debug1: key_load_public: No such file or directory

debug1: identity file /home/circleci/.ssh/id_rsa type -1

debug1: key_load_public: No such file or directory

debug1: identity file /home/circleci/.ssh/id_rsa-cert type -1

debug1: Enabling compatibility mode for protocol 2.0

debug1: Local version string SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u7

Received 'killed' signal

Others who get kill signals say this is the executor running out of memory. could ssh really be pushing it over?

2

Is this the CircleCI post-build SSH, or something you are doing in your build yourself?

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.