Your browser was unable to load all of the resources. They may have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.

Corrupted log data causing build failures #4425

tomz ·

We're starting to see some random issues after upgrading from QB10 to 12 that have never seen before. Build failures are occurring when trying to trigger builds on some agents where the log on the agent references log corruption:

Caused by: java.lang.RuntimeException: java.io.FileNotFoundException: C:\QBAgent\temp\job_d3382aa0-dae6-4169-893b-cd1080eefcaa.log (The file or directory is corrupted and unreadable)

Has anyone seen this before? Does anyone know what it means, and the appropriate way to fix it?

  • replies 3
  • views 784
  • stars 0
robinshen ADMIN ·

Changes since QB10 should not touch anything affecting this. Is the agent shutdown during the build?

tomz ·

No but logging on to the machine allows us to see similar windows disk errors just when interacting with the .log file normally (won't open in text editor, can't be deleted without deleting the parent directory). We've completely taken the hosts off the grid for a more thorough disk check. We are hoping the QB upgrade had nothing to do with it since it was seen on only two hosts out of almost 400.

TZ

robinshen ADMIN ·

Also make sure the disk is not full.