diff options
| author | James Shubin <james@shubin.ca> | 2014-05-06 10:23:05 -0400 |
|---|---|---|
| committer | James Shubin <james@shubin.ca> | 2014-05-06 10:23:05 -0400 |
| commit | 130abef98a5df08291042cce6a8efc8a089a244f (patch) | |
| tree | e30a50da4116c4d96764ef1042646cd3886c4d50 | |
| parent | a80a7a64835d450c168c4cede18ed156095a4fd7 (diff) | |
| download | puppet-gluster-130abef98a5df08291042cce6a8efc8a089a244f.tar.gz puppet-gluster-130abef98a5df08291042cce6a8efc8a089a244f.tar.xz puppet-gluster-130abef98a5df08291042cce6a8efc8a089a244f.zip | |
Add FAQ item about common puppet failures and the workaround.
| -rw-r--r-- | DOCUMENTATION.md | 9 | ||||
| -rw-r--r-- | puppet-gluster-documentation.pdf | bin | 229212 -> 230983 bytes |
2 files changed, 9 insertions, 0 deletions
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 Binary files differindex ef6f2f1..27d00d6 100644 --- a/puppet-gluster-documentation.pdf +++ b/puppet-gluster-documentation.pdf |