Jira (PUP-1280) Windows agent daemon script always captures runinterval as empty string

[Josh Cooper (JIRA)]

Title: Message Title

Josh Cooper commented on an issue   Re: Windows agent daemon script always captures runinterval as empty string Nicholas Fagerlund this is working correctly for me, using a very recent MSI built from master branch: From "Start Command Prompt with Puppet" running as administrator: C:\>puppet agent --configprint runinterval 100 C:\>sc start puppet --debug --logtofile This will append to the service log file: C:\>tail -f C:\ProgramData\PuppetLabs\puppet\var\log\windows.log ... 2014-09-02 21:17:13 -0700 Puppet (debug): Using 'C:/Program Files/Puppet Labs/Puppet/bin/puppet.bat' 2014-09-02 21:17:14 -0700 Puppet (notice): Service started 2014-09-02 21:17:19 -0700 Puppet (notice): Executing agent with arguments: --debug 2014-09-02 21:17:21 -0700 Puppet (debug): Process created: 1384 2014-09-02 21:17:23 -0700 Puppet (debug): Service worker thread waiting for 100 seconds Note it's using the runinterval setting of 100 seconds as expected. Changed runinterval to 2m in [main] setting. C:\>puppet agent --configprint runinterval 120 C:\>net stop puppet The Puppet Agent service is stopping. The Puppet Agent service was stopped successfully. C:\>sc start puppet --debug --logtofile ... C:\>tail -f C:\ProgramData\PuppetLabs\puppet\var\log\windows.log 2014-09-02 21:20:50 -0700 Puppet (notice): Service stopping / killing worker thread 2014-09-02 21:20:50 -0700 Puppet (notice): Service stopped 2014-09-02 21:21:05 -0700 Puppet (debug): Using 'C:/Program Files/Puppet Labs/Puppet/bin/puppet.bat' 2014-09-02 21:21:06 -0700 Puppet (notice): Service started 2014-09-02 21:21:10 -0700 Puppet (notice): Executing agent with arguments: --debug 2014-09-02 21:21:11 -0700 Puppet (debug): Process created: 2244 2014-09-02 21:21:16 -0700 Puppet (debug): Service worker thread waiting for 120 seconds As expected, the puppet service correctly interprets the 2m duration as 120 seconds and uses that setting. There definitely was an issue with earlier versions of puppet (when using rubyw.exe), but it is behaving correctly now. Add Comment   Puppet / PUP-1280 Windows agent daemon script always captures runinterval as empty string When running as a service, puppet on windows runs `puppet agent --configprint runinterval` and assumes the result is in seconds. It then runs `puppet agent --onetime` every runinterval seconds. In 3.0.0, runinterval was changed to a `duration` setting, so it can be of the form 5m, 2h, etc <http://docs.puppetlabs.com/references/latest/configuration.html... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.