Project

General

Profile

Actions

tickets #61650

closed

site outage software.opensuse.org

Added by mirppc@gmail.com over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Core services and virtual infrastructure
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:

Description

So i am been having issues accessing software.opensuse.org for about 3
days now. Per the information on status.opensuse.org i am emailing the
traceroute, ping and other information that i can gather. Sadly the
notice didnt say HOW to make a ticket.

"We've been experiencing sporadic outages of our web assets and generic
network connectivity issues throughout most of the day. The reasons are
not yet fully understood, and are still being investigated. For the
time being we've made some adjustments to our HA setup and haven't seen
the issues since then, but further investigations will be needed. Feel
free to make us aware of any network issues you're experiencing via
ticket(s) and some network debugging output (ping, mtr, traceroute), so
that we can gather more data to properly identify the problem."

Debug:

traceroute software.opensuse.org
Absolute path to 'traceroute' is '/usr/sbin/traceroute', so running it
may require superuser privileges (eg. root).
mirdellt610@hoppou:~/bin/neofetch> sudo traceroute
software.opensuse.org
[sudo] password for root:
traceroute to software.opensuse.org (195.135.221.140), 30 hops max, 60
byte packets
1 router.asus.com (192.168.5.1) 0.653 ms 1.184 ms 1.362 ms
2 Wireless_Broadband_Router.home (192.168.1.1) 3.740 ms 3.782
ms 3.860 ms
3 * * *
4 172.102.101.154 (172.102.101.154) 7.067 ms te-1-7-0-9---
0.lcr01.snmn.ca.frontiernet.net (172.102.98.32) 6.580 ms
172.102.106.210 (172.102.106.210) 8.081 ms
5 ae8---0.scr02.lsan.ca.frontiernet.net (74.40.3.49) 9.333 ms 9.152
ms ae8---0.scr01.lsan.ca.frontiernet.net (74.40.3.37) 7.215 ms
6 ae0---0.cbr01.lsan.ca.frontiernet.net (74.40.3.198) 7.320
ms 6.796 ms 5.092 ms
7 * * *
8 ge-6-3.car1.Hamburg1.Level3.net (4.69.141.133) 70.542 ms 69.754
ms 71.870 ms
9 ae0-3356.nyk10.core-backbone.com (4.35.80.194) 71.104 ms 71.777
ms 71.118 ms
10 ae2-2001.nbg30.core-backbone.com (81.95.15.161) 153.128
ms 153.370 ms 153.108 ms
11 core-backbone.microfocus.com (5.56.18.210) 151.540 ms 151.924
ms 150.905 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

ping software.opensuse.org
PING proxy-nue.opensuse.org (195.135.221.140) 56(84) bytes of data.
64 bytes from proxy-nue.opensuse.org (195.135.221.140): icmp_seq=1
ttl=53 time=150 ms
64 bytes from proxy-nue.opensuse.org (195.135.221.140): icmp_seq=2
ttl=53 time=151 ms
64 bytes from proxy-nue.opensuse.org (195.135.221.140): icmp_seq=3
ttl=53 time=150 ms
64 bytes from proxy-nue.opensuse.org (195.135.221.140): icmp_seq=4
ttl=53 time=150 ms
C
--- proxy-nue.opensuse.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 150.318/150.650/151.049/0.316 ms


Files

Actions #1

Updated by bmwiedemann over 4 years ago

I am getting the same partial traceroute.
When I run

traceroute -T software.opensuse.org

I get 1 more hop to the final destination, so some ICMP filtering might be involved somewhere.

mtr software.opensuse.org

could be more insightful, because it gathers statistics over a longer time.

Actions #2

Updated by bmwiedemann over 4 years ago

  • Private changed from Yes to No
Actions #3

Updated by lrupp over 4 years ago

  • Category set to Core services and virtual infrastructure
  • Status changed from New to Closed
  • % Done changed from 0 to 100

Haven't seen this behavior any longer - closing this ticket for now.

Thanks for the report!

Actions

Also available in: Atom PDF