Download (curl) error for 'http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_12.1/repodata/repomd.xml':
Error code: Connection failed
Error message: Failed to connect to 2001:67c:2178:8::13: Network is unreachable
I can’t connect via chrome (I could once, after several attempts and a very slow load), so I suppose is a server issue.
Where can I see if this is a server problem?
Like a “server status” icon or something.
Also, the forums are failing me too ;__;
>
> When using YaST or zypper:
>
>
> Code:
> --------------------
> Download (curl) error for
> ‘http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_12.1/repodata/repomd.xml’:
> Error code: Connection failed
> Error message: Failed to connect to 2001:67c:2178:8::13: Network is
> unreachable
> --------------------
>
> I can’t connect via chrome (I could once, after several attempts and a
> very slow load), so I suppose is a server issue.
>
> Where can I see if this is a server problem?
> Like a “server status” icon or something.
> Also, the forums are failing me too ;__;
>
>
The forums are currently much more reliable using NNTP.
Are You using NetworkManager or you prefer static configuration in YaST ?
Also please check if You’ve got some DNS problems:
PING download.opensuse.org (195.135.221.134) 56(84) bytes of data.
64 bytes from ftp.opensuse.org (195.135.221.134): icmp_seq=1 ttl=54 time=157 ms
64 bytes from ftp.opensuse.org (195.135.221.134): icmp_seq=2 ttl=54 time=157 ms
64 bytes from ftp.opensuse.org (195.135.221.134): icmp_seq=3 ttl=54 time=158 ms
64 bytes from ftp.opensuse.org (195.135.221.134): icmp_seq=4 ttl=54 time=156 ms
I also did a ping as per your request:
PING 8.8.4.4 (8.8.4.4) 56(84) bytes of data.
64 bytes from 8.8.4.4: icmp_seq=1 ttl=49 time=46.6 ms
64 bytes from 8.8.4.4: icmp_seq=2 ttl=49 time=45.8 ms
64 bytes from 8.8.4.4: icmp_seq=3 ttl=49 time=44.6 ms
64 bytes from 8.8.4.4: icmp_seq=4 ttl=49 time=47.8 ms
cat /etc/resolv.conf ended with (everything before was commented):
### Please remove (at least) this line when you modify the file!
search gdl.megared.net.mx
nameserver 192.168.0.1
finally:
route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
Also I think I’m using YaST to configure the network.
A coworker reported the same thing to me. I think this must be on
OpenSUSE’s side. I’ve also heard there were some disk issues recently
with the OpenSUSE Build Service so perhaps this is also related. I
believe it is known and being worked on as we type.
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
On 04/30/2012 12:17 PM, ab wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> A coworker reported the same thing to me. I think this must be on
> OpenSUSE’s side. I’ve also heard there were some disk issues recently
> with the OpenSUSE Build Service so perhaps this is also related. I
> believe it is known and being worked on as we type.
Two disks failed at the same time on download.opensuse.org, and they were unable
to recover without reloading the disks from scratch. nothing has been lost, but
it will take as long as a day to reload TB of data.
In the meantime, the IP number has been reassigned to a system of much lesser
power, thus it is likely being overloaded. At least it will be a stress test of
openSUSE.
>
> Everything is working now, it was a server issue.
>
> I just want to ask, is there a way of checking the server status? So
> people can be sure it’s not a fault on their side
>
>
That’s good to hear well I don’t think it’s possible if You’re not the
admin of the server. Otherwise is everything else is working and problems
are with specific server there’s a high probability the problem is on the
server side but it’s just wild guessing.
You could also try tracerouting to the server and see where the packets
get lost but not all service providers allow traceroute to pass through.
On 2012-04-30 19:46, kirbyiwakitsukino wrote:
> I just want to ask, is there a way of checking the server status? So
> people can be sure it’s not a fault on their side
Just read the announcements before asking. The problem was posted in
several places.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Carlos E. R. wrote:
> On 2012-04-30 19:46, kirbyiwakitsukino wrote:
>> I just want to ask, is there a way of checking the server status? So
>> people can be sure it’s not a fault on their side
>
> Just read the announcements before asking. The problem was posted in
> several places.
It would be quite a sensible idea to have a web-based status page
though. Our admins at work use SupportTrio, but I believe Nagios can
provide similar traffic light displays for particular services on
various hosts. It can show whether particular services on each host are
responding properly.
On 2012-05-01 14:47, Dave Howorth wrote:
> Carlos E. R. wrote:
>> On 2012-04-30 19:46, kirbyiwakitsukino wrote:
>>> I just want to ask, is there a way of checking the server status? So
>>> people can be sure it’s not a fault on their side
>>
>> Just read the announcements before asking. The problem was posted in
>> several places.
>
> It would be quite a sensible idea to have a web-based status page
> though. Our admins at work use SupportTrio, but I believe Nagios can
> provide similar traffic light displays for particular services on
> various hosts. It can show whether particular services on each host are
> responding properly.
Yes, would be nice. Does it have security dangers? :-?
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
well I don’t think it’s possible if You’re not the