647301 - give myk access to two minis (1x win7, 1x10.6)

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

To debug bug#647126 and bug#647124, myk wants access to a production machine on each of win7 and 10.6.

Comment 1

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

pushing to aki as he is on slaveduty today.

Comment 2

[Aki Sasaki (not active)]

Name:   talos-r3-snow-001.build.scl1.mozilla.com
Address: 10.12.50.54

Name:   t-r3-w764-001.build.scl1.mozilla.com
Address: 10.12.50.214

User/pass sent via email.

Comment 3

[Myk Melez [:myk] [@mykmelez]]

I don't seem to be able to access these machines.  I can connect to and view the Windows machine using cotvnc, but my view of it is frozen (the time indicator in the taskbar doesn't update), and mouse movement/button clicks don't seem to have any effect.

Subsequent attempts to connect fail, although if I wait a while to reconnect I can do so (so perhaps there is some inactivity timeout after which the remote machine drops the initial connection and allows subsequent ones).

I can't connect to the Mac machine at all; cotvnc reports that my connection attempt is unsuccessful.  Aki suggested that I might need to tunnel through the build VPN, but that didn't help, and it doesn't seem necessary in any case, since I do have access to the IP address in question (I can ping it, and I can SSH into the machine).

After the batch of fixes that landed last Friday, the Mac machines turned green, so right now it is just the Windows machine issues that it is important to diagnose.  Can anyone provide insight into how I can get access to that machine?

Note: I don't have "view only" checked in the cotvnc configuration for that machine; but in any case the problem doesn't seem to be that the connection is in some "read-only" mode but rather that it becomes frozen right after the connection is initiated.

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

I can try rebooting the machine.  The VNC server on Win7 is junk -- this happens all the time.  Ping me in IRC (#build) for more assistance.

Comment 5

[Myk Melez [:myk] [@mykmelez]]

Status Update: I did end up getting access to the Windows machine with help from Dustin and other folks in #build, after which I tried to reproduce the Win 7 problems but was unable to.  Fortunately, we subsequently found other ways to diagnose the problems, and we think we have fixed them, so I don't think I still need access to these machines.

There are still more bugs to track down and squash, but I don't think these machines will be helpful in that regard.  And if we decide that we do need me to have access to machines again, we can always track that as a new request.

So I think this can be resolved fixed.  Do y'all need to do any cleanup before we do that?

Comment 6

[Dustin J. Mitchell [:dustin] (he/him)]

I'll schedule the boxes for a reimage (bug 651272 and bug 651271) and set-up (bug 647302).  Thanks!