Re: [Puppet Users] Fact auto sync reloading
On Mon, Dec 6, 2010 at 7:46 AM, Derek Yarnell de...@umiacs.umd.edu wrote: On 12/3/10 5:13 PM, Nigel Kersten wrote: On Fri, Dec 3, 2010 at 11:58 AM, Derek Yarnell de...@umiacs.umd.edu wrote: So we run puppetd as a long running ruby process on the hosts. When we update a fact that gets auto sync'd to the host it seems when puppetd wakes up and starts its catalog run it doesn't re-sync the facts. It you run it standalone it will or if you restart the service then it will do the right thing. Do other people see this? Or have you all gone to running out of cron? What puppet version? Are you using factsync or pluginsync? Hi, I have noticed this through 0.24.x, 0.25.x and now 2.6.1 which we are running (both server and client) now everywhere. pluginsync = true pluginsource = puppet://$server/plugins Something is special about your case, as I've definitely used this functionality in 0.25.x. Can anyone else replicate this with a node in daemon mode? Anything exotic about your server/filesystem/mount ? Thanks, derek -- --- Derek T. Yarnell University of Maryland Institute for Advanced Computer Studies -- Nigel Kersten - Puppet Labs - http://www.puppetlabs.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
Re: [Puppet Users] Fact auto sync reloading
On 12/6/10 10:52 AM, Nigel Kersten wrote: On Mon, Dec 6, 2010 at 7:46 AM, Derek Yarnell de...@umiacs.umd.edu wrote: On 12/3/10 5:13 PM, Nigel Kersten wrote: On Fri, Dec 3, 2010 at 11:58 AM, Derek Yarnell de...@umiacs.umd.edu wrote: So we run puppetd as a long running ruby process on the hosts. When we update a fact that gets auto sync'd to the host it seems when puppetd wakes up and starts its catalog run it doesn't re-sync the facts. It you run it standalone it will or if you restart the service then it will do the right thing. Do other people see this? Or have you all gone to running out of cron? What puppet version? Are you using factsync or pluginsync? Hi, I have noticed this through 0.24.x, 0.25.x and now 2.6.1 which we are running (both server and client) now everywhere. pluginsync = true pluginsource = puppet://$server/plugins Something is special about your case, as I've definitely used this functionality in 0.25.x. Can anyone else replicate this with a node in daemon mode? Anything exotic about your server/filesystem/mount ? After double checking this, I can't seem to replicate it on 2.6.1 now. Sigh, sorry for the trouble. One other thing always annoys me though seems benign, # puppetd --test info: Retrieving plugin info: Loading facts in os_name info: Loading facts in hostname_hour info: Loading facts in os_platform info: Loading facts in nvidia_graphics info: Loading facts in os_version info: Loading facts in pam_limits_d info: Loading facts in rhn info: Loading facts in scratch info: Loading facts in os_name info: Loading facts in hostname_hour info: Loading facts in os_platform info: Loading facts in nvidia_graphics info: Loading facts in os_version info: Loading facts in pam_limits_d info: Loading facts in rhn info: Loading facts in scratch Why does it load the facts twice, or is this just misleading? Thanks, derek -- --- Derek T. Yarnell University of Maryland Institute for Advanced Computer Studies -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
Re: [Puppet Users] Fact auto sync reloading
On Mon, Dec 6, 2010 at 8:13 AM, Derek Yarnell de...@umiacs.umd.edu wrote: Why does it load the facts twice, or is this just misleading? That's currently an open issue: http://projects.puppetlabs.com/issues/3741. Thanks, 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-us...@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.
[Puppet Users] Fact auto sync reloading
So we run puppetd as a long running ruby process on the hosts. When we update a fact that gets auto sync'd to the host it seems when puppetd wakes up and starts its catalog run it doesn't re-sync the facts. It you run it standalone it will or if you restart the service then it will do the right thing. Do other people see this? Or have you all gone to running out of cron? Thanks, Derek -- Derek Yarnell -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
