Hi When using puppetrun to trigger machines to get and apply their configuration, it will only trigger the machine when executing puppetrun for the second time: puppetmaster # puppetrun --host puppetclient puppetclient log: -- snip Apr 13 08:19:49 puppetd[20208]: puppetmaster(172.16.34.12) triggered run Apr 13 08:20:08 puppetd[20208]: puppetmaster(172.16.34.12) triggered run Apr 13 08:20:08 puppetd[20208]: Starting configuration run ... -- snip Are there any tests done on the state of the puppetclient when receiving the trigger? - Koen Vereeken _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
On Apr 13, 2007, at 2:25 AM, Koen Vereeken wrote:> Hi > > When using puppetrun to trigger machines to get and apply their > configuration, it will only trigger the machine when executing > puppetrun for the second time: > > puppetmaster # puppetrun --host puppetclient > > puppetclient log: > -- snip > Apr 13 08:19:49 puppetd[20208]: puppetmaster(172.16.34.12) > triggered run > Apr 13 08:20:08 puppetd[20208]: puppetmaster( 172.16.34.12) > triggered run > Apr 13 08:20:08 puppetd[20208]: Starting configuration run > ... > -- snip > > Are there any tests done on the state of the puppetclient when > receiving the trigger?The only test is whether the client is currently in the middle of a run, but it looks like it''s not in this case, else you''d get a log message saying a run finished. This is happening for you consistently? -- Brand''s Asymmetry: The past can only be known, not changed. The future can only be changed, not known. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
2007/4/16, Luke Kanies <luke@madstop.com>:> > On Apr 13, 2007, at 2:25 AM, Koen Vereeken wrote: > > > Hi > > > > When using puppetrun to trigger machines to get and apply their > > configuration, it will only trigger the machine when executing > > puppetrun for the second time: > > > > puppetmaster # puppetrun --host puppetclient > > > > puppetclient log: > > -- snip > > Apr 13 08:19:49 puppetd[20208]: puppetmaster(172.16.34.12) > > triggered run > > Apr 13 08:20:08 puppetd[20208]: puppetmaster( 172.16.34.12) > > triggered run > > Apr 13 08:20:08 puppetd[20208]: Starting configuration run > > ... > > -- snip > > > > Are there any tests done on the state of the puppetclient when > > receiving the trigger? > > The only test is whether the client is currently in the middle of a > run, but it looks like it''s not in this case, else you''d get a log > message saying a run finished. > > This is happening for you consistently?No, mostly once I''m able to trigger the client, it works fine.. --> Brand''s Asymmetry: > The past can only be known, not changed. The future can only be > changed, not known. > --------------------------------------------------------------------- > Luke Kanies | http://reductivelabs.com | http://madstop.com > > >_______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users