| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: Africa Rainfall Project
Thread: Errors |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
One of my linux hosts received several resends so I took a look at them. The all had the same error. Just trowing this out in case it helps the techs.
----------------------------------------Result Log Result Name: ARP1_ 0001224_ 000_ 0-- <core_client_version>7.9.3</core_client_version> <![CDATA[ <message> finish file present too long</message> <stderr_txt> INFO: Initializing INFO: No state to restore. Start from the beginning. Starting WRFMain [22:45:47] INFO: Checkpoint taken at 2018-07-01_06:00:00 [01:29:17] INFO: Checkpoint taken at 2018-07-01_12:00:00 [04:41:25] INFO: Checkpoint taken at 2018-07-01_18:00:00 [07:39:29] INFO: Checkpoint taken at 2018-07-02_00:00:00 [09:59:24] INFO: Checkpoint taken at 2018-07-02_06:00:00 [13:32:06] INFO: Checkpoint taken at 2018-07-02_12:00:00 [16:36:36] INFO: Checkpoint taken at 2018-07-02_18:00:00 [19:38:04] INFO: Checkpoint taken at 2018-07-03_00:00:00 INFO: Simulation complete compressing output. 19:41:03 (32242): called boinc_finish(0) INFO: Initializing INFO: Simulation complete compressing output. </stderr_txt> ]]> And they all came from the same O/S. No way of telling if they all came from the same host. Linux Mint 19.2 Tina [4.15.0-66-generic|libc 2.27 (Ubuntu GLIBC 2.27-3ubuntu1)]
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
  |
||
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1403 Status: Offline Project Badges:
|
This is a very old issue of the BOINC-client caused by
- heavy loaded system - BOINC running with low priority - 7.9.3 is an older BOINC version, where it's not solved. When the application is ready boinc's finish file is written. When the app is still alive after 10 seconds the process is killed, although the science was ready :( In newer BOINC versions this timeout is increased to 5 minutes. |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges:
|
Is there a way to increase the timeout in older versions?
----------------------------------------
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
|
||
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1403 Status: Offline Project Badges:
|
Is there a way to increase the timeout in older versions? No, it is hard-coded. |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges:
|
Is there a way to increase the timeout in older versions? No, it is hard-coded. Thought so but was hoping there might be a hack. Since my linux server is only online for betas and new projects and I haven't had any issues with the APR1 WUs I'll just let it be for now. Thanks
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
|
||
|
|
|