Issue #21043 has been updated by Rob Reynolds.
In puppet.conf:
[main]
runinterval=1
c:\> puppet --version
3.3.1 (Puppet Enterprise 3.1.0)
Adding some logging to daemon.rb at
<https://github.com/puppetlabs/puppet/blob/master/ext/windows/service/daemon.rb#L48>
and then taking a look at the output afterwards. This is the logging items
added:
runintervalcommand = "\"#{puppet}\" agent --configprint runinterval"
log_notice("Running #{runintervalcommand}")
runintervaloutput = %x{ "#{puppet}" agent --configprint runinterval }
runinterval = %x{ "#{puppet}" agent --configprint runinterval }.to_i
log_notice("run interval = #{runinterval} | ouptput from command =
#{runintervaloutput}")
And here is the log output in
C:\ProgramData\PuppetLabs\puppet\var\log\windows.log:
2013-12-02 14:58:23 -0800 Puppet (notice): Running "C:/Program Files
(x86)/Puppet Labs/Puppet Enterprise/bin/puppet.bat" agent --configprint
runinterval
2013-12-02 14:58:26 -0800 Puppet (notice): run interval = 0 | ouptput from
command =
2013-12-02 14:58:26 -0800 Puppet (err): Failed to determine runinterval,
defaulting to 1800 seconds
2013-12-02 14:58:26 -0800 Puppet (notice): Service waiting for 1800 seconds
This appears to be broken (at least in PE).
----------------------------------------
Bug #21043: runinterval setting in puppet.conf ignored on Windows in Puppet
3.2.1
https://projects.puppetlabs.com/issues/21043#change-100307
* Author: Shane Madden
* Status: Closed
* Priority: Normal
* Assignee:
* Category: agent
* Target version: 3.2.3
* Affected Puppet version: 3.2.1
* Keywords: windows
* Branch: https://github.com/puppetlabs/puppet/pull/1725
----------------------------------------
Windows agents seem to no longer pay attention to `runinterval` as of 3.2.1.
Currently my Windows agents have `runinterval` set in both the `[agent]` and
`[main]` sections as a leftover workaround from #17554 - neither section works.
Commenting out `runinterval` from one section or the other has no effect.
It's returning the configuration correctly using (as far as I can tell) the
same command as `daemon.rb` is using to try to retrieve it:
C:\>"c:/Program Files (x86)/Puppet Labs/Puppet/bin/puppet.bat" agent
--configprint runinterval
600
But `daemon.rb` is somehow getting a `0` as the result to that command:
2013-06-03 16:32:26 -0600 Puppet (notice): Starting service: --debug
2013-06-03 16:32:26 -0600 Puppet (notice): Service running
2013-06-03 16:32:26 -0600 Puppet (debug): Using 'c:/Program Files
(x86)/Puppet Labs/Puppet/bin/puppet.bat'
2013-06-03 16:32:28 -0600 Puppet (err): Failed to determine runinterval,
defaulting to 1800 seconds
2013-06-03 16:32:28 -0600 Puppet (debug): Process created: 3100
2013-06-03 16:32:28 -0600 Puppet (debug): Service waiting for 1800 seconds
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
