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

Timestamp:

Jun 17, 2015, 1:36:30 PM (10 years ago)

Author:

Jamie McClelland

Comment:

--

debug-server-to-server-connections

@@ -18 +18 @@
 Here 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.
 
- * 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:
+ * 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 on the ''connecting'' server with:
 {{{
 echo $SSH_AUTH_SOCK
@@ -27 +27 @@
 }}}
  and try again.
- * 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:
+ * 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 on the ''connecting'' server:
 {{{
 ls -l /root/.ssh-agent-socket
@@ -33 +33 @@
 sv start ssh-agent-root
 }}}
- * 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:
+ * The target server does not have the latest version of the connecting server's OpenPGP key. Fix on the ''target'' server: refresh the key, reload the credentials, and test:
 {{{
 monkeysphere-authentication refresh-keys <username>
@@ -42 +42 @@
 Note: The last cat command must produce a file with the connecting server's key or it will never work.
 
- * The connecting server has not published the latest version of it's key. Fix: determine the keyid of the server's secret key, and then publish it:
+ * The connecting server has not published the latest version of it's key. Fix on the ''connecting'' server: determine the keyid of the server's secret key, and then publish it:
 {{{
 gpg --list-secret-key
 gpg --keyserver keys.mayfirst.org --send-key <keyid>
 }}}
- Then, refresh the key on the target (see above).
- * The connecting server's OpenPGP key is expired. Fix: extend it:
+ Then, refresh the key on the ''target'' server (see above).
+ * The connecting server's OpenPGP key is expired. Fix on the ''connecting'' server: extend it:
 {{{
 mf-gpg-extend-root-expiration
@@ -61 +61 @@
 gpg --check-sigs <keyid>
 }}}
- Then, on the target server, see if any of them match the allowed certifiers:
+ Then, on the ''target'' server, see if any of them match the allowed certifiers:
 {{{
 monkeysphere-authentication list-id-certifiers