puppet kick not working against windows service

[Matt F]

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).

Thanks!

[Nan Liu]

The listen option isn't supported yet. See issue #15838.

Nan

[Matt F]

Thanks Nan! Do you know if windows support of "-listen" is planned for any future release? (it's not clear to me reading the bug that you referenced).

[Josh Cooper]

Hi Matt,

On Fri, Aug 17, 2012 at 8:41 AM, Matt F <mfan...@gmail.com> wrote:
> Thanks Nan! Do you know if windows support of "-listen" is planned for any
> future release? (it's not clear to me reading the bug that you referenced).

Minor clarification. Puppet supports --listen on Windows, i.e. when
executing `puppet agent --listen`. But not when installed as a service
using the daemon.rb wrapper (which is the out-of-the-box
configuration). The reasons for this are memory usage issues
associated with long running ruby processes[1], security implications
of a network server running as LocalSystem, etc.

So it is possible to change the "Puppet Agent" service to run
something different, but it's not something that I would encourage due
to the problems mentioned above.

The long term plan is to deprecate puppet kick[2] in favor of using
mcollective (mcollective 2.0 supports Windows)[3]. There is also an
executable installer[4] from the community.

HTH,
Josh

[1] http://projects.puppetlabs.com/issues/11044
[2] http://projects.puppetlabs.com/issues/15735
[3] http://projects.puppetlabs.com/issues/12555
[4] http://www.kermit.fr/documentation/mcollective/windows_install.html

--
Josh Cooper
Developer, Puppet Labs

[Matt F]

I've installed mcollective, and I can get data from the client (IE: "mco inventory mywindowsclient"). I've configured the puppetd agent plugin, and that shows up in the "mco inventory" output as well. However, I still cannot trigger puppet to update on the client. Any idea of what the cause might be, or what next steps I can take to debug this? thx.

[Matt F]

Here's the mcollective.log from the client:

D, [2012-08-22T13:54:28.907044 #3224] DEBUG -- : runnerstats.rb Incrementing total stat

D, [2012-08-22T13:54:28.907044 #3224] DEBUG -- : pluginmanager.rb Returning cached plugin security_plugin with class MCollective::Security::Psk

D, [2012-08-22T13:54:28.907044 #3224] DEBUG -- : runnerstats.rb Incrementing validated stat

D, [2012-08-22T13:54:28.907044 #3224] DEBUG -- : pluginmanager.rb Returning cached plugin security_plugin with class MCollective::Security::Psk

D, [2012-08-22T13:54:28.907044 #3224] DEBUG -- : pluginmanager.rb Returning cached plugin security_plugin with class MCollective::Security::Psk

D, [2012-08-22T13:54:28.907044 #3224] DEBUG -- : base.rb Passing based on agent puppetd

D, [2012-08-22T13:54:28.907044 #3224] DEBUG -- : base.rb Passing based on identity

D, [2012-08-22T13:54:28.907044 #3224] DEBUG -- : base.rb Message passed the filter checks

D, [2012-08-22T13:54:28.907044 #3224] DEBUG -- : runnerstats.rb Incrementing passed stat

D, [2012-08-22T13:54:28.907044 #3224] DEBUG -- : runner.rb Handling message for agent 'puppetd' on collective 'mcollective'

D, [2012-08-22T13:54:28.907044 #3224] DEBUG -- : agents.rb Dispatching a message to agent puppetd

D, [2012-08-22T13:54:28.907044 #3224] DEBUG -- : stomp.rb Waiting for a message from Stomp

D, [2012-08-22T13:54:28.907044 #3224] DEBUG -- : pluginmanager.rb Returning new plugin puppetd_agent with class MCollective::Agent::Puppetd

D, [2012-08-22T13:54:28.907044 #3224] DEBUG -- : ddl.rb Found puppetd ddl at C:\mcollective\plugins/mcollective/agent/puppetd.ddl

D, [2012-08-22T13:54:28.953920 #3224] DEBUG -- : pluginmanager.rb Returning cached plugin security_plugin with class MCollective::Security::Psk

D, [2012-08-22T13:54:28.953920 #3224] DEBUG -- : pluginmanager.rb Returning cached plugin security_plugin with class MCollective::Security::Psk

D, [2012-08-22T13:54:28.953920 #3224] DEBUG -- : base.rb Encoded a message for request 7edf85764752fbda37ea8b8efbfedf70

D, [2012-08-22T13:54:28.953920 #3224] DEBUG -- : pluginmanager.rb Returning cached plugin connector_plugin with class MCollective::Connector::Stomp

D, [2012-08-22T13:54:28.953920 #3224] DEBUG -- : stomp.rb Sending a broadcast message to STOMP target '/topic/mcollective.puppetd.reply'

D, [2012-08-22T13:54:28.953920 #3224] DEBUG -- : runnerstats.rb Incrementing replies stat

[Josh Cooper]

Hi Matt,

I'm not sure what the issue is. I recommend posting to the
mcollective-users list.

> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/OPzKMQxoWr4J.
>
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.

Josh