3.5. Developers Connecting to a Gear are Disconnected Immediately
When connecting directly to a gear, for example when a
git clone
is performed, a developer can authenticate successfully, but then be disconnected by the remote host. This could be due to PAM being misconfigured. An example of this error is shown in the output below.
rhc app create -n apps -t php -a testing
$ rhc app create -n apps -t php -a testing
Creating application 'testing'
==============================
Scaling: no
Gear Size: default
Cartridge: php
Namespace: apps
Password: ********
Your application's domain name is being propagated worldwide (this might take a minute)...
The authenticity of host 'testing-apps.example.com (x.x.x.x)' can't be established.
RSA key fingerprint is [...].
Are you sure you want to continue connecting (yes/no)? yes
Initialized empty Git repository in /home/test/testing/.git/
done
Error in git clone - Warning: Permanently added 'testing-apps.example.com' (RSA) to the list of known hosts.
Traceback (most recent call last):
File "/usr/bin/oo-trap-user", line 134, in <module>
read_env_vars()
File "/usr/bin/oo-trap-user", line 64, in read_env_vars
fp = open(os.path.expanduser('~/.env/') + env, 'r')
IOError: [Errno 13] Permission denied: '/var/lib/openshift/a7a330ee62ae467ca6d74cd0ce29742a/.env/OPENSHIFT_APP_NAME'
fatal: The remote end hung up unexpectedly
Ensure that PAM is correctly configured by performing the steps located in the Configuring PAM section of the OpenShift Enterprise Deployment Guide. Note that
pam_selinux
should be changed to pam_openshift
in /etc/pam.d/sshd
, and a line with pam_namespace.so
should be at the end of each file modified. If your change management system overwrote these settings, ensure that your system will retain the correctly modified files in the future.