[Puppet Users] SSL Certificate errors - Migrating from build in webserver to Apache and Passenger
Hi All I've been running Puppet using the build in web server and I'm now moving to Apache and Passenger. I've completed the installation and started testing. If I run puppet agent --test --noop I get the following error (domain removed) Warning: Unable to fetch my node definition, but the agent run will continue: Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001...] Info: Retrieving plugin Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001...] Error: /File[/var/lib/puppet/lib]: Could not evaluate: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001] Could not retrieve file metadata for puppet://puppet/plugins: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001...] Error: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001...] Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Error: Could not send report: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001...] If I turn apache off and the built in webserver back on it all works. The server I'm running puppet on server that has a CNAME puppet that points to its real name ecm-rhl-001 Apache site is configured with ecm-rhl-001... as the servername and puppet... as server alias. The system returns 'ecm-rhl-001' for hostname and 'ecm-rhl-001' for hostname -f. The certificate has ecm-rhl-001... as its CN and puppet... as one of its alt names. Obviously the cert is OK as it works with the built in webserver. It looks like I'm missing something in the apache SSL or Passenger configuration but I have no idea what. I've tried various permutations of servername and serveralias without success. Changing the server name in the agent configuration so it users the real name instead of the CNAME also does not fix the issue. Any suggestions? Tom -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/f21d077a-14f8-4712-a0d6-8e8bfeb0652a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] HP-UX Puppet Init Script !!
Hi, I have been successfully able to install puppet on hu-ux, all I am looking is to run puppet agent from this server. Can someone please help me with the init script for puppet agent on HP-UX ?? It would be great if you have one, else if you can point me to the correct directions for creating one. Thanks, Rakesh K -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEJrXMXVgfa1QTGb4pV2SdCREpe1eJeR5BsNmtZKCvr9A1vn0w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] SSL Certificate errors - Migrating from build in webserver to Apache and Passenger
You should have several lines in your apache vhost pointing to specific ssl certs. Can you verify that all these paths are correct? Specifically the lines beginning with SSL in http://docs.puppetlabs.com/guides/passenger.html#create-and-enable-the-puppet-master-vhost On Sat, Mar 22, 2014 at 7:51 AM, Tom Hallam thalla...@gmail.com wrote: Hi All I've been running Puppet using the build in web server and I'm now moving to Apache and Passenger. I've completed the installation and started testing. If I run puppet agent --test --noop I get the following error (domain removed) Warning: Unable to fetch my node definition, but the agent run will continue: Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001...] Info: Retrieving plugin Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001...] Error: /File[/var/lib/puppet/lib]: Could not evaluate: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001] Could not retrieve file metadata for puppet://puppet/plugins: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001...] Error: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001...] Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Error: Could not send report: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001...] If I turn apache off and the built in webserver back on it all works. The server I'm running puppet on server that has a CNAME puppet that points to its real name ecm-rhl-001 Apache site is configured with ecm-rhl-001... as the servername and puppet... as server alias. The system returns 'ecm-rhl-001' for hostname and 'ecm-rhl-001' for hostname -f. The certificate has ecm-rhl-001... as its CN and puppet... as one of its alt names. Obviously the cert is OK as it works with the built in webserver. It looks like I'm missing something in the apache SSL or Passenger configuration but I have no idea what. I've tried various permutations of servername and serveralias without success. Changing the server name in the agent configuration so it users the real name instead of the CNAME also does not fix the issue. Any suggestions? Tom -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/f21d077a-14f8-4712-a0d6-8e8bfeb0652a%40googlegroups.comhttps://groups.google.com/d/msgid/puppet-users/f21d077a-14f8-4712-a0d6-8e8bfeb0652a%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Spencer Krum (619)-980-7820 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CADt6FWOQT9NbjK2NGXmegtnBqTVnRE7j%3Dtn_WyJxPn10%3DWZwYQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: SSL Certificate errors - Migrating from build in webserver to Apache and Passenger
Hi Just tried openssl s_client -connect puppet...:8140 -showcerts /dev/null /tmp/file To get the certificates from each server and they are not the same. I've checked /etc/puppet/ssl and the Pasenger configuration is giving me the same certificates as are in there. Can't find ones that match WebBricks certificates. Tom -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/c3960d51-8be5-4db6-8090-1d9c3c2b2a57%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] hiera could not find item
How can I check this , 'Cause in my nodes I received this?
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not find data item in any Hiera data file and no default supplied at
/etc/puppet/modules/ananke-base-utils/manifests/init.pp:42 on node
tm-ld168-senacWarning: Not using cache on failed catalogError: Could not
retrieve catalog; skipping run
this is the part of my code that I am having trouble:
38 class ananke-base-utils {
39
40 # variables from hiera
41
42 $conf_file= hiera($conf_ntp)
43 $cpath_ntp= hiera($conf_ntp_path)
44 $cpath_vim= hiera($conf_vim_path)
45 $package_name = hiera_array($packages_utils)
46
47
48 # install package based on distribuition
49 package {$package_name:
50 ensure = 'present',
51 }
52
On Friday, March 21, 2014 9:01:35 PM UTC-3, Jose Luis Ledesma wrote:
The hiera command doesn't use facter, its a tool to check the values
returned by hiera in different circumstances.
El 21/03/2014 21:19, Renan Vicente rena...@gmail.com javascript:
escribió:
Any one had this problem to find a attribute or know how to solve this?
In my case I separated hiera files by osfamily when I execute
# hiera packages_utils
return me
nil
BUT if I execute
# hiera packages_utils osfamily=Debian
it's works
[tzdata,
dnsutils,
bash-completion,
unzip,
bzip2,
htop,
vim,
ntpdate,
mlocate,
nfs-common,
sysstat]
the facter osfamily works.
# facter osfamily
Debian
my hiera.yaml
---
:backends:
- yaml
:hierarchy:
- nodes/%{fqdn}
- osfamily/%{osfamily}
- osfamily/%{operatingsystem}
- defaults/users
- defaults/hosts
- %{clientcert}
- %{environment}
- global
:yaml:
# datadir is empty here, so hiera uses its defaults:
# - /var/lib/hiera on *nix
# - %CommonAppData%\PuppetLabs\hiera\var on Windows
# When specifying a datadir, make sure the directory exists.
:datadir: /etc/puppet/hiera
my osfamily directory content
# ls -l /etc/puppet/hiera/osfamily/
total 12
lrwxrwxrwx 1 root root 11 Mar 21 15:44 CentOS.yaml - RedHat.yaml
-rw-r--r-- 1 root root 248 Mar 21 16:11 Debian.yaml
-rw-r--r-- 1 root root 29 Mar 21 16:13 default.yaml
-rw-r--r-- 1 root root 223 Mar 21 15:44 RedHat.yaml
lrwxrwxrwx 1 root root 11 Mar 21 15:44 Ubuntu.yaml - Debian.yaml
my Debian.yaml
---
packages_utils:
- tzdata
- dnsutils
- bash-completion
- unzip
- bzip2
- htop
- vim
- ntpdate
- mlocate
- nfs-common
- sysstat
conf_ntp:
- ntpdate
conf_ntp_path:
- /etc/default/ntpdate
conf_vim_path:
- /etc/vim/vimrc
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users...@googlegroups.com javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/11625c93-4c89-4fd6-8c82-6b9c170ebddb%40googlegroups.comhttps://groups.google.com/d/msgid/puppet-users/11625c93-4c89-4fd6-8c82-6b9c170ebddb%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/3aa62b7f-ea52-47d9-91de-687414c03047%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] SSL Certificate errors - Migrating from build in webserver to Apache and Passenger
Ahh, those lines are different. The ones I have point to /etc/puppet/ssl Yep, the cert you've just pointed to look like they match what I'm getting from WebBrick. On Sunday, 23 March 2014 01:59:50 UTC+8, Spencer Krum wrote: You should have several lines in your apache vhost pointing to specific ssl certs. Can you verify that all these paths are correct? Specifically the lines beginning with SSL in http://docs.puppetlabs.com/guides/passenger.html#create-and-enable-the-puppet-master-vhost On Sat, Mar 22, 2014 at 7:51 AM, Tom Hallam thalla...@gmail.com wrote: Hi All I've been running Puppet using the build in web server and I'm now moving to Apache and Passenger. I've completed the installation and started testing. If I run puppet agent --test --noop I get the following error (domain removed) Warning: Unable to fetch my node definition, but the agent run will continue: Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001...] Info: Retrieving plugin Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001...] Error: /File[/var/lib/puppet/lib]: Could not evaluate: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001] Could not retrieve file metadata for puppet://puppet/plugins: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001...] Error: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001...] Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Error: Could not send report: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=ecm-rhl-001...] If I turn apache off and the built in webserver back on it all works. The server I'm running puppet on server that has a CNAME puppet that points to its real name ecm-rhl-001 Apache site is configured with ecm-rhl-001... as the servername and puppet... as server alias. The system returns 'ecm-rhl-001' for hostname and 'ecm-rhl-001' for hostname -f. The certificate has ecm-rhl-001... as its CN and puppet... as one of its alt names. Obviously the cert is OK as it works with the built in webserver. It looks like I'm missing something in the apache SSL or Passenger configuration but I have no idea what. I've tried various permutations of servername and serveralias without success. Changing the server name in the agent configuration so it users the real name instead of the CNAME also does not fix the issue. Any suggestions? Tom -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/f21d077a-14f8-4712-a0d6-8e8bfeb0652a%40googlegroups.comhttps://groups.google.com/d/msgid/puppet-users/f21d077a-14f8-4712-a0d6-8e8bfeb0652a%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Spencer Krum (619)-980-7820 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/3c30c2ee-e5de-4dce-b7e4-e434f9ed2880%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] SSL Certificate errors - Migrating from build in webserver to Apache and Passenger
Hi Spencer That's fixed the ssl issue. Not sure where I got the /etc/puppet/ssl... from. I've got some access denied issues now. Trace them down another day Thanks for the help Tom On Sunday, 23 March 2014 02:16:12 UTC+8, Tom Hallam wrote: Ahh, those lines are different. The ones I have point to /etc/puppet/ssl Yep, the cert you've just pointed to look like they match what I'm getting from WebBrick. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e74a9abd-f533-4908-93ef-090c54fccf4c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] hiera could not find item
problem solved I just was using hiera of the wrong way, I was using
hiera($conf_ntp)
instead hiera('conf_ntp'), I need to provide a keyname that hiera should
look up as a string.So , the error indicates that I was trying to look up a
key that is stored in `$conf_ntp` and $conf_ntp is not set to a value so
hiera tries to lookup an empty key.
On Saturday, March 22, 2014 3:09:49 PM UTC-3, Renan Vicente wrote:
How can I check this , 'Cause in my nodes I received this?
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not find data item in any Hiera data file and no default supplied at
/etc/puppet/modules/ananke-base-utils/manifests/init.pp:42 on node
tm-ld168-senacWarning: Not using cache on failed catalogError: Could not
retrieve catalog; skipping run
this is the part of my code that I am having trouble:
38 class ananke-base-utils {
39
40 # variables from hiera
41
42 $conf_file= hiera($conf_ntp)
43 $cpath_ntp= hiera($conf_ntp_path)
44 $cpath_vim= hiera($conf_vim_path)
45 $package_name = hiera_array($packages_utils)
46
47
48 # install package based on distribuition
49 package {$package_name:
50 ensure = 'present',
51 }
52
On Friday, March 21, 2014 9:01:35 PM UTC-3, Jose Luis Ledesma wrote:
The hiera command doesn't use facter, its a tool to check the values
returned by hiera in different circumstances.
El 21/03/2014 21:19, Renan Vicente rena...@gmail.com escribió:
Any one had this problem to find a attribute or know how to solve this?
In my case I separated hiera files by osfamily when I execute
# hiera packages_utils
return me
nil
BUT if I execute
# hiera packages_utils osfamily=Debian
it's works
[tzdata,
dnsutils,
bash-completion,
unzip,
bzip2,
htop,
vim,
ntpdate,
mlocate,
nfs-common,
sysstat]
the facter osfamily works.
# facter osfamily
Debian
my hiera.yaml
---
:backends:
- yaml
:hierarchy:
- nodes/%{fqdn}
- osfamily/%{osfamily}
- osfamily/%{operatingsystem}
- defaults/users
- defaults/hosts
- %{clientcert}
- %{environment}
- global
:yaml:
# datadir is empty here, so hiera uses its defaults:
# - /var/lib/hiera on *nix
# - %CommonAppData%\PuppetLabs\hiera\var on Windows
# When specifying a datadir, make sure the directory exists.
:datadir: /etc/puppet/hiera
my osfamily directory content
# ls -l /etc/puppet/hiera/osfamily/
total 12
lrwxrwxrwx 1 root root 11 Mar 21 15:44 CentOS.yaml - RedHat.yaml
-rw-r--r-- 1 root root 248 Mar 21 16:11 Debian.yaml
-rw-r--r-- 1 root root 29 Mar 21 16:13 default.yaml
-rw-r--r-- 1 root root 223 Mar 21 15:44 RedHat.yaml
lrwxrwxrwx 1 root root 11 Mar 21 15:44 Ubuntu.yaml - Debian.yaml
my Debian.yaml
---
packages_utils:
- tzdata
- dnsutils
- bash-completion
- unzip
- bzip2
- htop
- vim
- ntpdate
- mlocate
- nfs-common
- sysstat
conf_ntp:
- ntpdate
conf_ntp_path:
- /etc/default/ntpdate
conf_vim_path:
- /etc/vim/vimrc
--
You received this message because you are subscribed to the Google
Groups Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send
an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/11625c93-4c89-4fd6-8c82-6b9c170ebddb%40googlegroups.comhttps://groups.google.com/d/msgid/puppet-users/11625c93-4c89-4fd6-8c82-6b9c170ebddb%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/7f42c2a8-81a0-4a9b-8d9b-42ca06305883%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Problems in Ch. 1 and 2 of Pro Puppet 2nd Edition
Hi John,
thanks for your work.
I think i found another typo or maybe there is something i don't understand?
(T) Pg. 51 file { ::$ssh::params::ssh_service_config: -
file { $::ssh::params::ssh_service_config:
Le lundi 24 février 2014 07:01:49 UTC+1, Jon Forrest a écrit :
I spent a lot of time reading the 1st edition of the Pro Puppet
book and I found many problems, most of which should have been
caught by the various editors at Apress. I posted a list of
what I found to this list and to Apress. My feeling was that Apress
was surprisingly nonchalant about the editorial quality of that book.
Since I'm the first to admit that I'm no Puppet expert I'm not
talking much about problems in its technical coverage since I'm not
really qualified to judge.
When the 2nd edition of Pro Puppet came out I had high hopes
that Apress would have learned something from the 1st edition.
I was wrong. Below are the issues I've found with Chapter 1 and 2.
Fortunately, the vast majority of these problems are very minor. But
they still show a surprising lack of attention to detail by Apress.
In one case, an error I found in the 1st edition appears again
in the 2nd edition. This error even appears in their errata for
the 1st edition.
In spite of what appears below, I think Pro Puppet is pretty good,
and is definitely worth reading. But Apress better be careful, because
they're in danger of becoming as bad as Packt in their editorial
quality.
Cordially,
Jon Forrest
M = mistake
U = unclear
T = typo
E = text change
C = comment
(C) Node definitions throughout the Safari online book have the closing
single quote
on a line by itself. They should be on the same line as the opening
single quote.
This is correct in the printed book. In fact, there are a number of
similar formatting
issues that only appear in the Safari online book. I've noted some of
them below.
Starting with Ch.2 I'm now reading a borrowed copy of the Apress book so
I won't
be commenting on these issues further.
(E) Pg. 1 you use to create Puppet configuration -
you use to create Puppet configurations
(M) Pg. 1 “licensed as Apache 2.0” - “licensed under the Apache 2.0
license”
This appears correctly in the section about Facter and Facts.
(U) Pg. 2 The Puppet master runs as a daemon on a host and contains the
configuration required for the specific environment.”
This is poor wording. What does the configuration required for the
specific environment” mean?
(T) Pg. 4 .apt-get install vim” - apt-get install vim”
(T) Pg. 5 on Red Hat it would execute yum
execute should not be in italics.
(E) Pg. 6 Puppet configuration can be safely run -
Puppet can be safely run
(M) Pg. 7 The first caveat is that the master needs to be a later
release than the agents.” -
The first caveat is that the master needs to be the same or a later
release than the agents.”
(T) Pg. 9 On Red Hat, CentOS, Fedora, SUSE/SLES, Debian and Ubuntu,
this package is called rubygems.” -
On Red Hat, CentOS, Fedora, SUSE/SLES, Debian, and Ubuntu, this package
is called rubygems.”
(T) Pg. 10 RubyGems or Source -
RubyGems or source
(M) Pg. 19 and C:\ProgramData\PuppetLabs\puppet\etc\ -
and C:\ProgramData\PuppetLabs\puppet\etc\puppet.conf
(E) Pg. 19 Once we've configured appropriate DNS for Puppet -
Once we've configured appropriate DNS entries for Puppet
(E) Pg. 20 This directory and file is often already created when the
Puppet packages are installed. If it hasn’t already been created, create
this directory and file now” -
This directory and file are often already created when the Puppet
packages are installed. If they haven’t already been created, create
this directory and file now”
(E) Pg. 21 Starting the daemon will initiate -
Starting the daemon will initialize
(T) Pg. ? puppet agent --test --server= puppet.pro-puppet.com” -
puppet agent --test --server=puppet.pro-puppet.com”
(On Safari online only)
(M) Pg. 22 with three options. The first option, --server, -
with three options. The second option, --server,
(T) Pg. 23 in the main section -
in the [main] section
(T) Pg. 23 your client).The -
your client). The
(E) Pg. 23 The agent sends the certificate request -
The agent sends the certificate signing request
Pg. ? This configuration is called waitforcertand is” -
This configuration is called waitforcert and is”
(On Safari online only)
(U) Pg. 26 In Listing 1-7 there are two node definitions for ‘node1’.
The text doesn’t
make it clear why an. A FQDN name is shown in one definition and just
a hostname is shown in the other.
(C) Pg. 26 Parameterized classes is too important a concept to be
brushed over.
Just a short description only confuses readers.
(M) Pg. 28 check the value of the operatingsystem fact -
check the value of the osfamily fact
(U) Pg. 28 relationship between
Re: [Puppet Users] Re: Problems in Ch. 1 and 2 of Pro Puppet 2nd Edition
On 3/22/2014 4:03 PM, Julien Deloubes wrote:
Hi John,
thanks for your work.
I think i found another typo or maybe there is something i don't understand?
(T) Pg. 51 file { ::$ssh::params::ssh_service_config: -
file { $::ssh::params::ssh_service_config:
Very good find. I missed that one. I've added it to my master list,
credited to you, which I'll be putting on Dropbox when it's finished.
Submitting errors to Apress is also a good idea, although it isn't clear
if it will do any good. After all, the Errata page for Pro Puppet
2nd ed. is still empty, even after everything I've posted.
Jon
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/lglbvm%24rvg%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.
