Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-12315

ASF JIRA is not accessible on one of Databricks' network

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: Jul 2016
    • Component/s: JIRA
    • Labels:
      None

      Description

      Starting yesterday, we can no longer access issues.apache.org on one of Databricks' network. It appears that on this network we could reach issues.apache.org, but we couldn't talk to the web servers.

      We checked firewalls on our side and did not find anything irregular, so we suspect the issue is on the Apache side.

      {noformat}
      ~ » curl icanhazip.com
      199.76.8.162
      ------------------------------------------------------------
      ~ » curl -vvv https://issues.apache.org
      * Rebuilt URL to: https://issues.apache.org/
      * Trying 140.211.11.138...
      * connect to 140.211.11.138 port 443 failed: Connection refused
      * Failed to connect to issues.apache.org port 443: Connection refused
      * Closing connection 0
      curl: (7) Failed to connect to issues.apache.org port 443: Connection refused
      ------------------------------------------------------------
      ~ » curl -vvv issues.apache.org
      * Rebuilt URL to: issues.apache.org/
      * Trying 140.211.11.138...
      * connect to 140.211.11.138 port 80 failed: Connection refused
      * Failed to connect to issues.apache.org port 80: Connection refused
      * Closing connection 0
      curl: (7) Failed to connect to issues.apache.org port 80: Connection refused
      ------------------------------------------------------------
      ~ » ping issues.apache.org
      PING issues.apache.org (140.211.11.138): 56 data bytes
      64 bytes from 140.211.11.138: icmp_seq=0 ttl=59 time=34.493 ms
      64 bytes from 140.211.11.138: icmp_seq=1 ttl=59 time=61.056 ms
      64 bytes from 140.211.11.138: icmp_seq=2 ttl=59 time=25.906 ms
      ^C
      --- issues.apache.org ping statistics ---
      3 packets transmitted, 3 packets received, 0.0% packet loss
      round-trip min/avg/max/stddev = 25.906/40.485/61.056/14.962 ms
      ------------------------------------------------------------
      ~ » traceroute issues.apache.org
      traceroute to issues.apache.org (140.211.11.138), 64 hops max, 52 byte packets
       1 192.168.0.1 (192.168.0.1) 5.942 ms 3.058 ms 18.037 ms
       2 199.76.8.161 (199.76.8.161) 11.317 ms 7.620 ms 3.950 ms
       3 ae3-265.bar1.sanfrancisco1.level3.net (4.14.105.141) 14.122 ms 11.549 ms 16.837 ms
       4 ae-1-51.edge2.seattle3.level3.net (4.69.147.139) 27.910 ms 36.537 ms 25.747 ms
       5 ae-1-51.edge2.seattle3.level3.net (4.69.147.139) 35.325 ms 39.401 ms 29.440 ms
       6 university.edge2.seattle3.level3.net (4.59.234.70) 32.858 ms 33.254 ms 31.199 ms
       7 corv-car1-gw.nero.net (207.98.64.39) 27.183 ms 31.245 ms 34.107 ms
       8 proxy1-us-west.apache.org (140.211.11.138) 27.052 ms 36.003 ms 27.741 ms
      ------------------------------------------------------------
      ~ » nmap -sS issues.apache.org
      Starting Nmap 7.12 ( https://nmap.org ) at 2016-07-20 15:00 PDT
      Nmap scan report for issues.apache.org (140.211.11.138)
      Host is up (0.033s latency).
      rDNS record for 140.211.11.138: proxy1-us-west.apache.org
      All 1000 scanned ports on issues.apache.org (140.211.11.138) are filtered
      Nmap done: 1 IP address (1 host up) scanned in 6.02 seconds
      {noformat}

        Attachments

          Activity

            People

            • Assignee:
              humbedooh Daniel Gruno
              Reporter:
              rxin Reynold Xin
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: