Opened 17 years ago

Closed 15 years ago

#205 closed Defect (fixed)

Can't rename current state file to previous state file

Reported by: Ageless Owned by: charlief
Priority: Major Milestone: Undetermined
Component: Client - Daemon Version:
Keywords: Cc:

Description

As reported by zombie67 on the BOINC_dev forums: http://boinc.berkeley.edu/dev/forum_thread.php?id=1827

I regularly have BOINC lock up. During the lock up, CPU usage drops to 0. After about a minute, it resumes with the following error message. Upon resuming, the tasks continue to crunch until complete like normal. FWIW, it does not cause the tasks to abort, or cause validation errors.

Tue May 22 09:43:47 2007Tue May 22 09:43:47 2007
Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
[error] Couldn't write state file: system rename

Tue May 22 09:44:47 2007|SETI@home|Task 05mr05aa.16368.15714.348568.3.118_6 exited with zero status but no 'finished' file Tue May 22 09:44:47 2007|SETI@home|If this happens repeatedly you may need to reset the project.

The last two lines are repeated, once for each task running (8 times total for my machine).

The permissions look correct to me. I have tried resetting with no luck. Any ideas?

[hulk:/Library/Application Support/BOINC Data] zombie% ls -la

total 17720

drwxrwxr-x 32 boinc_ma boinc_ma 1088 May 22 09:50 .

drwxrwxr-x 20 root admin 680 May 12 15:17 ..

-rw-rw-r-- 1 boinc_ma boinc_ma 12292 May 14 16:49 .DS_Store

-rw-rw-r-- 1 boinc_ma boinc_ma 2097 May 22 08:09 account_setiathome.berkeley.edu.xml

-rw-rw-r-- 1 boinc_ma boinc_ma 13959 May 18 07:19 all_projects_list.xml

-rw-rw-r-- 1 boinc_ma boinc_ma 238100 Apr 26 02:24 ca-bundle.crt

-rw-rw-r-- 1 boinc_ma boinc_ma 1622746 May 22 09:50 client_state.xml

-rw-rw-r-- 1 boinc_ma boinc_ma 1622746 May 22 09:49 client_state_prev.xml

-rw-rw-r-- 1 boinc_ma boinc_ma 260 May 17 14:42 get_project_config.xml

-rw-rw-r-- 1 boinc_ma boinc_ma 2037 May 21 12:16 global_prefs.xml

-rw-rw---- 1 boinc_ma boinc_ma 32 May 12 15:18 gui_rpc_auth.cfg

-rw-rw-r-- 1 boinc_ma boinc_ma 14701 May 18 07:25 job_log_abcbeta.math.leidenuniv.nl.txt

-rw-rw-r-- 1 boinc_ma boinc_ma 186 May 14 09:44 job_log_boinc.bakerlab.org_rosetta.txt

-rw-rw-r-- 1 boinc_ma boinc_ma 8133 May 18 08:23 job_log_dist.ist.tugraz.at_cape5.txt

-rw-rw-r-- 1 boinc_ma boinc_ma 141525 May 22 09:45 job_log_setiathome.berkeley.edu.txt

dr-xr-x--- 38 boinc_ma boinc_ma 1292 May 8 23:25 locale

-rw-rw-r-- 1 boinc_ma boinc_ma 0 May 12 15:18 lockfile

-rw-rw-r-- 1 boinc_ma boinc_ma 139 May 17 14:42 lookup_account.xml

-rw-rw-r-- 1 boinc_ma boinc_ma 5964 May 22 09:45 lookup_website.html

-rw-rw-r-- 1 boinc_ma boinc_ma 69 May 18 04:49 master_setiathome.berkeley.edu.xml

drwxrwxr-x 4 boinc_ma boinc_ma 136 May 18 08:25 projects

-rw-rw-r-- 1 boinc_ma boinc_ma 5395 May 22 08:47 sched_reply_setiathome.berkeley.edu.xml

-rw-rw-r-- 1 boinc_ma boinc_ma 249360 May 22 08:47 sched_request_setiathome.berkeley.edu.xml

drwxrwxr-x 19 boinc_ma boinc_ma 646 May 22 08:16 slots

-rw-rw-r-- 1 boinc_ma boinc_ma 3723 May 22 08:48 statistics_setiathome.berkeley.edu.xml

-rw-rw-r-- 1 boinc_ma boinc_ma 0 May 12 15:18 stderrdae.txt

-rw-rw-r-- 1 boinc_ma boinc_ma 2180603 May 22 08:08 stderrgui.txt

-rw-rw-r-- 1 boinc_ma boinc_ma 2097163 May 21 07:43 stdoutdae.old

-rw-rw-r-- 1 boinc_ma boinc_ma 781017 May 22 09:47 stdoutdae.txt

-rw-rw-r-- 1 boinc_ma boinc_ma 268 May 22 06:23 stdoutgui.txt

dr-xr-x--- 4 boinc_ma boinc_ma 136 May 18 08:05 switcher

-rw-rw-r-- 1 boinc_ma boinc_ma 4862 May 22 08:08 time_stats_log

Change History (7)

comment:1 Changed 17 years ago by Ageless

Reported to Charlie Fenton. A fix was included for 5.9.12 by David Anderson.

comment:2 Changed 17 years ago by Ageless

zombie67 is testing 5.9.12 now.

It doesn't look like the fix worked...

But now I am beginning to think there are two different problems, maybe not related.

1) BOINC periodically locking up for about a minute at a time. Haven't seen this happen with 5.9.12 yet. But I have only been running it for a little while.

2) "Can't rename client_state_next.xml to client_state.xml"

Wed May 23 18:50:43 2007Wed May 23 18:50:43 2007Wed May 23 18:50:43 2007Wed May 23 18:50:43 2007
Starting BOINC client version 5.9.12 for i686-apple-darwin
log flags: task, file_xfer, sched_ops
Libraries: libcurl/7.16.1 OpenSSL/0.9.7l zlib/1.2.3
Data directory: /Library/Application? Support/BOINC Data

Wed May 23 18:50:43 2007|SETI@home|Found app_info.xml; using anonymous platform

Wed May 23 18:50:44 2007Wed May 23 18:50:44 2007Wed May 23 18:50:44 2007Wed May 23 18:50:44 2007Wed May 23 18:50:44 2007
Processor: 8 GenuineIntel? Intel(R) Xeon(R) CPU X5365 @ 3.00GHz [x86 Family 6 Model 15 Stepping 7]
Processor features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM SSE3 MON DSCPL VMX EST TM2 MNI CX16 TPR
Memory: 4.00 GB physical, 628.77 GB virtual
Disk: 698.32 GB total, 628.52 GB free
Version change (5.9.11 -> 5.9.12)

Wed May 23 18:50:44 2007|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 3360245; location: work; project prefs: default

Wed May 23 18:50:44 2007Wed May 23 18:50:44 2007Wed May 23 18:50:44 2007Wed May 23 18:50:44 2007Wed May 23 18:50:44 2007Wed May 23 18:50:44 2007Wed May 23 18:50:44 2007Wed May 23 18:51:45 2007Wed May 23 18:51:45 2007Wed May 23 18:51:45 2007Wed May 23 18:51:45 2007
General prefs: from http://www.worldcommunitygrid.org/ (last modified 2007-05-20 21:24:06)
Host location: work
General prefs: using separate prefs for work
Preferences limit memory usage when active to 4055.04MB
Preferences limit memory usage when idle to 4055.04MB
Preferences limit disk usage to 93.13GB
Running CPU benchmarks
Benchmark results:
Number of CPUs: 8
2434 floating point MIPS (Whetstone) per CPU
6777 integer MIPS (Dhrystone) per CPU

Wed May 23 18:51:46 2007|SETI@home|Restarting task 16ja05ab.25838.11154.586070.3.134_2 using setiathome_enhanced version 513 Wed May 23 18:51:46 2007|SETI@home|Restarting task 18mr05aa.11342.17728.990892.3.112_0 using setiathome_enhanced version 513 Wed May 23 18:51:46 2007|SETI@home|Restarting task 27fe05aa.20439.24976.884652.3.1_0 using setiathome_enhanced version 513 Wed May 23 18:51:46 2007|SETI@home|Restarting task 27fe05aa.20439.22530.117328.3.32_0 using setiathome_enhanced version 513 Wed May 23 18:51:46 2007|SETI@home|Restarting task 27fe05aa.20439.24976.884652.3.132_1 using setiathome_enhanced version 513 Wed May 23 18:51:46 2007|SETI@home|Restarting task 27fe05aa.20439.24976.884652.3.108_0 using setiathome_enhanced version 513 Wed May 23 18:51:46 2007|SETI@home|Restarting task 27fe05aa.20439.24976.884652.3.109_0 using setiathome_enhanced version 513 Wed May 23 18:51:46 2007|SETI@home|Restarting task 27fe05aa.20439.24976.884652.3.238_0 using setiathome_enhanced version 513 Wed May 23 18:52:04 2007|SETI@home|Sending scheduler request: Requested by user Wed May 23 18:52:04 2007|SETI@home|Reporting 7 tasks Wed May 23 18:52:25 2007|SETI@home|Scheduler RPC succeeded [server version 509] Wed May 23 18:52:25 2007|SETI@home|Deferring communication for 11 sec Wed May 23 18:52:25 2007|SETI@home|Reason: requested by project Wed May 23 19:04:36 2007|SETI@home|Computation for task 16ja05ab.25838.11154.586070.3.134_2 finished Wed May 23 19:04:36 2007|SETI@home|Starting 27fe05aa.20439.24976.884652.3.233_0 Wed May 23 19:04:37 2007|SETI@home|Starting task 27fe05aa.20439.24976.884652.3.233_0 using setiathome_enhanced version 513 Wed May 23 19:04:39 2007|SETI@home|[file_xfer] Started upload of file 16ja05ab.25838.11154.586070.3.134_2_0 Wed May 23 19:04:41 2007|SETI@home|[file_xfer] Finished upload of file 16ja05ab.25838.11154.586070.3.134_2_0 Wed May 23 19:04:41 2007|SETI@home|[file_xfer] Throughput 29322 bytes/sec Wed May 23 19:08:42 2007|SETI@home|Sending scheduler request: Requested by user Wed May 23 19:08:42 2007|SETI@home|Reporting 1 tasks Wed May 23 19:09:02 2007|SETI@home|Scheduler RPC succeeded [server version 509] Wed May 23 19:09:02 2007|SETI@home|Deferring communication for 11 sec Wed May 23 19:09:02 2007|SETI@home|Reason: requested by project Wed May 23 19:14:18 2007|SETI@home|Computation for task 18mr05aa.11342.17728.990892.3.112_0 finished Wed May 23 19:14:18 2007|SETI@home|Starting 27fe05aa.20439.24976.884652.3.244_2 Wed May 23 19:14:18 2007|SETI@home|Starting task 27fe05aa.20439.24976.884652.3.244_2 using setiathome_enhanced version 513 Wed May 23 19:14:20 2007|SETI@home|[file_xfer] Started upload of file 18mr05aa.11342.17728.990892.3.112_0_0 Wed May 23 19:14:23 2007|SETI@home|[file_xfer] Finished upload of file 18mr05aa.11342.17728.990892.3.112_0_0 Wed May 23 19:14:23 2007|SETI@home|[file_xfer] Throughput 36473 bytes/sec

Wed May 23 19:17:58 2007Wed May 23 19:17:58 2007
Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
[error] Couldn't write state file: system rename

Wed May 23 19:27:51 2007|SETI@home|Computation for task 27fe05aa.20439.24976.884652.3.1_0 finished Wed May 23 19:27:51 2007|SETI@home|Starting 16ja05ab.25838.15234.517322.3.89_1 Wed May 23 19:27:51 2007|SETI@home|Starting task 16ja05ab.25838.15234.517322.3.89_1 using setiathome_enhanced version 513 Wed May 23 19:27:53 2007|SETI@home|[file_xfer] Started upload of file 27fe05aa.20439.24976.884652.3.1_0_0 Wed May 23 19:27:57 2007|SETI@home|[file_xfer] Finished upload of file 27fe05aa.20439.24976.884652.3.1_0_0 Wed May 23 19:27:57 2007|SETI@home|[file_xfer] Throughput 7808 bytes/sec

Wed May 23 19:31:01 2007Wed May 23 19:31:01 2007
Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
[error] Couldn't write state file: system rename

comment:3 Changed 17 years ago by davea

Resolution: fixed
Status: newclosed

Should be fixed in 5.9.12. -David

comment:4 Changed 17 years ago by Ageless

Resolution: fixed
Status: closedreopened

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

AdrianX - WinXP, 5.8.15, reports:

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]

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.

comment:5 Changed 17 years ago by Ageless

Summary: Macintosh: Error: Can't rename client_state_next.xmlCan't rename current state file to previous state file

comment:6 Changed 17 years ago by davea

Owner: changed from davea to charlief
Status: reopenednew

comment:8 Changed 15 years ago by charlief

Resolution: fixed
Status: newclosed

This message has appeared from time to time but can never be reproduced. As noted by Ageless above, it does no harm because it usually works on a retry, and even if all the retries fail, it will usually work the next time the state file is updated. The only real problem was that it unnecessarily alarmed users. So I made the following change for version 6.1.10 to fix that:

Charlie Mar 10 2008

  • Client: Rework write_state_file logic to always retry if there is an

error writing or renaming the state file, and to show warning messages Can't rename / Can't write state file only if it failed all retries or if the state_debug log flag is set. These messages have appeared from time to time and worry users, but they never seemed to signal any real problems, probably because the subsequent retry succeeded.

I also deleted the last entry, which was SPAM.

Note: See TracTickets for help on using tickets.