Changes between Version 1 and Version 2 of configuring_a_geexblox_server

Timestamp:

Apr 21, 2012, 9:46:30 PM (13 years ago)

Author:

Ross

Comment:

--

configuring_a_geexblox_server

@@ -43 +43 @@
 
 /etc/resolve.conf should only look like this for initial configuration.  Puppet should change those values to the appropriate values.  This is only for getting the initial puppet configurations working properly.
+
+=== Connection Problems ===
+
+When working on geeblox (or probably any server we do not have console access too), it's possible using freepuppet-helper to block ssh access to the server.  Since monkeysphere configuration files get loaded before the monkeysphere packages get installed, the ssh config can expect the monkeysphere and without it will fail.  In order to avoid this, '''you should keep a live ssh session on the remote machine at all times'''.  If you do lock yourself out, but still have a live session running, modify the following files to grant ssh access.
+
+'''/etc/ssh/sshd_config''' make sure you have a section that looks like this:
+
+{{{
+RSAAuthentication yes
+
+PubkeyAuthentication yes
+
+# AuthorizedKeysFile /var/lib/monkeysphere/authorized_keys/%u
+AuthorizedKeysFile /root/.ssh/authorized_keys
+}}}
+
+You can also add password access by setting "PasswordAuthentication yes".
+
+If '''/root/.ssh/config''' has anything in it, comment out those lines.  Then run:
+
+{{{
+/etc/init.d/ssh reload
+}}}
+
+That should give you ssh access again.