502031 - Enable cb-seamonkey-linux-01:9010 access from .nl colo machines

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Robert Kaiser]

The new buildbot master for SeaMonkey is running on cb-seamonkey-linux-01 and is just moving to production.

We currently have two VMs, cn-sea-qm-centos5-01 and cn-sea-qm-win2k3-01, running on the same ESX as the L10n server in the .nl colo, and slaves running on those should be able to connect to the new master now.

For that, we need those two slaves be able to access cb-sea-linux-tbox.sj.mozilla.com:9010. Could the firewall be configured to allow them connecting to this port?

On the other hand, we can remove the firewall rule added for bug 443228, cb-sea-linux-tbox:8010 doesn't need to be accessed from the outside any more, only the new cb-seamonkey-linux-01 master needs access (to 8010 for the web interface as has been set up in bug 492253, and to 910 from the two .nl slaves as requested in here).

Comment 1

[Robert Kaiser]

cb-sea-linux-tbox and cb-sea-win32-tbox also don't seem to be able to connect to cb-seamonkey-linux-01:9010 - are machines inside the community network also firewalled against each other? If so, could you please open access for those two as well?

Comment 2

[Derek Moore [:dmoore]]

At this time, cn-sea-qm-centos5-01 (63.245.212.102) and cn-sea-qm-win2k3-01 (63.245.212.103) should be able to access cb-sea-linux-tbox (63.245.210.16) on TCP port 9010.

As to cb-seamonkey-linux-01, there should be no firewall rules which would prevent access from other servers within the community network. Are you able to connect to ports other than 9010 (ssh, for example)?

Comment 3

[Robert Kaiser]

(In reply to comment #2)
> At this time, cn-sea-qm-centos5-01 (63.245.212.102) and cn-sea-qm-win2k3-01
> (63.245.212.103) should be able to access cb-sea-linux-tbox (63.245.210.16) on
> TCP port 9010.

Er, we got something wrong there, and I just realized my comment #0 disagrees with the summary - cn-sea-qm-centos5-01 and cn-sea-qm-win2k3-01 need access to cb-seamonkey-linux-01:9010

> As to cb-seamonkey-linux-01, there should be no firewall rules which would
> prevent access from other servers within the community network. Are you able to
> connect to ports other than 9010 (ssh, for example)?

cb-sea-linux-tbox can't ssh to cb-seamonkey-linux-01 - I need both cb-sea-linux-tbox and cb-sea-win32-tbox to be able to access cb-seamonkey-linux-01:9010 as well...

Comment 4

[Derek Moore [:dmoore]]

(In reply to comment #3)
> Er, we got something wrong there, and I just realized my comment #0 disagrees
> with the summary - cn-sea-qm-centos5-01 and cn-sea-qm-win2k3-01 need access to
> cb-seamonkey-linux-01:9010

This has been fixed.


> cb-sea-linux-tbox can't ssh to cb-seamonkey-linux-01 - I need both
> cb-sea-linux-tbox and cb-sea-win32-tbox to be able to access
> cb-seamonkey-linux-01:9010 as well...

Still troubleshooting this problem...

Comment 5

[Robert Kaiser]

(In reply to comment #4)
> (In reply to comment #3)
> > Er, we got something wrong there, and I just realized my comment #0 disagrees
> > with the summary - cn-sea-qm-centos5-01 and cn-sea-qm-win2k3-01 need access to
> > cb-seamonkey-linux-01:9010
> 
> This has been fixed.

Thanks, those work now.

> > cb-sea-linux-tbox can't ssh to cb-seamonkey-linux-01 - I need both
> > cb-sea-linux-tbox and cb-sea-win32-tbox to be able to access
> > cb-seamonkey-linux-01:9010 as well...
> 
> Still troubleshooting this problem...

Just like you, I wouldn't have expected to run into those problems within the cb network...

Comment 6

[Robert Kaiser]

(In reply to comment #3)
> cn-sea-qm-centos5-01 and cn-sea-qm-win2k3-01 need access to
> cb-seamonkey-linux-01:9010

Can you give them access to aus2-community.mozilla.org:22 as well? I now get errors because they can't push snippets up to that update server.

Comment 7

[Derek Moore [:dmoore]]

(In reply to comment #6)
> Can you give them access to aus2-community.mozilla.org:22 as well? I now get
> errors because they can't push snippets up to that update server.

Access granted.

Comment 8

[Robert Kaiser]

Thanks, that works now.

What's still open is that cb-sea-linux-tbox and cb-sea-win32-tbox can't connect to cb-seamonkey-linux-01:9010 yet.

Comment 9

[Derek Moore [:dmoore]]

cb-sea-linux-tbox is configured with a netmask of 255.255.255.224. I think it's likely cb-sea-win32-tbox is, as well.

The appropriate netmask for the community build network is 255.255.255.192. 

Fixing this netmask will allow the server to communicate properly with the rest of the network, including cb-seamonkey-linux-01.

Comment 10

[Robert Kaiser]

That was the clue I needed, thanks. Things are working fine now on those boxes, it seems. Thanks for all your help.