Questions and Answers : Windows : WU is stuck and not progressing
Message board moderation

To post messages, you must log in.

AuthorMessage
davalc

Send message
Joined: 20 Feb 22
Posts: 1
Credit: 1,816,000
RAC: 0
Message 5715 - Posted: 22 Jul 2022, 4:25:42 UTC

A work unit is stuck on 30.009%. The remaining time is decrementing and the elapsed time is incrementing. Should I delete this work unit and any work unit that is stuck/locked up? Am I wasting my processer time waiting it out? Thank you in advance.
ID: 5715 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Grant (SSSF)

Send message
Joined: 23 Apr 22
Posts: 167
Credit: 69,772,000
RAC: 0
Message 5716 - Posted: 22 Jul 2022, 9:40:59 UTC - in response to Message 5715.  

A work unit is stuck on 30.009%. The remaining time is decrementing and the elapsed time is incrementing. Should I delete this work unit and any work unit that is stuck/locked up? Am I wasting my processer time waiting it out? Thank you in advance.
If the remaining time is decreasing as the elapsed time increases, then it appears that the Task is being processed, even if the percentage done doesn't reflect that.
I'd let it run until the remaining time gets to zero- or until the remaining time starts to climb. If that occurs, exit & restart BOINC- it may complete & clear the Task, if not then abort it.
Grant
Darwin NT
ID: 5716 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Grant (SSSF)

Send message
Joined: 23 Apr 22
Posts: 167
Credit: 69,772,000
RAC: 0
Message 5717 - Posted: 24 Jul 2022, 8:21:57 UTC

A couple of your Tasks did error out- do you have a 3rd party AV programme? If so, i'd white list the BOINC data folders so they are not scanned by the AV programme. It's the only thing i can thing of that would cause that file access timeout error (unless BOINC is installed on a HDD that is being flogged).

<core_client_version>7.20.0</core_client_version>
<![CDATA[
<message>
Process still present 5 min after writing finish file; aborting</message>
<stderr_txt>
09:06:19 (7856): Can't acquire lockfile (32) - waiting 35s
09:06:54 (7856): Can't acquire lockfile (32) - exiting
09:06:54 (7856): Error: The process cannot access the file because it is being used by another process.

 (0x20)
09:36:24 (19532): Can't acquire lockfile (32) - waiting 35s
09:36:59 (19532): Can't acquire lockfile (32) - exiting
09:36:59 (19532): Error: The process cannot access the file because it is being used by another process.

 (0x20)
10:40:00 (4840): Can't acquire lockfile (32) - waiting 35s
10:40:35 (4840): Can't acquire lockfile (32) - exiting
10:40:35 (4840): Error: The process cannot access the file because it is being used by another process.

 (0x20)
12:57:12 (16260): called boinc_finish(0)

</stderr_txt>
]]>



And your completed Tasks show a fair difference between their Run time & CPU time, which indicates the system is over committed. I'd look at Task Manager to see what processes are using up so much CPU time.
Grant
Darwin NT
ID: 5717 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Questions and Answers : Windows : WU is stuck and not progressing




Copyright © 2024 Copernicus Astronomical Centre of the Polish Academy of Sciences
Project server and website managed by Krzysztof 'krzyszp' Piszczek