Add FAQ item about common puppet failures and the workaround.

kiwnix · May 6, 2014 · 130abef · 130abef
1 parent a80a7a6
commit 130abef
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 0 deletions.
diff --git a/DOCUMENTATION.md b/DOCUMENTATION.md
@@ -289,6 +289,15 @@ puppet node deactivate HOSTNAME
 for each host you're using, and that you've removed all of the files from the
 brick directories on each host.
 
+###Puppet runs fail with "Connection refused - connect(2)" errors.
+
+You may see a "_Connection refused - connect(2)_" message when running puppet.
+This typically happens if your puppet vm guest is overloaded. When running high
+guest counts on your laptop, or running without hardware virtualization support
+this is quite common. Another common causes of this is if your domain type is
+set to _qemu_ instead of the accelerated _kvm_. Since the _qemu_ domain type is
+much slower, puppet timeouts and failures are common when it doesn't respond.
+
 ###Provisioning fails with: "Can't open /dev/sdb1 exclusively."
 
 If when provisioning you get an error like:

diff --git a/puppet-gluster-documentation.pdf b/puppet-gluster-documentation.pdf