Message boards : BOINC client : exited with zero status but no 'finished'
Message board moderation
Author | Message |
---|---|
Send message Joined: 27 Apr 06 Posts: 1 |
Hi, I"m using boinc 5.2.13 on i686 Slackware Linux machine. I tried to reset project, delete folder, but same message always come back : 2006-04-27 13:35:03 [---] Starting BOINC client version 5.2.13 for i686-pc-linux-gnu 2006-04-27 13:35:03 [---] libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3 2006-04-27 13:35:03 [---] Data directory: /home/boinc/BOINC 2006-04-27 13:35:03 [---] Processor: 1 GenuineIntel Pentium II (Deschutes) 2006-04-27 13:35:03 [---] Memory: 249.87 MB physical, 133.31 MB virtual 2006-04-27 13:35:03 [---] Disk: 3.64 GB total, 1.53 GB free 2006-04-27 13:35:03 [World Community Grid] Computer ID: 36548; location: ; project prefs: default 2006-04-27 13:35:03 [---] General prefs: from World Community Grid (last modified 1970-01-01 01:00:01) 2006-04-27 13:35:03 [---] General prefs: using your defaults 2006-04-27 13:35:03 [---] Remote control not allowed; using loopback address 2006-04-27 13:35:03 [World Community Grid] File wcg_faah_autodock_5.09_i686-pc-linux-gnu exists already, skipping download 2006-04-27 13:35:03 [World Community Grid] Started download of faah0447_d009cb796_x1hpv_01_faah0447_d009cb796_x1hpv_01.dpf 2006-04-27 13:35:03 [World Community Grid] Started download of faah0447_d009cb796_x1hpv_01_d009cb796_x1hpv_01.gpf 2006-04-27 13:35:06 [World Community Grid] Finished download of faah0447_d009cb796_x1hpv_01_faah0447_d009cb796_x1hpv_01.dpf 2006-04-27 13:35:06 [World Community Grid] Throughput 3056 bytes/sec 2006-04-27 13:35:06 [World Community Grid] Finished download of faah0447_d009cb796_x1hpv_01_d009cb796_x1hpv_01.gpf 2006-04-27 13:35:06 [World Community Grid] Throughput 1142 bytes/sec 2006-04-27 13:35:07 [---] request_reschedule_cpus: files downloaded 2006-04-27 13:35:07 [World Community Grid] Starting result faah0447_d009cb796_x1hpv_01_2 using faah version 509 2006-04-27 13:35:08 [World Community Grid] Result faah0447_d009cb796_x1hpv_01_2 exited with zero status but no 'finished' file 2006-04-27 13:35:08 [World Community Grid] If this happens repeatedly you may need to reset the project. 2006-04-27 13:35:08 [---] request_reschedule_cpus: process exited 2006-04-27 13:35:08 [World Community Grid] Restarting result faah0447_d009cb796_x1hpv_01_2 using faah version 509 2006-04-27 13:35:09 [World Community Grid] Result faah0447_d009cb796_x1hpv_01_2 exited with zero status but no 'finished' file 2006-04-27 13:35:09 [World Community Grid] If this happens repeatedly you may need to reset the project. 2006-04-27 13:35:09 [---] request_reschedule_cpus: process exited 2006-04-27 13:35:09 [World Community Grid] Restarting result faah0447_d009cb796_x1hpv_01_2 using faah version 509 2006-04-27 13:35:11 [World Community Grid] Result faah0447_d009cb796_x1hpv_01_2 exited with zero status but no 'finished' file 2006-04-27 13:35:11 [World Community Grid] If this happens repeatedly you may need to reset the project. 2006-04-27 13:35:11 [---] request_reschedule_cpus: process exited 2006-04-27 13:35:11 [World Community Grid] Restarting result faah0447_d009cb796_x1hpv_01_2 using faah version 509 2006-04-27 13:35:13 [World Community Grid] Result faah0447_d009cb796_x1hpv_01_2 exited with zero status but no 'finished' file 2006-04-27 13:35:13 [World Community Grid] If this happens repeatedly you may need to reset the project. 2006-04-27 13:35:13 [---] request_reschedule_cpus: process exited 2006-04-27 13:35:13 [World Community Grid] Restarting result faah0447_d009cb796_x1hpv_01_2 using faah version 509 2006-04-27 13:35:14 [World Community Grid] Result faah0447_d009cb796_x1hpv_01_2 exited with zero status but no 'finished' file 2006-04-27 13:35:14 [World Community Grid] If this happens repeatedly you may need to reset the project. 2006-04-27 13:35:14 [---] request_reschedule_cpus: process exited I also tried to find solution on Google x_x Any solution for this ? Thanks |
Send message Joined: 29 Aug 05 Posts: 15581 |
|
Send message Joined: 8 Jan 06 Posts: 448 |
Here is the Boinc Wiki link for link Result '(result)' exited with zero status but no 'finished' file The few times I have had this message it was cause by another program (a P2P in my case) locking up the CPU for a short time, causing the Boinc to time out on its communication to the client software. The WU completed and reported properly. Boinc V 7.4.36 Win7 i5 3.33G 4GB NVidia 470 |
Send message Joined: 16 Apr 06 Posts: 386 |
The most common cause I've found on CPDN is the windows time sync. Doesn't do it on my machine, but many people on the forums experience it when Windows does it's automatic sync (or if they manually request a time sync). |
Send message Joined: 13 Aug 06 Posts: 8 |
I have a Dual 1 GHz PowerPC G4 with 1GB SDRAM and am running Mac OS X 10.4.7. The BOINC client is v. 5.4.9, and projects are SETI@Home, Einstein@Home, World Community Grid, and SZTAKI Desktop Grid. I have been having the same trouble, but with exits almost every hour. shortly before exiting with zero status but no 'finished', we get the following error messages: Sun 13 Aug 11:43:27 2006 Can't rename state file: Error -1 Sun 13 Aug 11:43:27 2006 Couldn't write state file: system rename so the cause is something else locking up the state file. In checking the state files, I note that something is changing them to read only for the group (admin), and even if I change group status to 'read & write', it gets changed back 30 sec later. Interestingly, the BOINC Client is running in group 'wheel'. The stderr message is "client exit because of no heartbeat". I haven't noticed it as a problem until upgrade to the latest version of OS X. The anti-virus software is Norton Antivirus 10.1.1 (002), but it shouldn't be interfering with the file system unless I do a complete check on the disk, which hasn't appened for a while. I have tried resetting projects, but it has made no difference. I have now isolated Spotlight from the BOINC data folder, which should keep it from periodically sampling files, and hope that this does the trick. I'll report back later if the problem goes away. Otherwise, there is some sort of access or timing problem between the OS and the BOINC Client. Dr George W Gerrity |
Send message Joined: 13 Aug 06 Posts: 8 |
I have a Dual 1 GHz PowerPC G4 with 1GB SDRAM and am running Mac OS X 10.4.7. The BOINC client is v. 5.4.9, and projects are SETI@Home, Einstein@Home, World Community Grid, and SZTAKI Desktop Grid. I have now reset all projects, reset all access rights to the BOINC Data folder to be owner 'system', group 'admin' with read and write for owner and group, read for others. I have reset the BOINC application to the same owner and group and access rights, except execute rights for all three classes of user: these seem to be the default rights for most applications, but BOINC originally had owner george (me) and group wheel. I have also rechecked that neither Norton Antivirus or Spotlight can access the BOINC Data folder. I rstarted the Boinc manager with the four projects mentioned above, and am still getting problems with heartbeat timeout after BOINC fails to rename the state file. This is obviously a BOINC synchronisation failure. It should be isolated, tracked down, and fixed for the next Mac OS X release. At the moment, it doesn't seem to be doing too much harm, since it happens less than 20 times per day, although sometimes the state file access failure occurs several times in a few minutes until access and update is achieved. Thereafter, it seems to run for about 20, 30, or 60 minutes and sometimes much longer before failing again. My concern arose because it seemed to be causing loss of computation, especially in SZTAKI Desktop Grid, but it now seems that the WU was making so little progress that it wasn't even benchmarking. The new WU is still taking about 3 days to complete, but there is progress in all four projects. George ------ Dr George W Gerrity |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.