Closed Bug 1533248 (t-yosemite-r7-472) Opened 6 years ago Closed 6 years ago

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

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: apop, Unassigned)

References

Details

The machine haven't took jobs for 3 days.
It has been reboot several times and reimaged, but this haven't solved the issue.
In papertrail I've found the following:

Mar 06 19:35:52 t-yosemite-r7-472.test.releng.mdc1.mozilla.com generic-worker: 2019/03/06 19:35:52 No task claimed. Idle for 4m58.615991503s (will exit if no task claimed in 95h55m1.384008497s). 1 more tasks to run before exiting.
Mar 06 19:36:52 t-yosemite-r7-472.test.releng.mdc1.mozilla.com nsurlstoraged: realpath() returned NULL for /var/root/Library/Caches/ocspd
Mar 06 19:36:52 t-yosemite-r7-472.test.releng.mdc1.mozilla.com nsurlstoraged: The read-connection to the DB=/var/root/Library/Caches/ocspd/Cache.db is NOT valid. Unable to determine schema version.
Mar 06 19:36:52 t-yosemite-r7-472.test.releng.mdc1.mozilla.com nsurlstoraged: realpath() returned NULL for /var/root/Library/Caches/ocspd
Mar 06 19:36:52 t-yosemite-r7-472.test.releng.mdc1.mozilla.com nsurlstoraged: realpath() returned NULL for /var/root/Library/Caches/ocspd
Mar 06 19:36:52 t-yosemite-r7-472.test.releng.mdc1.mozilla.com nsurlstoraged: ERROR: unable to determine file-system usage for FS-backed cache at /var/root/Library/Caches/ocspd/fsCachedData. Errno=13
Mar 06 19:37:07 t-yosemite-r7-472.test.releng.mdc1.mozilla.com generic-worker: 2019/03/06 19:37:07 No task claimed. Idle for 6m14.410299444s (will exit if no task claimed in 95h53m45.589700556s). 1 more tasks to run before exiting.

Depends on: 1533249

This machine was reallocated into the new gecko-3-t-osx-1010 worker type.

https://bugzilla.mozilla.org/show_bug.cgi?id=1530732

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.