Closed Bug 560460 Opened 14 years ago Closed 14 years ago

moz2-linux-slave51 can't mount the NFS file share

Categories

(Release Engineering :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rail, Assigned: bhearsum)

References

Details

Attachments

(1 file)

There is a dangled symlink in /tools directory pointing to non existing directory:

[cltbld@moz2-linux-slave51 ~]$ ls -l /tools/buildbot
lrwxrwxrwx 1 root root 28 Mar 25 07:13 /tools/buildbot -> /tools/buildbot-1a62c6abfe0d
[cltbld@moz2-linux-slave51 ~]$ ls -l /tools/buildbot-1a62c6abfe0d
ls: /tools/buildbot-1a62c6abfe0d: No such file or directory
bhearsum was using this for debugging something as of 2010/04/15, or at least that's what nagios tells me. it's not in the machine bookings though.

bhearsum: you still using it?
This one is back in the pool again.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Apr 20 10:37:54 moz2-linux-slave51 puppetd[2506]: (//Node[moz2-linux-slave51.build.mozilla.org]/sandbox-network/puppet-files-sandbox-netw
ork/Mount[puppet-files]/ensure) change from present to mounted failed: Execution of '/bin/mount -o ro /N' returned 32: mount: mount to NF
S server '10.2.76.136' failed: timed out (giving up).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: moz2-linux-slave51 doesn't have buildbot installed → moz2-linux-slave51 can't mount the NFS file share
I changed the IP of the NFS share in /etc/fstab and it seems to be syncing up with the puppet server now.
Assignee: nobody → bhearsum
This slave synced up and is connected to staging-master:9012
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
This machine is still claiming to be in the sandbox network in the configs, so it broke again. Lukas, was that done on purpose?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Attachment #440539 - Flags: review?(lsblakk) → review+
it was not left in the sandbox on purpose, switching it to the build network was overlooked in the re-imaging and bringing over to moz2 slave pool.
Comment on attachment 440539 [details] [diff] [review]
switch staging try slaves to build-network

changeset:   128:cf5ad9c3911c
Attachment #440539 - Flags: checked-in+
I synced this slave up again and rebooted -- worked fine. Should be fixed-real-real this time.
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: