Erwin
2012-Jan-27 10:59 UTC
[Puppet Users] yum.puppetlabs.com and downloads.puppetlabs.com unreachable
Since several weeks, both yum.puppetlabs.com and downloads.puppetlabs.com are unreachable from some connections. This is showing every time I check for updates in the repository. It seems that there is a problem in routing. See: traceroute to yum.puppetlabs.com (96.126.116.126), 30 hops max, 40 byte packets 1 … 2 … 3 vlan130.newxr2.nik-asd.internl.net (217.149.196.89) 2.124 ms 2.251 ms 2.709 ms 4 vlan51.newxr1.nik-asd.internl.net (217.149.207.201) 2.963 ms 2.886 ms 2.932 ms 5 bbr01.eq01.ams01.networklayer.com (195.69.146.82) 2.848 ms 2.865 ms 3.155 ms 6 ae7.bbr02.eq01.ams02.networklayer.com (50.97.18.213) 3.447 ms 3.368 ms 3.415 ms 7 ae0.bbr02.tg01.lon01.networklayer.com (50.97.18.210) 16.768 ms 11.892 ms 11.778 ms 8 ae7.bbr01.tg01.lon01.networklayer.com (50.97.18.206) 38.213 ms 38.338 ms 35.312 ms 9 ae1.bbr02.tl01.nyc01.networklayer.com (50.97.18.204) 74.553 ms 75.003 ms 74.937 ms 10 ae1.bbr01.eq01.chi01.networklayer.com (173.192.18.132) 96.712 ms 96.987 ms 97.576 ms 11 ae20.bbr01.eq01.dal03.networklayer.com (173.192.18.136) 115.286 ms 114.407 ms 114.534 ms 12 po31.dsr02.dllstx3.networklayer.com (173.192.18.227) 144.169 ms 140.364 ms 140.263 ms 13 * * * 14 po2.car01.dllstx2.networklayer.com (70.87.254.78) 115.204 ms 114.533 ms 114.426 ms 15 5a.7.1243.static.theplanet.com (67.18.7.90) 114.740 ms 116.290 ms 116.175 ms 16 * * * 17 * * * 18 * * * 19 * * * 20 etc… When I traceroute to puppetlabs.com, all is well: traceroute to puppetlabs.com (96.126.112.51), 30 hops max, 40 byte packets 1 … 2 … 3 vlan130.newxr2.nik-asd.internl.net (217.149.196.89) 2.551 ms 2.659 ms 2.095 ms 4 vlan51.newxr1.nik-asd.internl.net (217.149.207.201) 1.338 ms 2.002 ms 1.878 ms 5 bbr01.eq01.ams01.networklayer.com (195.69.146.82) 43.903 ms 44.072 ms 43.848 ms 6 ae7.bbr02.eq01.ams02.networklayer.com (50.97.18.213) 1.521 ms 1.859 ms 1.598 ms 7 ae0.bbr02.tg01.lon01.networklayer.com (50.97.18.210) 7.397 ms 7.434 ms 7.423 ms 8 ae7.bbr01.tg01.lon01.networklayer.com (50.97.18.206) 8.290 ms 8.152 ms 8.367 ms 9 ae1.bbr02.tl01.nyc01.networklayer.com (50.97.18.204) 75.874 ms 75.963 ms 76.013 ms 10 * * * 11 ae20.bbr01.eq01.dal03.networklayer.com (173.192.18.136) 119.603 ms 121.916 ms 121.599 ms 12 po31.dsr01.dllstx3.networklayer.com (173.192.18.225) 121.406 ms 120.453 ms 120.361 ms 13 te3-2.dsr01.dllstx2.networklayer.com (70.87.253.130) 120.158 ms 118.674 ms 118.645 ms 14 po1.car01.dllstx2.networklayer.com (70.87.254.74) 118.616 ms 118.558 ms 118.822 ms 15 5a.7.1243.static.theplanet.com (67.18.7.90) 122.036 ms 119.985 ms 119.083 ms From some other connections I can reach yum,puppetlabs.com without a problem. Anyone else seeing this as well? Is there a solution? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Michael Stahnke
2012-Jan-27 20:18 UTC
Re: [Puppet Users] yum.puppetlabs.com and downloads.puppetlabs.com unreachable
On Fri, Jan 27, 2012 at 2:59 AM, Erwin <erwin.bogaard@gmail.com> wrote:> Since several weeks, both yum.puppetlabs.com and > downloads.puppetlabs.com are unreachable from some connections. This > is showing every time I check for updates in the repository. > > It seems that there is a problem in routing. See: > traceroute to yum.puppetlabs.com (96.126.116.126), 30 hops max, 40 > byte packets > 1 … > 2 … > 3 vlan130.newxr2.nik-asd.internl.net (217.149.196.89) 2.124 ms > 2.251 ms 2.709 ms > 4 vlan51.newxr1.nik-asd.internl.net (217.149.207.201) 2.963 ms > 2.886 ms 2.932 ms > 5 bbr01.eq01.ams01.networklayer.com (195.69.146.82) 2.848 ms 2.865 > ms 3.155 ms > 6 ae7.bbr02.eq01.ams02.networklayer.com (50.97.18.213) 3.447 ms > 3.368 ms 3.415 ms > 7 ae0.bbr02.tg01.lon01.networklayer.com (50.97.18.210) 16.768 ms > 11.892 ms 11.778 ms > 8 ae7.bbr01.tg01.lon01.networklayer.com (50.97.18.206) 38.213 ms > 38.338 ms 35.312 ms > 9 ae1.bbr02.tl01.nyc01.networklayer.com (50.97.18.204) 74.553 ms > 75.003 ms 74.937 ms > 10 ae1.bbr01.eq01.chi01.networklayer.com (173.192.18.132) 96.712 ms > 96.987 ms 97.576 ms > 11 ae20.bbr01.eq01.dal03.networklayer.com (173.192.18.136) 115.286 > ms 114.407 ms 114.534 ms > 12 po31.dsr02.dllstx3.networklayer.com (173.192.18.227) 144.169 ms > 140.364 ms 140.263 ms > 13 * * * > 14 po2.car01.dllstx2.networklayer.com (70.87.254.78) 115.204 ms > 114.533 ms 114.426 ms > 15 5a.7.1243.static.theplanet.com (67.18.7.90) 114.740 ms 116.290 > ms 116.175 ms > 16 * * * > 17 * * * > 18 * * * > 19 * * * > 20 etc… > > When I traceroute to puppetlabs.com, all is well: > traceroute to puppetlabs.com (96.126.112.51), 30 hops max, 40 byte > packets > 1 … > 2 … > 3 vlan130.newxr2.nik-asd.internl.net (217.149.196.89) 2.551 ms > 2.659 ms 2.095 ms > 4 vlan51.newxr1.nik-asd.internl.net (217.149.207.201) 1.338 ms > 2.002 ms 1.878 ms > 5 bbr01.eq01.ams01.networklayer.com (195.69.146.82) 43.903 ms > 44.072 ms 43.848 ms > 6 ae7.bbr02.eq01.ams02.networklayer.com (50.97.18.213) 1.521 ms > 1.859 ms 1.598 ms > 7 ae0.bbr02.tg01.lon01.networklayer.com (50.97.18.210) 7.397 ms > 7.434 ms 7.423 ms > 8 ae7.bbr01.tg01.lon01.networklayer.com (50.97.18.206) 8.290 ms > 8.152 ms 8.367 ms > 9 ae1.bbr02.tl01.nyc01.networklayer.com (50.97.18.204) 75.874 ms > 75.963 ms 76.013 ms > 10 * * * > 11 ae20.bbr01.eq01.dal03.networklayer.com (173.192.18.136) 119.603 > ms 121.916 ms 121.599 ms > 12 po31.dsr01.dllstx3.networklayer.com (173.192.18.225) 121.406 ms > 120.453 ms 120.361 ms > 13 te3-2.dsr01.dllstx2.networklayer.com (70.87.253.130) 120.158 ms > 118.674 ms 118.645 ms > 14 po1.car01.dllstx2.networklayer.com (70.87.254.74) 118.616 ms > 118.558 ms 118.822 ms > 15 5a.7.1243.static.theplanet.com (67.18.7.90) 122.036 ms 119.985 > ms 119.083 ms > > From some other connections I can reach yum,puppetlabs.com without a > problem. > > Anyone else seeing this as well? > Is there a solution?Are you able to do: http://www.downforeveryoneorjustme.com/downloads.puppetlabs.com and http://www.downforeveryoneorjustme.com/yum.puppetlabs.com We have had no reports of users being unable to access our software. Are you still seeing these issues? Mike> > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > 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 post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Erwin
2012-Jan-27 22:45 UTC
[Puppet Users] Re: yum.puppetlabs.com and downloads.puppetlabs.com unreachable
Downforeveryone... says the service is up. I can confirm this with a traceroute from a VPS on another network (on which yum can check the repository). On my network bot URLs (which point to the same IP/server) still cannot be reached. I tried several machines, but all can''t reach this server. And it''s like that for several weeks (before that I could reach it). And it''s the only server I know of that has these problems. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Erwin
2012-Jan-31 13:50 UTC
[Puppet Users] Re: yum.puppetlabs.com and downloads.puppetlabs.com unreachable
It''s still impossible for me to reach (yum|downloads).puppetlabs.com. When I do a traceroute, it stops at hop ''static.theplanet.com''. On another network, I can see the next hop is ''li341-126.members.linode.com''. I ca reach linode.com, but I can''t reach the host ''li341-126.members.linode.com''. So there must be something wrong at linode.com or at the host itself. Hope someone can fix this. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Michael Stahnke
2012-Jan-31 16:44 UTC
Re: [Puppet Users] Re: yum.puppetlabs.com and downloads.puppetlabs.com unreachable
On Tue, Jan 31, 2012 at 5:50 AM, Erwin <erwin.bogaard@gmail.com> wrote:> It''s still impossible for me to reach (yum|downloads).puppetlabs.com. > When I do a traceroute, it stops at hop ''static.theplanet.com''. > On another network, I can see the next hop is > ''li341-126.members.linode.com''. I ca reach linode.com, but I can''t > reach the host ''li341-126.members.linode.com''. So there must be > something wrong at linode.com or at the host itself. > > Hope someone can fix this.I''ve forwarded to our operations team. They''ll be checking with Linode.> > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > 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 post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.