Closed
Bug 743937
Opened 14 years ago
Closed 14 years ago
dm-partnerdist01 unreachable from MPT-VPN
Categories
(Infrastructure & Operations Graveyard :: NetOps: DC ACL Request, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cbook, Assigned: cransom)
Details
seems something happened with dm-partnerdist while the move from bug 726707 because i cannot connect to partnerdist01 anymore.
using non hard entry in the hostfile i get:
debug1: Reading configuration data /Users/Tomcat/.ssh/config
debug1: Applying options for dm-partnerdist01.mozilla.org
debug1: Reading configuration data /etc/ssh_config
debug1: Applying options for *
debug1: Connecting to dm-partnerdist01.mozilla.org [10.2.74.38] port 22.
debug1: connect to address 10.2.74.38 port 22: Operation timed out
ssh: connect to host dm-partnerdist01.mozilla.org port 22: Operation timed out
when i use the ip from https://bugzilla.mozilla.org/show_bug.cgi?id=726707#c28 i get also operation time out.
The Side of effect of the problem is that BYOB is not building builds anymore since it depends on this server and apparently can't connect to this server too. It gives a can't connect error back on the repack.log :/
| Reporter | ||
Updated•14 years ago
|
Assignee: nobody → server-ops
Component: Release Engineering → Server Operations
QA Contact: release → phong
Comment 1•14 years ago
|
||
Ignore the connections to the wrong IP above - they're having trouble connecting to 10.22.74.132 as well. Ahill set this up in bug 743373 but wasn't able to verify (since it was pre-move).
This is blocking getting byob.mozilla.com up and running again (web interface is up, but the backend is still down), hence the severity level.
Assignee: server-ops → network-operations
Component: Server Operations → Server Operations: ACL Request
QA Contact: phong → ravi
Summary: dm-partnerdist01 down/lost/unable to connect → dm-partnerdist01 unreachable from MPT-VPN
| Assignee | ||
Updated•14 years ago
|
Assignee: network-operations → cransom
| Assignee | ||
Comment 2•14 years ago
|
||
i've rectified. let me know if you have any other issues.
[root@cm-vpn01 ~]# nc -vz 10.22.74.132 22
Connection to 10.22.74.132 22 port [tcp/ssh] succeeded!
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 3•14 years ago
|
||
verified fixed. also note that the internal NS might be need to be updated because without the IP entry for the ip from comment #2 it failes with Tomcats-MacBook-Pro:partners-staging Tomcat$ ssh -v dm-partnerdist01.mozilla.org
OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /Users/Tomcat/.ssh/config
debug1: Applying options for dm-partnerdist01.mozilla.org
debug1: Reading configuration data /etc/ssh_config
debug1: Applying options for *
debug1: Connecting to dm-partnerdist01.mozilla.org [10.2.74.38] port 22.
^C
and 10.2.74.38 is obviously the wrong ip :)
Comment 4•14 years ago
|
||
The DNS is right, it's just for a host that isn't there anymore.
The correct hostname is byob-app1.dmz.scl3.mozilla.com.
Updated•13 years ago
|
Product: mozilla.org → Infrastructure & Operations
Updated•3 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•