Closed Bug 1470061 (t-yosemite-r7-385) Opened 6 years ago Closed 5 years ago

[MDC1] t-yosemite-r7-385 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dhouse, Unassigned)

References

Details

      No description provided.
Depends on: 1470062
Machine is visible in taskcluster and completing jobs.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 1490912
Summary: t-yosemite-r7-385.test.releng.mdc1.mozilla.com. problem tracking → [MDC1] t-yosemite-r7-385 problem tracking
today, I've tried to log on it but I've received STDIO issue. The problem still persists
machine seems to be up and running tasks. we will close the bug for now. If the problem will persist in the future, we will re-open the bug.
Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
Depends on: 1492559
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 1525251

tried to connect on the machine, but I've received the following message :

Passcode or option (1-2): 231814
ssh_exchange_identification: Connection closed by remote host

on papertrail, I've found many entries like this :

Feb 05 18:17:00 t-yosemite-r7-385.test.releng.mdc1.mozilla.com /usr/sbin/cron: (root) CMD (. /usr/local/bin/proxy_reset_env.sh && PUPPET_SERVER=releng-puppet2.srv.releng.mdc1.mozilla.com /usr/local/bin/renew_cert.sh > /dev/null 2>&1)
Feb 05 18:17:05 t-yosemite-r7-385.test.releng.mdc1.mozilla.com fseventsd: event logs in /.fseventsd out of sync with volume. destroying old logs. (-71070 71076 11)
Feb 05 18:17:05 t-yosemite-r7-385.test.releng.mdc1.mozilla.com fseventsd: log dir: /.fseventsd getting new uuid: 5AE2A2AB-4CA0-4A42-94E5-F71F42EE53B0
Feb 05 18:17:15 t-yosemite-r7-385.test.releng.mdc1.mozilla.com fseventsd: event logs in /.fseventsd out of sync with volume. destroying old logs. (-71081 71086 10)
Feb 05 18:17:15 t-yosemite-r7-385.test.releng.mdc1.mozilla.com fseventsd: log dir: /.fseventsd getting new uuid: 0F08E20E-6700-4C69-A39E-A416DD7194EC
Feb 05 18:17:26 t-yosemite-r7-385.test.releng.mdc1.mozilla.com fseventsd: event logs in /.fseventsd out of sync with volume. destroying old logs. (-71091 71097 11)
Feb 05 18:17:26 t-yosemite-r7-385.test.releng.mdc1.mozilla.com fseventsd: log dir: /.fseventsd getting new uuid: 15B26F08-8927-4955-9CEF-4E22E98B4383
Feb 05 18:17:46 t-yosemite-r7-385.test.releng.mdc1.mozilla.com fseventsd: event logs in /.fseventsd out of sync with volume. destroying old logs. (-71112 71117 10)
Feb 05 18:17:46 t-yosemite-r7-385.test.releng.mdc1.mozilla.com fseventsd: log dir: /.fseventsd getting new uuid: 845D41E0-DB14-4315-8609-B7C1470BEC08
Feb 05 18:17:57 t-yosemite-r7-385.test.releng.mdc1.mozilla.com fseventsd: event logs in /.fseventsd out of sync with volume. destroying old logs. (-71122 71128 11)
Feb 05 18:17:57 t-yosemite-r7-385.test.releng.mdc1.mozilla.com fseventsd: log dir: /.fseventsd getting new uuid: 53A1D975-B5A7-4DE8-9504-38F30C29D2A2
Feb 05 18:18:07 t-yosemite-r7-385.test.releng.mdc1.mozilla.com fseventsd: event logs in /.fseventsd out of sync with volume. destroying old logs. (-71133 71138 10)
Feb 05 18:18:07 t-yosemite-r7-385.test.releng.mdc1.mozilla.com fseventsd: log dir: /.fseventsd getting new uuid: 26AAD760-7E78-4685-B360-3C1B705F41A3

Dave, can you please take a look ?

Flags: needinfo?(dave.a.house)
Flags: needinfo?(dhouse)

QTS reset SMC and NVRAM and ran internet hardware diagnostics (no problems found). I reimaged the machine and have un-quarantined it.

It ran 12 tasks this evening: 10 success, 1 exception, 1 failure.

Status: REOPENED → RESOLVED
Closed: 6 years ago5 years ago
Flags: needinfo?(dhouse)
Flags: needinfo?(dave.a.house)
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.