Changes between Version 6 and Version 7 of debug-server-to-server-connections


Ignore:
Timestamp:
Dec 22, 2014, 9:51:16 AM (5 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • debug-server-to-server-connections

    v6 v7  
    1818Here are the top causes for the failures, and the remedies. Note: you may need to repeat the first one ''after'' fixing the problem with one of the later steps. A failure to connect sometimes seem to kill the ssh-agent.
    1919
    20  * The connecting server does not have SSH_AUTH_SOCK set. This is set in ~/.profile. If you are debugging, you may need to source this file. If you are scripting, be sure to manually set the environment variable: SSH_AUTH_SOCK=/root/.ssh-agent-socket/sock.
    21  * Something went wrong with ssh-agent on the connecting server. Fix: Stop and restart the service, check for existence of socket:
     20 * The connecting server does not have SSH_AUTH_SOCK set. This is set in ~/.profile. If you are debugging, you may need to source this file. If you are scripting, be sure to manually set the environment variable: SSH_AUTH_SOCK=/root/.ssh-agent-socket/sock. Test with:
    2221{{{
     22echo $SSH_AUTH_SOCK
     23}}}
     24 If you get no output, source the ~/.profile file:
     25{{{
     26source ~/.profile
     27}}}
     28 and try again.
     29 * Something went wrong with ssh-agent on the connecting server. Check for the existence of the socket file. If it's not there, fix: Stop and restart the service:
     30{{{
     31ls -l /root/.ssh-agent-socket
    2332sv stop ssh-agent-root
    2433sv start ssh-agent-root
    25 ls -l /root/.ssh-agent-socket
    2634}}}
    2735 * The target server does not have the latest version of the connecting server's OpenPGP key. Fix: refresh the key, reload the credentials, and test: