Project

General

Profile

tickets #80352

ns3.opensuse.org reports wrong IP to meet.opensuse.org

Added by tjyrinki@suse.de about 1 year ago. Updated 12 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Core services and infra
Target version:
-
Start date:
2020-11-25
Due date:
% Done:

0%

Estimated time:

Description


Admin mailing list -- admin@lists.opensuse.org
To unsubscribe, email admin-leave@lists.opensuse.org
List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette
List Archives: https://lists.opensuse.org/archives/list/admin@lists.opensuse.org

The new meet.o.o server was put into place, and it's at 195.135.221.174.
However, ns3.opensuse.org disagrees and reports 173, which breaks
meet.o.o for everyone (unless using direct IP).

Meanwhile, ns2 and ns4 are also down, possibly something to look at as
well and verify if they'll eventually agree on the IP of meet.o.o.

-Timo

OpenPGP_0xE0F759F790BDD207.asc (29.1 KB) OpenPGP_0xE0F759F790BDD207.asc tjyrinki@suse.de, 2020-11-25 09:56
OpenPGP_signature.asc (840 Bytes) OpenPGP_signature.asc tjyrinki@suse.de, 2020-11-25 09:56

History

#1 Updated by pjessen about 1 year ago

  • Category set to Core services and infra
  • Private changed from Yes to No

AFAICT, ns1 and ns2 are both running, ns3 is not up-to-date and ns4 is down.

#2 Updated by cboltz 12 months ago

  • Status changed from New to Resolved

ns3 was fixed in the meantime and now is up to date again.

ns4 (in Provo) is running, but doesn't have a public IP (the interface is missing in the VM). On the positive side, our whois and NS records don't include ns4, so from the outside view, nothing is broken ;-) We'll need to fix ns4 nevertheless, but it doesn't make sense to keep this ticket open just for that.

Also available in: Atom PDF