On Fri, Aug 17, 2012 at 6:55 AM, Matt F <mfan2...@gmail.com> wrote: > I am running puppet 2.7.14 - CentOS 6 server, CentOS and windows 2008 R2 > clients. > > I'm having problems with the "puppet kick" command - it works on linux > clients, and on my windows box when "puppet agent --no-daemonize --verbose" > is run from a command prompt. However, when I run it as a windows service, I > get "Host blah failed: Connection refused - connect(2)" and "blah finished > with exit code 2". Any idea why the behaviour might be different when > running as a service vs running from the "Start Command Prompt with Puppet" > window? > > I did a test with "process monitor" from the windows resource toolkit and > it looks like the service is actually running 'ruby -S -- "puppet" agent > --onetime'..? > > Is there a way to force the windows service to use listen mode? I've > modified C:\ProgramData\PuppetLabs\puppet\etc\puppet.conf to have "[agent] > listen=true" but that seems not to be working (at least not when run as a > service).
The listen option isn't supported yet. See issue #15838. Nan -- 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.
