Message boards :
Number crunching :
Waiting to acquire lock
Message board moderation
Author | Message |
---|---|
Send message Joined: 28 Mar 10 Posts: 671 Credit: 3,987,227 RAC: 691 |
Weird, never seen this before, the Wu Prop Wu remains in a Waiting to aquire lock stage ... ??? 10/17/2015 1:18:20 PM | WUProp@Home | task postponed 600.000000 sec: Waiting to acquire lock 10/17/2015 1:28:56 PM | WUProp@Home | task postponed 600.000000 sec: Waiting to acquire lock 10/17/2015 1:31:20 PM | | Windows is suspending operations 10/17/2015 1:31:20 PM | | Suspending computation - requested by operating system 10/17/2015 1:31:20 PM | | Suspending network activity - requested by operating system 10/17/2015 1:31:23 PM | | Resuming after OS suspension 10/17/2015 1:31:23 PM | | Resuming after OS suspension 10/17/2015 3:21:59 PM | | Resuming computation 10/17/2015 3:21:59 PM | | Resuming network activity |
Send message Joined: 11 Apr 10 Posts: 54 Credit: 382,341 RAC: 0 |
Weird, never seen this before, the Wu Prop Wu remains in a Waiting to aquire lock stage ... ??? The first thing a BOINC task does when it starts is open and lock the file "boinc_lockfile" in its allocated slot directory. This prevents another task from using the same slot until the lock is released. The only time I've seen this was after a task failed to stop running when BOINC was shut down (that was years ago; the way BOINC terminates tasks has been improved massively singe then). When BOINC is restarted it reallocates the slot and the new task finds itself locked out. It could also happen without atopping BOINC if a task notifies BOINC that it has finished but it continues running. "The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer |
©2024 Sébastien