What does this mean, and shpould I worry about it...

02/06/2007 15:09:13|Leiden Classical|Sending scheduler request: Requested by user
02/06/2007 15:09:13|Leiden Classical|(not requesting new work or reporting completed tasks)
02/06/2007 15:09:18|Leiden Classical|Scheduler RPC succeeded [server version 503]
02/06/2007 15:09:18|Leiden Classical|Deferring communication for 3 min 1 sec
02/06/2007 15:09:18|Leiden Classical|Reason: requested by project
02/06/2007 15:09:31||Can't rename current state file to previous state file; The process cannot access the file because it is being used by another process. (0x20)
02/06/2007 15:12:38|uFluids|Sending scheduler request: Requested by user
02/06/2007 15:12:38|uFluids|(not requesting new work or reporting completed tasks)
02/06/2007 15:12:43|uFluids|Scheduler RPC succeeded [server version 509]
02/06/2007 15:12:43|uFluids|Deferring communication for 31 sec
02/06/2007 15:12:43|uFluids|Reason: requested by project

... I don't recall seeing that before.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

What version of BOINC? What OS? What security software? Was it a one time thing or is it happening over and over?


I was getting similar errors back in January on an alpha client (I'm looking at the email I sent to the alpha list, and it was in the 5.7.x and early 5.8.x range).

My first guess is there is a virus scan or something like that going on that has locked the file.

A couple questions Rom asked me at the time.

If you restart BOINC does it still happen? How about rebooting the computer? Will the system let you delete client_state_prev.xml yourself?

A thread with the problems I (and at least one other person) was having...

http://boinc.berkeley.edu/dev/forum_thread.php?id=1470

David did do a few code check-ins to deal with the issue.

The consensus from that thread seem to be adding the BOINC directory as an exclusion in your AV scanner works.

---

Kathryn :o)

5.8.15 under XP. I have NAV, but it would not have been scanning then, it scans at night. Looks like it was a one-off. The client_state and client_state_prev XML files have both been updated later today.

I can't think of anything that would have had the file locked at that time except BOINC itself.

Since that time, projects have up/downloaded, new work has arrived, there are no unusual events reported.

I've knocked up a little perl script to search for the message and see if it comes up more often.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Sounds good.

Let us know if it happens again/repeatedly.

---

Kathryn :o)

Sounds good.
Let us know if it happens again/repeatedly.

You can also get a copy of unlocker http://ccollomb.free.fr/unlocker/

That way you can find what process has it locked!

06/06/2007 17:31:01|Docking@Home|Reporting 1 tasks
06/06/2007 17:31:06|Docking@Home|Scheduler RPC succeeded [server version 509]
06/06/2007 17:31:06|Docking@Home|Deferring communication for 11 sec
06/06/2007 17:31:06|Docking@Home|Reason: requested by project
06/06/2007 17:52:37||Can't rename current state file to previous state file; The process cannot access the file because it is being used by another process. (0x20)
06/06/2007 17:58:13|QMC@HOME|Sending scheduler request: Requested by user
06/06/2007 17:58:13|QMC@HOME|(not requesting new work or reporting completed tasks)
06/06/2007 17:58:18|QMC@HOME|Scheduler RPC succeeded [server version 509]

Well, it's not what you would call regular, but it has happened again. I'll have a look at that unlocker program - thanks for the steer.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Won't let me edit!

Okay, so...

06/06/2007 17:58:18|QMC@HOME|Scheduler RPC succeeded [server version 509]
06/06/2007 17:58:18|QMC@HOME|Deferring communication for 7 sec
06/06/2007 17:58:18|QMC@HOME|Reason: requested by project
06/06/2007 18:04:31||Can't rename current state file to previous state file; The process cannot access the file because it is being used by another process. (0x20)
06/06/2007 19:03:02|QMC@HOME|Sending scheduler request: To fetch work
06/06/2007 19:03:02|QMC@HOME|Requesting 736 seconds of new work
06/06/2007 19:03:08|QMC@HOME|Scheduler RPC succeeded [server version 509]
06/06/2007 19:03:08|QMC@HOME|Deferring communication for 7 sec
06/06/2007 19:03:08|QMC@HOME|Reason: requested by project
06/06/2007 19:03:10|QMC@HOME|[file_xfer] Started download of file qmc.in.two_470_peptidexp.1833

... again, but all still seems to function. client_state and client_state_prev xml files both have time stamps of 20:20 so they are obviously updating.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

http://boinc.berkeley.edu/trac/ticket/205

I changed the Mac ticket to show it for all OSes.

---

Greetings,

I would like to share some info...

I got a similar message today - #0x5.
(I had posted this on the boinc-simap forum and those knowledable
said it was a BOINC client problem.....)

Perhaps a virus scan (Kaspersky) was in effect. I'm not sure.

Here are 3 messages:
11/29/2007 2:17:56 PM|boincsimap|Starting task 7120101.026807_0 using simap version 510
11/29/2007 2:49:34 PM||Can't rename current state file to previous state file; Access is denied. (0x5)
11/29/2007 2:49:40 PM||Can't delete previous state file; Access is denied. (0x5)


I did see a common item with the other posts - a tx timeout/retry ....
This had happened earlier..... 3 or so hours earlier...

11/29/2007 11:22:33 AM|boincsimap|Started upload of 7120101.026820_0_0
11/29/2007 11:22:34 AM||Project communication failed: attempting access to reference site
11/29/2007 11:22:34 AM|boincsimap|Temporarily failed upload of 7120101.026820_0_0: http error
11/29/2007 11:22:34 AM|boincsimap|Backing off 1 min 19 sec on upload of 7120101.026820_0_0
11/29/2007 11:22:36 AM||Access to reference site succeeded - project servers may be temporarily down.
11/29/2007 11:22:45 AM|boincsimap|Started upload of 7120101.026820_0_0
11/29/2007 11:22:46 AM|boincsimap|Finished upload of 7120101.026820_0_0
11/29/2007 11:23:18 AM|boincsimap|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
11/29/2007 11:23:20 AM||Project communication failed: attempting access to reference site
11/29/2007 11:23:21 AM||Access to reference site succeeded - project servers may be temporarily down.
11/29/2007 11:23:23 AM|boincsimap|Scheduler request failed: Transferred a partial file
11/29/2007 11:24:26 AM|boincsimap|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
11/29/2007 11:24:32 AM|boincsimap|Scheduler request succeeded: got 0 new tasks
11/29/2007 11:24:32 AM|boincsimap|Message from server: Completed result 7120101.026820_0 refused: result already reported as success



Just grasping at straws at the tx tie-in -

Environment:

11/29/2007 5:59:13 PM||Starting BOINC client version 5.10.28 for windows_intelx86
11/29/2007 5:59:13 PM||log flags: task, file_xfer, sched_ops
11/29/2007 5:59:13 PM||Libraries: libcurl/7.17.0 OpenSSL/0.9.8e zlib/1.2.3
11/29/2007 5:59:13 PM||Data directory: C:\Program Files\BOINC
11/29/2007 5:59:13 PM||Processor: 1 GenuineIntel Intel(R) Pentium(R) 4 Mobile CPU 1.70GHz [x86 Family 15 Model 2 Stepping 4]
11/29/2007 5:59:13 PM||Processor features: fpu tsc sse mmx
11/29/2007 5:59:13 PM||OS: Microsoft Windows 2000: Professional Edition, Service Pack 4, (05.00.2195.00)
11/29/2007 5:59:13 PM||Memory: 254.98 MB physical, 980.97 MB virtual
11/29/2007 5:59:13 PM||Disk: 11.18 GB total, 4.05 GB free
11/29/2007 5:59:13 PM||Local time is UTC -5 hours

Other:
I had only a single WU for each of Simap and Seti.
I was concerned about a loss of work if the simap task swapped out to seti;
so, I suspended set until the simap completed and uploaded.

Seti@home was able to update the
client_state.xml
and
client_state_prev.xml
files without a problem.
So, its not e recurring problem.....

I guess I shouldn't worry about it.

Thanks in advance,
Jay