Closed Bug 996651 Opened 11 years ago Closed 11 years ago

NFS symbol mount broken on symbolfetch1.dmz.phx1

Categories

(Infrastructure & Operations :: Storage, task)

x86_64
Windows 7
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ted, Unassigned)

Details

This NFS mount was configured in bug 913864. I RDPed into the VM yesterday to find it had rebooted (I'm not sure why) and the NFS mount was no longer working. Running the "map_symbols.bat" script on the desktop results in: C:\Users\mozilla\Desktop>nfs_mount -p z 10.8.74.13:/symbols WNetUseConnection(Z:, \\10.8.74.13\symbols) failed with error code 2. The system cannot find the file specified. Can one of you take a look and see what happened here?
Filer permissions looks fine. I don't have RDP into there. Doc says: Check for the running NFSv4.1 Client serivce Start a command prompt (Start->run cmd or your favorite GUI method including just typing cmd in any explorer title bar ) type "net start" (no quotes) and look for "NFSv4.1 Client" ( if the gnu tools are installed you can use "net start | grep -i NFS" to narrow results) Optionally for GUI users check the services control panel under either "manage" or "administrative tools" sections Could you check that? Google makes it sound like error code 2 is that the service isn't running.
You're right, the NFSv4.1 Client service is not running. I tried starting it but it fails saying something like "The service started then stopped". I don't know where to look for logs detailing more information. I'm happy to provide you with the login credentials via IRC.
OK, I think it's working now. There were at least 3 competing NFS clients. disabled the ones that we weren't having luck with originally and reinstalled the 4.1 pnfs one that was working. several reboots later... re-mapped the drive, and rebooted again, just to make sure that it stays across reboots. It appears to have. Take a look, and let me know.
Thanks, looks good!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.