From 130abef98a5df08291042cce6a8efc8a089a244f Mon Sep 17 00:00:00 2001 From: James Shubin Date: Tue, 6 May 2014 10:23:05 -0400 Subject: Add FAQ item about common puppet failures and the workaround. --- DOCUMENTATION.md | 9 +++++++++ puppet-gluster-documentation.pdf | Bin 229212 -> 230983 bytes 2 files changed, 9 insertions(+) diff --git a/DOCUMENTATION.md b/DOCUMENTATION.md index 6f50993..b37f0b1 100644 --- 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 index ef6f2f1..27d00d6 100644 Binary files a/puppet-gluster-documentation.pdf and b/puppet-gluster-documentation.pdf differ -- cgit