Configuring geekblox server

You might run into a few problems with geekblox server configuration. Using our freepuppet-helper for both geekblox servers fela and femi threw one or both of these error:

remote: Could not retrieve hostname: getaddrinfo: Name or service not known
remote: warning: Could not retrieve fact fqdn

It seems that the default configurations of these servers require us to modify the dns and host settings of the server itself. Here's are files to check, if you run into these errors.

  • /etc/hostname
  • /etc/hosts
  • /etc/resolv.conf

On fela this is what they look like respectively, you should replace fela below with the actual server name and correct ip address.



/etc/hosts       localhost       fela

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters



/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.

SSH Connection Problems

When working on geekblox (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.

Last modified 10 years ago Last modified on Apr 28, 2012, 7:19:24 PM