Running in webrick, for the exact same node, we saw 458 seconds to compile
using directory environments vs 4.5 seconds using the old file-based
environments.
On Thursday, April 17, 2014 5:23:24 AM UTC-4, Antoine Cotten wrote:
Dear Puppet Users community, I would like to report an issue I
Josh, thanks for the info. Based on your description, I think I was seeing
a bug. Because the agents were all definitely getting certificates. When
I did the tcpdump, I could see them being used in the exchange. So, it
sounds like the puppetmaster running in webrick was still performing a
Master was able to reply without being able to resolve the name,
why was it bothering to resolve the name instead of just replying directly
to the request?
Thanks,
Kirk
On Wednesday, January 9, 2013 5:45:16 PM UTC-5, Kirk Steffensen wrote:
Josh,
use_srv_records is not set in puppet.conf
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
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
Here is the strace output from one of the 10-second periods while waiting
for the File notice to appear. https://gist.github.com/4497263
The strace output came in two bursts during this 10-seconds.
The thing that leaps out at me is that of the 4061 lines of output, 3754 of
them are
, January 9, 2013 5:13:04 PM UTC-5, Josh Cooper wrote:
Hi Kirk,
Do you happen to have SRV lookups enabled via the `use_srv_records`
setting? You may want to run tcpdump and look for extraneous DNS
lookups.
Josh
On Wed, Jan 9, 2013 at 2:00 PM, Kirk Steffensen
ki...@steffensenfamily.com
Hi,
I have a fresh CentOS 5.8 Vagrant VM that I'm using to emulate a customer's
server. During the first Puppet run, it takes 13 minutes and 48 seconds to
sync the Puppet Labs stdlib module. On a similar Ubuntu 12.04.1 Vagrant
VM, Puppet starts up, and almost instantly goes from plugin sync
installed when building your Centos vagrant box btw
(VBoxGuestAdditions) ... I'm not sure of its origin but this can be an
important step for network performance.
On Mon, Jan 7, 2013 at 4:50 PM, Kirk Steffensen
ki...@steffensenfamily.com javascript: wrote:
Hi,
I have a fresh CentOS
known to be a problem - alas it shouldn't be a problem during a
sequential pluginsync :-(.
On Mon, Jan 7, 2013 at 6:28 PM, Kirk Steffensen
ki...@steffensenfamily.com javascript: wrote:
Ken,
Thanks. I agree with your gut feeling, but after running the first
round of
tests you
10 matches
Mail list logo
