I''m getting really really frustrated with puppet. Why is it that when I install the puppet-server RPM, my default config file in /etc/puppet/puppet.conf has a [puppetd] section and not a [puppetmasterd] section? Isn''t that what the puppetmaster looks for? The output from --genconfig generates a config file with a [puppetmasterd] section. I''ve been trying to get the client and server to talk to each other for over 24 hours now and inconsistency''s like this are making it REALLY hard to get a good starting baseline. Doug. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Hi, [puppetd] is for the puppet process that runs on every puppet node. [puppetmasterd] is for the puppet master process. What is the issue with getting the client and server talking? What happens? J. 2009/10/14 Douglas Garstang <doug.garstang@gmail.com>:> > I''m getting really really frustrated with puppet. > > Why is it that when I install the puppet-server RPM, my default config > file in /etc/puppet/puppet.conf has a [puppetd] section and not a > [puppetmasterd] section? Isn''t that what the puppetmaster looks for? > The output from --genconfig generates a config file with a > [puppetmasterd] section. I''ve been trying to get the client and server > to talk to each other for over 24 hours now and inconsistency''s like > this are making it REALLY hard to get a good starting baseline. > > Doug. > > > >-- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Tue, Oct 13, 2009 at 4:07 PM, Douglas Garstang <doug.garstang@gmail.com> wrote:> > I''m getting really really frustrated with puppet. > > Why is it that when I install the puppet-server RPM, my default config > file in /etc/puppet/puppet.conf has a [puppetd] section and not a > [puppetmasterd] section? Isn''t that what the puppetmaster looks for? > The output from --genconfig generates a config file with a > [puppetmasterd] section. I''ve been trying to get the client and server > to talk to each other for over 24 hours now and inconsistency''s like > this are making it REALLY hard to get a good starting baseline.I''ve found this somewhat frustrating too Douglas. If you invoke puppetd --genconfig, the whole config is in a [puppetd] stanza. If you invoke puppet --genconfig, the whole config is in a [puppet] stanza If you invoke puppetmasterd --genconfig .... you get the picture. This is my understanding of how things work, and it''s likely I''m wrong. [main] # these things get set for puppet/puppetd/puppetmasterd # unless overriden by a following stanza [puppet] # these things just get set for puppet # the standalone executable [puppetd] # these things just get set for puppetd # the client in the client-server modle [puppetmasterd] # these things just get set for puppetmasterd # the server in the client-server model I tend to work backwards somewhat with puppetmasterd configuration files. I work it all out on the command line with a simple webrick --no-daemonize --verbose invocation, adding flags as I work out what I need, then reconstruct the puppet.conf [puppetmasterd] section based upon the necessary settings. Once I have that working, I then get the same config working in Passenger, which these days doesn''t usually require any extra settings in puppet.conf. If you give us a bit more detail about what''s going on, we can probably help sort it out.> > Doug. > > > >-- nigel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Can anyone in the know please help to clear this up? Does puppetmaster look for [puppetd] or [puppetmasterd] in /etc/puppet/puppet.conf ??? Doug. On Wed, Oct 14, 2009 at 5:37 AM, Nigel Kersten <nigelk@google.com> wrote:> > On Tue, Oct 13, 2009 at 4:07 PM, Douglas Garstang > <doug.garstang@gmail.com> wrote: >> >> I''m getting really really frustrated with puppet. >> >> Why is it that when I install the puppet-server RPM, my default config >> file in /etc/puppet/puppet.conf has a [puppetd] section and not a >> [puppetmasterd] section? Isn''t that what the puppetmaster looks for? >> The output from --genconfig generates a config file with a >> [puppetmasterd] section. I''ve been trying to get the client and server >> to talk to each other for over 24 hours now and inconsistency''s like >> this are making it REALLY hard to get a good starting baseline. > > I''ve found this somewhat frustrating too Douglas. > > If you invoke puppetd --genconfig, the whole config is in a [puppetd] stanza. > If you invoke puppet --genconfig, the whole config is in a [puppet] stanza > If you invoke puppetmasterd --genconfig .... you get the picture. > > This is my understanding of how things work, and it''s likely I''m wrong. > > [main] > # these things get set for puppet/puppetd/puppetmasterd > # unless overriden by a following stanza > > [puppet] > # these things just get set for puppet > # the standalone executable > > [puppetd] > # these things just get set for puppetd > # the client in the client-server modle > > [puppetmasterd] > # these things just get set for puppetmasterd > # the server in the client-server model > > I tend to work backwards somewhat with puppetmasterd configuration > files. I work it all out on the command line with a simple webrick > --no-daemonize --verbose invocation, adding flags as I work out what I > need, then reconstruct the puppet.conf [puppetmasterd] section based > upon the necessary settings. > > Once I have that working, I then get the same config working in > Passenger, which these days doesn''t usually require any extra settings > in puppet.conf. > > > If you give us a bit more detail about what''s going on, we can > probably help sort it out. > >> >> Doug. >> >> > >> > > > > -- > nigel > > > >-- Regards, Douglas Garstang http://www.linkedin.com/in/garstang Email: doug.garstang@gmail.com Cell: +1-805-340-5627 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Wed, Oct 14, 2009 at 9:31 AM, Douglas Garstang <doug.garstang@gmail.com> wrote:> > Can anyone in the know please help to clear this up? > > Does puppetmaster look for [puppetd] or [puppetmasterd] in > /etc/puppet/puppet.conf ???[puppetmasterd] I believe. That''s what I always use on my servers.> > Doug. > > On Wed, Oct 14, 2009 at 5:37 AM, Nigel Kersten <nigelk@google.com> wrote: >> >> On Tue, Oct 13, 2009 at 4:07 PM, Douglas Garstang >> <doug.garstang@gmail.com> wrote: >>> >>> I''m getting really really frustrated with puppet. >>> >>> Why is it that when I install the puppet-server RPM, my default config >>> file in /etc/puppet/puppet.conf has a [puppetd] section and not a >>> [puppetmasterd] section? Isn''t that what the puppetmaster looks for? >>> The output from --genconfig generates a config file with a >>> [puppetmasterd] section. I''ve been trying to get the client and server >>> to talk to each other for over 24 hours now and inconsistency''s like >>> this are making it REALLY hard to get a good starting baseline. >> >> I''ve found this somewhat frustrating too Douglas. >> >> If you invoke puppetd --genconfig, the whole config is in a [puppetd] stanza. >> If you invoke puppet --genconfig, the whole config is in a [puppet] stanza >> If you invoke puppetmasterd --genconfig .... you get the picture. >> >> This is my understanding of how things work, and it''s likely I''m wrong. >> >> [main] >> # these things get set for puppet/puppetd/puppetmasterd >> # unless overriden by a following stanza >> >> [puppet] >> # these things just get set for puppet >> # the standalone executable >> >> [puppetd] >> # these things just get set for puppetd >> # the client in the client-server modle >> >> [puppetmasterd] >> # these things just get set for puppetmasterd >> # the server in the client-server model >> >> I tend to work backwards somewhat with puppetmasterd configuration >> files. I work it all out on the command line with a simple webrick >> --no-daemonize --verbose invocation, adding flags as I work out what I >> need, then reconstruct the puppet.conf [puppetmasterd] section based >> upon the necessary settings. >> >> Once I have that working, I then get the same config working in >> Passenger, which these days doesn''t usually require any extra settings >> in puppet.conf. >> >> >> If you give us a bit more detail about what''s going on, we can >> probably help sort it out. >> >>> >>> Doug. >>> >>> > >>> >> >> >> >> -- >> nigel >> >> > >> > > > > -- > Regards, > > Douglas Garstang > http://www.linkedin.com/in/garstang > Email: doug.garstang@gmail.com > Cell: +1-805-340-5627 > > > >-- nigel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Wed, Oct 14, 2009 at 9:35 AM, Nigel Kersten <nigelk@google.com> wrote:> > On Wed, Oct 14, 2009 at 9:31 AM, Douglas Garstang > <doug.garstang@gmail.com> wrote: >> >> Can anyone in the know please help to clear this up? >> >> Does puppetmaster look for [puppetd] or [puppetmasterd] in >> /etc/puppet/puppet.conf ??? > > [puppetmasterd] I believe. That''s what I always use on my servers.Thanks Nigel. I''ll give that a shot. Wonder what [main] is used for. I guess both puppetd and puppetmasterd both read from [main].> > > >> >> Doug. >> >> On Wed, Oct 14, 2009 at 5:37 AM, Nigel Kersten <nigelk@google.com> wrote: >>> >>> On Tue, Oct 13, 2009 at 4:07 PM, Douglas Garstang >>> <doug.garstang@gmail.com> wrote: >>>> >>>> I''m getting really really frustrated with puppet. >>>> >>>> Why is it that when I install the puppet-server RPM, my default config >>>> file in /etc/puppet/puppet.conf has a [puppetd] section and not a >>>> [puppetmasterd] section? Isn''t that what the puppetmaster looks for? >>>> The output from --genconfig generates a config file with a >>>> [puppetmasterd] section. I''ve been trying to get the client and server >>>> to talk to each other for over 24 hours now and inconsistency''s like >>>> this are making it REALLY hard to get a good starting baseline. >>> >>> I''ve found this somewhat frustrating too Douglas. >>> >>> If you invoke puppetd --genconfig, the whole config is in a [puppetd] stanza. >>> If you invoke puppet --genconfig, the whole config is in a [puppet] stanza >>> If you invoke puppetmasterd --genconfig .... you get the picture. >>> >>> This is my understanding of how things work, and it''s likely I''m wrong. >>> >>> [main] >>> # these things get set for puppet/puppetd/puppetmasterd >>> # unless overriden by a following stanza >>> >>> [puppet] >>> # these things just get set for puppet >>> # the standalone executable >>> >>> [puppetd] >>> # these things just get set for puppetd >>> # the client in the client-server modle >>> >>> [puppetmasterd] >>> # these things just get set for puppetmasterd >>> # the server in the client-server model >>> >>> I tend to work backwards somewhat with puppetmasterd configuration >>> files. I work it all out on the command line with a simple webrick >>> --no-daemonize --verbose invocation, adding flags as I work out what I >>> need, then reconstruct the puppet.conf [puppetmasterd] section based >>> upon the necessary settings. >>> >>> Once I have that working, I then get the same config working in >>> Passenger, which these days doesn''t usually require any extra settings >>> in puppet.conf. >>> >>> >>> If you give us a bit more detail about what''s going on, we can >>> probably help sort it out. >>> >>>> >>>> Doug. >>>> >>>> > >>>> >>> >>> >>> >>> -- >>> nigel >>> >>> > >>> >> >> >> >> -- >> Regards, >> >> Douglas Garstang >> http://www.linkedin.com/in/garstang >> Email: doug.garstang@gmail.com >> Cell: +1-805-340-5627 >> >> > >> > > > > -- > nigel > > > >-- Regards, Douglas Garstang http://www.linkedin.com/in/garstang Email: doug.garstang@gmail.com Cell: +1-805-340-5627 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Wed, Oct 14, 2009 at 9:51 AM, Douglas Garstang <doug.garstang@gmail.com> wrote:> > On Wed, Oct 14, 2009 at 9:35 AM, Nigel Kersten <nigelk@google.com> wrote: >> >> On Wed, Oct 14, 2009 at 9:31 AM, Douglas Garstang >> <doug.garstang@gmail.com> wrote: >>> >>> Can anyone in the know please help to clear this up? >>> >>> Does puppetmaster look for [puppetd] or [puppetmasterd] in >>> /etc/puppet/puppet.conf ??? >> >> [puppetmasterd] I believe. That''s what I always use on my servers. > > Thanks Nigel. I''ll give that a shot. Wonder what [main] is used for. I > guess both puppetd and puppetmasterd both read from [main].Wasn''t I clear before in my explanation? I use [main] for values that I want to set for puppetd and puppet and puppetmasterd.> >> >> >> >>> >>> Doug. >>> >>> On Wed, Oct 14, 2009 at 5:37 AM, Nigel Kersten <nigelk@google.com> wrote: >>>> >>>> On Tue, Oct 13, 2009 at 4:07 PM, Douglas Garstang >>>> <doug.garstang@gmail.com> wrote: >>>>> >>>>> I''m getting really really frustrated with puppet. >>>>> >>>>> Why is it that when I install the puppet-server RPM, my default config >>>>> file in /etc/puppet/puppet.conf has a [puppetd] section and not a >>>>> [puppetmasterd] section? Isn''t that what the puppetmaster looks for? >>>>> The output from --genconfig generates a config file with a >>>>> [puppetmasterd] section. I''ve been trying to get the client and server >>>>> to talk to each other for over 24 hours now and inconsistency''s like >>>>> this are making it REALLY hard to get a good starting baseline. >>>> >>>> I''ve found this somewhat frustrating too Douglas. >>>> >>>> If you invoke puppetd --genconfig, the whole config is in a [puppetd] stanza. >>>> If you invoke puppet --genconfig, the whole config is in a [puppet] stanza >>>> If you invoke puppetmasterd --genconfig .... you get the picture. >>>> >>>> This is my understanding of how things work, and it''s likely I''m wrong. >>>> >>>> [main] >>>> # these things get set for puppet/puppetd/puppetmasterd >>>> # unless overriden by a following stanza >>>> >>>> [puppet] >>>> # these things just get set for puppet >>>> # the standalone executable >>>> >>>> [puppetd] >>>> # these things just get set for puppetd >>>> # the client in the client-server modle >>>> >>>> [puppetmasterd] >>>> # these things just get set for puppetmasterd >>>> # the server in the client-server model >>>> >>>> I tend to work backwards somewhat with puppetmasterd configuration >>>> files. I work it all out on the command line with a simple webrick >>>> --no-daemonize --verbose invocation, adding flags as I work out what I >>>> need, then reconstruct the puppet.conf [puppetmasterd] section based >>>> upon the necessary settings. >>>> >>>> Once I have that working, I then get the same config working in >>>> Passenger, which these days doesn''t usually require any extra settings >>>> in puppet.conf. >>>> >>>> >>>> If you give us a bit more detail about what''s going on, we can >>>> probably help sort it out. >>>> >>>>> >>>>> Doug. >>>>> >>>>> > >>>>> >>>> >>>> >>>> >>>> -- >>>> nigel >>>> >>>> > >>>> >>> >>> >>> >>> -- >>> Regards, >>> >>> Douglas Garstang >>> http://www.linkedin.com/in/garstang >>> Email: doug.garstang@gmail.com >>> Cell: +1-805-340-5627 >>> >>> > >>> >> >> >> >> -- >> nigel >> >> > >> > > > > -- > Regards, > > Douglas Garstang > http://www.linkedin.com/in/garstang > Email: doug.garstang@gmail.com > Cell: +1-805-340-5627 > > > >-- nigel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Douglas Garstang wrote:> On Wed, Oct 14, 2009 at 9:35 AM, Nigel Kersten <nigelk@google.com> wrote: >> On Wed, Oct 14, 2009 at 9:31 AM, Douglas Garstang >> <doug.garstang@gmail.com> wrote: >>> Can anyone in the know please help to clear this up? >>> >>> Does puppetmaster look for [puppetd] or [puppetmasterd] in >>> /etc/puppet/puppet.conf ??? >> [puppetmasterd] I believe. That''s what I always use on my servers.The options in the blocks like [puppetd] or [puppetmasterd] are for that particular binary. The options in [main] are global and used for every binary. Regards James Turnbull - -- Author of: * Pro Linux Systems Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBStY4iCFa/lDkFHAyAQIsAwf/en71WrJ748FdOakdyjXdWQBsr7DhT+Un RcQ7XsNMmgA8vvhuLN5L0iD58fsEpgzdW17dVkarGMF0JLj6RcbfGv12W3EqPKGn 6ZbnzphuxHinYW97R0E6lXvR91hgXu1df+PqecDEqfwgFHVLXeR71h4G/hY/6m3v DuaqXdqUSk5z88DcrdtX1GWdfYyMFy5oTUl4SRNqxulZ6AHibyTkwT0oUrCEtDHb HnM3XXavrrzheFdzSkhaUeszLVYQBwVOnj+FN4gn+2k1SB5SAZyCsqHnUJE6HLQC 6ColuNtXvANdHjAIccjmo3yjRUJT4PCx4rXAmSD3//DWSMbkBJwbRQ==7R/R -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Douglas,> I''m getting really really frustrated with puppet.I also had a tough time configuring the client and the server part on the same host. I finally settled down to completely seperate the 2, by starting puppetmaster with "--confdir=/etc/puppetmaster". I then have a super simple puppetmaster setup: $ find /etc/puppetmaster/ /etc/puppetmaster/ /etc/puppetmaster/fileserver.conf /etc/puppetmaster/manifests /etc/puppetmaster/facts /etc/puppetmaster/puppet.conf And /etc/puppetmaster/puppet.conf basically breaks down to: [main] vardir = /var/lib/puppetmaster logdir = /var/log/puppetmaster rundir = /var/run/puppetmaster ssldir = $vardir/ssl # puppetmaster needs to read plugins run by clients libdir = /var/lib/puppet/lib environments = prod,test,dev [puppetmasterd] storeconfigs = true dbadapter = mysql ... ... environment configuration follows ... This way I have all the puppet-server stuff in /{etc,var/lib,var/log,var/run}/puppetmaster/ and all the puppet-client stuff in /{etc,var/lib,var/log,var/run}/puppet/ Hope this helps ! Marc --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---