795470 - (talos-r3-w7-004) talos-r3-w7-004 problem tracking

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

Comment 1

[Chris AtLee [:catlee]]

back in production

Comment 2

[Justin Wood (:Callek)]

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?

Comment 3

[Armen [:armenzg]]

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.

Comment 4

[John Hopkins (:jhopkins)]

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.

Comment 5

[John Hopkins (:jhopkins)]

Several good builds have been done

Comment 6

[Armen [:armenzg]]

Reboot needed.

Comment 7

[Armen [:armenzg]]

Reboot needed again.

We should look at the event viewer to see if there is any indication on why it went down so fast.

Comment 8

[Phil Ringnalda (:philor)]

We should probably disable it in slavealloc, since it took three jobs (and burned them complaining of corrupted disk) an hour ago.

Comment 9

[Phil Ringnalda (:philor)]

Where by "three an hour ago" I actually  mean "59 over the last three hours."

Comment 10

[Nick Thomas [:nthomas] (UTC+12)]

Disabled in slavealloc + buildbot terminated.

Comment 11

[Van Le [:van]]

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

Comment 12

[Armen [:armenzg]]

Machine has been setup and put back into the pool.