Hey Everyone, I have a question about the listen option for the puppetd command. When I run this manually on a client called puppetclient like so /usr/sbin/puppetd --listen --server puppetmaster.com I can use the "puppetrun --host puppetclient" command from the server and push config changes to that client as expected. This tells me there are no namespaceauth.conf or connectivity issues. I can also run "puppetd --test --server puppetmaster" on the client itself and the config run happens. But what I want to do is start the clients with their init.d scripts "/ etc/init.d/puppet start" and still have them listen for puppetrun commands. I tried to add listen=true in the puppet.conf file but that entry doesn''t seem to be picked up there. What am I missing? Where should I make the config change for the clients? The only other thing I can think is to edit that init.d script and put it in there. Thanks, Chris -- 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 Thu, Jan 21, 2010 at 3:03 PM, Breeze <breeze773@gmail.com> wrote:> Hey Everyone, > I have a question about the listen option for the puppetd command. > When I run this manually on a client called puppetclient like so > /usr/sbin/puppetd --listen --server puppetmaster.com > > I can use the "puppetrun --host puppetclient" command from the server > and push config changes to that client as expected. This tells me > there are no namespaceauth.conf or connectivity issues. > > I can also run "puppetd --test --server puppetmaster" on the client > itself and the config run happens. > > But what I want to do is start the clients with their init.d scripts "/ > etc/init.d/puppet start" and still have them listen for puppetrun > commands. I tried to add listen=true in the puppet.conf file but that > entry doesn''t seem to be picked up there. What am I missing? Where > should I make the config change for the clients? The only other thing > I can think is to edit that init.d script and put it in there. >In which section of your puppet.conf file are you setting listen=true. After you set it, what is the output of: puppetd --configprint listen -teyo -- Teyo Tyree :: www.reductivelabs.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.
I have the listen=true under the [puppetd] section. /usr/sbin/puppetd --configprint listen false Hope that info helps. Also, BTW, I am using version 0.24.8 Thanks, Chris On Jan 21, 6:32 pm, Teyo Tyree <t...@reductivelabs.com> wrote:> On Thu, Jan 21, 2010 at 3:03 PM, Breeze <breeze...@gmail.com> wrote: > > Hey Everyone, > > I have a question about the listen option for the puppetd command. > > When I run this manually on a client called puppetclient like so > > /usr/sbin/puppetd --listen --server puppetmaster.com > > > I can use the "puppetrun --host puppetclient" command from the server > > and push config changes to that client as expected. This tells me > > there are no namespaceauth.conf or connectivity issues. > > > I can also run "puppetd --test --server puppetmaster" on the client > > itself and the config run happens. > > > But what I want to do is start the clients with their init.d scripts "/ > > etc/init.d/puppet start" and still have them listen for puppetrun > > commands. I tried to add listen=true in the puppet.conf file but that > > entry doesn''t seem to be picked up there. What am I missing? Where > > should I make the config change for the clients? The only other thing > > I can think is to edit that init.d script and put it in there. > > In which section of your puppet.conf file are you setting listen=true. > After you set it, what is the output of: > > puppetd --configprint listen > > -teyo > > -- > Teyo Tyree ::www.reductivelabs.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.
Teyo, Thanks for suggesting the --configprint option. I think it has helped me uncover some deeper problem. For background, we cannot run puppetd as root in the environment I am trying to set it up. It seemed like puppet was working ok in this fashion until I ran puppetd --configprint confdir as the user we want to run puppetd as. This resulted in the output of usersHomeDir/.puppet not /etc/puppet/ where I was making the config file changes. The sysadmins did give me write access to that file in etc, btw. So, I copied my puppet.conf file to homeDir/.puppet and ran your first suggested test "puppetd --configprint listen" which resulted in true. The lesson I learned then, is that when not running puppetd as root / etc/puppet dir is not the correct place to make config file changes. Although, I''d still like it to be, if you have suggestions on that. Chris On Jan 21, 6:32 pm, Teyo Tyree <t...@reductivelabs.com> wrote:> On Thu, Jan 21, 2010 at 3:03 PM, Breeze <breeze...@gmail.com> wrote: > > Hey Everyone, > > I have a question about the listen option for the puppetd command. > > When I run this manually on a client called puppetclient like so > > /usr/sbin/puppetd --listen --server puppetmaster.com > > > I can use the "puppetrun --host puppetclient" command from the server > > and push config changes to that client as expected. This tells me > > there are no namespaceauth.conf or connectivity issues. > > > I can also run "puppetd --test --server puppetmaster" on the client > > itself and the config run happens. > > > But what I want to do is start the clients with their init.d scripts "/ > > etc/init.d/puppet start" and still have them listen for puppetrun > > commands. I tried to add listen=true in the puppet.conf file but that > > entry doesn''t seem to be picked up there. What am I missing? Where > > should I make the config change for the clients? The only other thing > > I can think is to edit that init.d script and put it in there. > > In which section of your puppet.conf file are you setting listen=true. > After you set it, what is the output of: > > puppetd --configprint listen > > -teyo > > -- > Teyo Tyree ::www.reductivelabs.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 1/22/10 9:13 AM, Breeze wrote:> The lesson I learned then, is that when not running puppetd as root / > etc/puppet dir is not the correct place to make config file changes. > Although, I''d still like it to be, if you have suggestions on that.Check out --confdir -scott -- 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.