[MDC1] T-W1064-MS-121 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
People
(Reporter: arny, Unassigned)
References
Details
Reporter | ||
Updated•6 years ago
|
Updated•6 years ago
|
Comment 1•6 years ago
|
||
Comment 2•6 years ago
|
||
Updated•6 years ago
|
Comment 3•6 years ago
|
||
Comment 4•6 years ago
|
||
re-opening bug as the machine isn't available on taskcluster
The papertrail last entries :
Mar 16 17:02:30 T-W1064-MS-121.mdc1.mozilla.com mlx4eth63: Mellanox ConnectX-3 Pro Ethernet Adapter device detected that the link connected to port 2 is down. This can occur if the physical link is disconnected or damaged, or if the other end-port is down.
Mar 16 17:02:30 T-W1064-MS-121.mdc1.mozilla.com Microsoft-Windows-DNS-Client: The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings: Adapter Name : {7086DA67-9AE0-4135-B2B0-1A847D8914A8} Host Name : T-W1064-MS-121 Primary Domain Suffix : mdc1.mozilla.com DNS server list : 10.48.75.120, 10.50.75.120 Sent update to server : <?> IP Address(es) : 10.49.40.77 The reason the system could not register these RRs during the update request was because of a system problem. You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.
Mar 16 17:02:31 T-W1064-MS-121.mdc1.mozilla.com generic-worker-wrapper: Checking for manifest completion
Mar 16 17:02:33 T-W1064-MS-121.mdc1.mozilla.com Microsoft-Windows-DNS-Client: The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings: Adapter Name : {7086DA67-9AE0-4135-B2B0-1A847D8914A8} Host Name : T-W1064-MS-121 Primary Domain Suffix : mdc1.mozilla.com DNS server list : 10.48.75.120, 10.50.75.120 Sent update to server : <?> IP Address(es) : 10.49.40.77 The reason the system could not register these RRs during the update request was because of a system problem. You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.
tried to ping the machine and received reply :
ping t-w1064-ms-121.wintest.releng.mdc1.mozilla.com
Pinging t-w1064-ms-121.wintest.releng.mdc1.mozilla.com [10.49.40.77] with 32 bytes of data:
Reply from 10.49.40.77: bytes=32 time=202ms TTL=126
Reply from 10.49.40.77: bytes=32 time=202ms TTL=126
Reply from 10.49.40.77: bytes=32 time=202ms TTL=126
Reply from 10.49.40.77: bytes=32 time=202ms TTL=126
Ping statistics for 10.49.40.77:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 202ms, Maximum = 202ms, Average = 202ms
Updated•6 years ago
|
Comment 5•6 years ago
•
|
||
Ran a re-image process. Currently the worker can be found on taskcluster, but it didn't ran any jobs yet :
We will keep on monitoring it.
Comment 6•6 years ago
|
||
the machine seems to be up and running and taking jobs.
https://tools.taskcluster.net/provisioners/releng-hardware/worker-types/gecko-t-win10-64-hw/workers/mdc1/T-W1064-MS-121
We will close the bug for now. If the problem will persist in the future, we will re-open this bug.
Updated•5 years ago
|
Description
•