Ken, thanks. Unfortunately, (from a troubleshooting standpoint), it only took one or two seconds to sync stdlib on the local box.
rm -rf /var/lib/puppet/lib/* puppet agent --test I saw the same stream of File notices, but they streamed by in real time, instead of taking 10 seconds per notice. John may still have something. There may still be some name resolution issue on the client, but it's just not obvious from the testing that I did. I haven't dug into the file provider code. What mechanism is it using to move the files from the server to the client? Could it be a delay in an scp handshake or the like? Thanks, Kirk On Wednesday, January 9, 2013 11:39:06 AM UTC-5, Ken Barber wrote: > > Damn, I thought John had it :-(. > > Here's a question I hadn't asked - whats your plugin sync performance > like on the puppetmaster node itself? ie. clear all synced files and > run it locally and time it, comparing to the other nodes. > > > > On Wed, Jan 9, 2013 at 4:02 PM, Kirk Steffensen > <ki...@steffensenfamily.com <javascript:>> wrote: > > John, I don't believe there is any name resolution issue. Both the > CentOS > > and Ubuntu base boxes have "192.168.33.1 puppet" in their /etc/hosts. > From > > inside the Vagrant VM, a ping to puppet responds immediately, and a > > tracepath to puppet returns as quickly as I can hit enter, showing > > sub-millisecond results. > > > > I'll be happy to try any other troubleshooting steps. For now, I've > just > > inserted pluginsync=false in the base boxes' puppet.conf files. But > I'll > > make another couple of base boxes with pluginsync=true for > troubleshooting, > > if needed. > > > > Thanks, > > Kirk > > > > On Tuesday, January 8, 2013 9:25:06 AM UTC-5, jcbollinger wrote: > >> > >> > >> Is it possible that you have a name resolution issue? The time scale > you > >> described is about right for a small number of name resolution timeouts > >> before the client falls back to a different name server or name > resolution > >> mechanism. > >> > >> > >> John > >> > > -- > > 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/-/hJ_-Tm4hg1cJ. > > > > To post to this group, send email to > > puppet...@googlegroups.com<javascript:>. > > > To unsubscribe from this group, send email to > > puppet-users...@googlegroups.com <javascript:>. > > For more options, visit this group at > > http://groups.google.com/group/puppet-users?hl=en. > -- 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/-/VZkrj4rKJ9gJ. To post to this group, send email to puppet-users@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.
