Bug 795470 (talos-r3-w7-004)

talos-r3-w7-004 problem tracking

RESOLVED FIXED

Status

P3
normal
RESOLVED FIXED
6 years ago
7 months ago

People

(Reporter: coop, Unassigned)

Tracking

Details

(Whiteboard: [buildduty][buildslaves][capacity])

Comment hidden (empty)
(Reporter)

Updated

6 years ago
Depends on: 795471
back in production
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Was stuck at login screen, I logged in with current cltbld pw and system seems amazingly sluggish [could be factor of r3 slave], the Administrator PW for the last 3 iterations did not work for me for an RDP session, so did not check the Registry for a missing Default Login or wrong pw, etc.

this is the first instance of DefaultLogin failing in a talos slave as far as I know, armen any thoughts?
Status: RESOLVED → REOPENED
Flags: needinfo?(armenzg)
Resolution: FIXED → ---

Comment 3

6 years ago
Callek, this can be checked by login in as cltbld either through RDP or VNC.

FTR we cannot RDP into the Administrator account as it doesn't exist for Windows 7 slaves.

You can run these:
reg query "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon" /v AutoAdminLogon
reg query "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon" /v DefaultPassword
reg query "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon" /v DefaultUserName

All three values were in the registry. This machine should not be having auto-login issues. I don't know why it would have stopped auto logging in.

I don't know on the 16th. I would disable the slave on slavealloc and check the Windows Application Logs if you wanted to dig deeper.
We can also just leave the slave taking jobs if you prefer depending on how much work there is for buildduty.

I did not find the host sluggish. I noticed VNC under-performing as usual. This is just a setting change that we should eventually deploy across the board. I have changed the setting on this slave and you should notice now the difference.
Flags: needinfo?(armenzg)
DefaultDomainName was set to  talos-r3-w7-005 rather than  talos-r3-w7-004.  I fixed that and it auto-logged in as cltbld after a reboot.
Several good builds have been done
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED

Comment 6

6 years ago
Reboot needed.
Status: RESOLVED → REOPENED
Depends on: 826001
Resolution: FIXED → ---

Updated

6 years ago
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED

Comment 7

6 years ago
Reboot needed again.

We should look at the event viewer to see if there is any indication on why it went down so fast.
Status: RESOLVED → REOPENED
Depends on: 826428
Resolution: FIXED → ---
No longer depends on: 826428
Depends on: 828016
Depends on: 829365
We should probably disable it in slavealloc, since it took three jobs (and burned them complaining of corrupted disk) an hour ago.
Where by "three an hour ago" I actually  mean "59 over the last three hours."
Disabled in slavealloc + buildbot terminated.
Depends on: 838367

Updated

6 years ago
Depends on: 842538

Updated

6 years ago
Depends on: 843590

Comment 11

6 years ago
Bad hard drive - we're looking for a replacement drive. We'll track this host through bug 838367.

Comment 12

6 years ago
Machine has been setup and put back into the pool.
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering

Updated

7 months ago
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.