Core 8900 "Clean Up"

[Clyde46]

Got a 8900 WU sitting at the "Clean up" stage. According to the logs, the server has acknowledged it so I'm not sure whats going on. Also, this is a snipet.

Code: Select all

07:59:48:WU01:FS00:Upload 88.20%
07:59:53:WARNING:WU00:FS00:Failed to get assignment from 'assign-GPU.stanford.edu:80': 10002: Received short response, expected 272 bytes, got 0
07:59:53:WU00:FS00:Connecting to assign-GPU.stanford.edu:8080
07:59:54:WU01:FS00:Upload 93.99%
08:00:00:WU01:FS00:Upload 99.77%
08:00:08:WU01:FS00:Upload complete
08:00:08:WU01:FS00:Server responded WORK_ACK (400)
08:00:08:WU01:FS00:Final credit estimate, 20253.00 points
08:00:08:WU01:FS00:Cleaning up
08:00:08:ERROR:WU01:FS00:Exception: Failed to remove directory './work/01': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\01\wudata_01.dat"
08:00:08:WU01:FS00:Cleaning up
08:00:08:ERROR:WU01:FS00:Exception: Failed to remove directory './work/01': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\01\wudata_01.dat"
08:00:35:WARNING:WU00:FS00:Failed to get assignment from 'assign-GPU.stanford.edu:8080': 10002: Received short response, expected 272 bytes, got 0
08:00:35:ERROR:WU00:FS00:Exception: Could not get an assignmen

[P5-133XL]

reboot and see if that fixes things.

I'd also like to see the system and config portions of the log for diagnosis purposes.

[gimpy]

ithink you should have re-booted internet connect,F@H client. Not P.C. Did that work or you lose all your work? I think you got great advice for different problem?

[davidcoton]

It looks as though something else was accessing the work folder -- were you checking files behind the scenes? I think it is only the delete of the old file that failed, so a reboot may well sort it out. Otherwise, find and stop the other process, then delete the ./work/01 folder manually. Cleanup will be noted at next restart.

(As an aside, note the forward slashes -- Linux? Interesting that the first part of the error message uses backslashes -- probably generated by the client using Windows convention? Inn any case a bug, albeit very minor.)

David

EDIT: may be a Core17 bug, see https://fah.stanford.edu/projects/FAHCl ... #comment:1

[bmxjumperc]

I have that same error on project 8900
it was/is on the FAHCore_17.exe version 0.0.52
after rebooting the cleanup is gone