apt.puppetlabs.com to slow

[Tudor Rogoz]

Hello,

The apt.puppetlabs.com repository is not responding, or is responding to slow. [0]

Is a temporary issue or was moved to a different address?

Tudor

[0]

wget http://apt.puppetlabs.com/puppetlabs-release-stable.deb

--2013-12-11 13:23:30--  http://apt.puppetlabs.com/puppetlabs-release-stable.deb

Resolving apt.puppetlabs.com (apt.puppetlabs.com)... 198.58.114.168, 2600:3c00::f03c:91ff:fe69:6bf0

Connecting to apt.puppetlabs.com (apt.puppetlabs.com)|198.58.114.168|:80... failed: Connection timed out.

Connecting to apt.puppetlabs.com (apt.puppetlabs.com)|2600:3c00::f03c:91ff:fe69:6bf0|:80... failed: Network is unreachable.

[Tony McMahon]

I'm seeing this with yum.puppetlabs.com as well.

Something's up, me thinks...

[Rob Braden]

Something was up...

We were running out of available http server threads. There was one particular client being a bit aggressive with the number of concurrent requests. The http server config has been tweaked a bit and that client has been throttled. At the moment, everything appears to be working normally. We will continue to monitor, but don't hesitate to speak up if you see further issues, either here or in #puppet.

Thanks!

Rob Braden

[Russell Jackson]

I've been constantly seeing errors from apt-get update being unable to connect to apt.puppetlabs.com for months.

It is very confusing because apt tries the ipv4 address first. It times out. Then, it tries the ipv6 address which for must of us results in a network unreachable; however, it doesn't display an error about the timeout and only display's the network unreachable from the ipv6 attempt. Annoying!

[Rob Braden]

  Hopefully the changes that we are implementing today will significantly mitigate these issues. Please let us know here, in #puppet or for maximum visibility, update the ticket at https://projects.puppetlabs.com/issues/23397 if you continue to see issues.

Thanks, apologies for the issues.