Closed Bug 555790 Opened 10 years ago Closed 10 years ago
The talos-r3-snow-* machines can't reach 10
.2 .71 .136
talos-r3-snow-001:~ cltbld$ mount -a mount_nfs: can't access /export/buildlogs/puppet-files: Permission denied I have also tried it as sudo and manually: talos-r3-snow-001:~ root# mount 10.2.71.136:/export/buildlogs/puppet-files /N mount_nfs: can't access /export/buildlogs/puppet-files: Permission denied This blocks me on testing my puppet changes for snow leopard and therefore the unit test on talos project.
bash-3.2$ ping 10.2.71.136 PING 10.2.71.136 (10.2.71.136): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 ^C --- 10.2.71.136 ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss bash-3.2$ traceroute 10.2.71.136 traceroute to 10.2.71.136 (10.2.71.136), 64 hops max, 52 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * Can please somebody look into this?
Summary: help debugging why /N is not mounting on talos-r3-snow-001 → talos-r3-snow-001 can't reach 10.2.71.136
This is blocking us rolling out a Q1 goal. Any chance of quick help?
what does showmount -e 10.2.71.136 say?
18:18 < nthomas> showmount is fails on talos-r3-snow-001 18:19 < nthomas> $ showmount -e 10.2.71.136 18:19 < nthomas> Cannot MNT RPC: RPC: Port mapper failure - RPC: Timed out 18:19 < nthomas> can't connect socket for RPC This looks like a firewall problem to me. That mount can be accessed from any box in the this network space.. ro,email@example.com/24,firstname.lastname@example.org/24,rw=10.2.90/23,root=10.2.90/23,email@example.com/24,firstname.lastname@example.org/24 Derek, can you take a look at this? If you think the firewall looks okay, let me know which network they appear as when they talk to 10.2.71.136 and I will poke at the sun box some more.
Assignee: server-ops → dmoore
I can't ping that IP from any of the talos-r3-snow leopard machines.
Summary: talos-r3-snow-001 can't reach 10.2.71.136 → The talos-r3-snow-* machines can't reach 10.2.71.136
Fixed by updating static routes on the NFS server to reflect the new Castro build netmask.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.