On Wed, Oct 14, 2009 at 9:51 AM, Douglas Garstang <doug.garst...@gmail.com> wrote: > > On Wed, Oct 14, 2009 at 9:35 AM, Nigel Kersten <nig...@google.com> wrote: >> >> On Wed, Oct 14, 2009 at 9:31 AM, Douglas Garstang >> <doug.garst...@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 <nig...@google.com> wrote: >>>> >>>> On Tue, Oct 13, 2009 at 4:07 PM, Douglas Garstang >>>> <doug.garst...@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.garst...@gmail.com >>> Cell: +1-805-340-5627 >>> >>> > >>> >> >> >> >> -- >> nigel >> >> > >> > > > > -- > Regards, > > Douglas Garstang > http://www.linkedin.com/in/garstang > Email: doug.garst...@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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
