41)
Questions and Answers :
Windows :
WorkUnit #6117234
(Message 32148)
Posted 12 Jan 2008 by ChrisD Post: I just noticed that this task on my BOINC-Manager had stopped counting elapsed CPU-Time at exactly 66.66% which is the time where data for Phase 2 is to be uploaded. Looking at the Message tab showed me that the task repeatedly sent trickle up messages. Each request was replied OK: Sceduler RPC Succeded [Server Ver 509] I suspended the task and counted 20 trickle up messages in my log sent in one minute. Looking in the WU database, it seems that my fellow crunchers also has problems with this task. Right now I will try to suspend network traffic and see if the task actually generates the result files and continues crunching. If not, I am afraid I have to trash this WU, sorry. Has anybody else seen this before? ChrisD |
42)
Questions and Answers :
Windows :
Exit code 22, what is that?
(Message 31879)
Posted 24 Dec 2007 by ChrisD Post: After 305,216.11 seconds computing my HadCM3 Coupled Model Experiment Optimised File I/O created 5 Dec 2007 12:42:43 UTC name: hadcm3iozn_cq5n_2000_80_155899668 just gave up and crashed with error code (0x16) - exit code 22 (0x16) ... last trickle: TS 129,600 at 252,519 seconds. for the tecnical mineded the result is #7028784. I just need to know if it was a hardware failure. My computer seems to run steady enough and is not o/c\'ed. ChrisD |
43)
Questions and Answers :
Windows :
Missing Work Units.
(Message 31682)
Posted 12 Dec 2007 by ChrisD Post:
Sure, here is the log from power on today until 17:45 UTC 12-12-2007 13:56:07||Starting BOINC client version 5.10.13 for windows_intelx86 12-12-2007 13:56:07||log flags: task, file_xfer, sched_ops 12-12-2007 13:56:07||Libraries: libcurl/7.16.1 OpenSSL/0.9.8e zlib/1.2.3 12-12-2007 13:56:07||Data directory: C:\\BOINC 12-12-2007 13:56:07||Processor: 2 AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 6400+ [x86 Family 15 Model 67 Stepping 3] 12-12-2007 13:56:07||Processor features: fpu tsc pae nx sse sse2 3dnow mmx 12-12-2007 13:56:07||Memory: 2.00 GB physical, 3.85 GB virtual 12-12-2007 13:56:07||Disk: 136.09 GB total, 38.07 GB free 12-12-2007 13:56:08|CPDN Seasonal Attribution Project|URL: http://attribution.cpdn.org/; Computer ID: 25018; location: (none); project prefs: default 12-12-2007 13:56:08|climateprediction.net|URL: http://climateprediction.net/; Computer ID: 767991; location: home; project prefs: default 12-12-2007 13:56:08|lhcathome|URL: http://lhcathome.cern.ch/lhcathome/; Computer ID: 9642356; location: home; project prefs: home 12-12-2007 13:56:08|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 4009089; location: home; project prefs: default 12-12-2007 13:56:08||General prefs: from SETI@home (last modified 2007-12-04 16:29:33) 12-12-2007 13:56:08||Host location: home 12-12-2007 13:56:08||General prefs: no separate prefs for home; using your defaults 12-12-2007 13:56:08||Preferences limit memory usage when active to 1433.24MB 12-12-2007 13:56:08||Preferences limit memory usage when idle to 1842.73MB 12-12-2007 13:56:08||Preferences limit disk usage to 28.76GB 12-12-2007 13:56:08||Suspending network activity - user request 12-12-2007 13:56:08|climateprediction.net|Restarting task hadsm3fub_0210_005908225_2 using hadsm3 version 506 12-12-2007 13:57:47||Resuming network activity 12-12-2007 13:57:48|CPDN Seasonal Attribution Project|Sending scheduler request: Requested by user 12-12-2007 13:57:48|CPDN Seasonal Attribution Project|(not requesting new work or reporting completed tasks) 12-12-2007 13:58:02||Project communication failed: attempting access to reference site 12-12-2007 13:58:03||Access to reference site succeeded - project servers may be temporarily down. 12-12-2007 13:58:03|CPDN Seasonal Attribution Project|Scheduler request failed: couldn\'t connect to server 12-12-2007 13:58:03|CPDN Seasonal Attribution Project|Deferring communication for 1 min 41 sec 12-12-2007 13:58:03|CPDN Seasonal Attribution Project|Reason: scheduler request failed 12-12-2007 13:58:08|climateprediction.net|Sending scheduler request: To send trickle-up message 12-12-2007 13:58:08|climateprediction.net|(not requesting new work or reporting completed tasks) 12-12-2007 13:58:58||General prefs: from SETI@home (last modified 2007-12-04 16:29:33) 12-12-2007 13:58:58||Host location: home 12-12-2007 13:58:58||General prefs: no separate prefs for home; using your defaults 12-12-2007 13:58:58||Reading preferences override file 12-12-2007 13:58:58||Preferences limit memory usage when active to 1023.74MB 12-12-2007 13:58:58||Preferences limit memory usage when idle to 1842.73MB 12-12-2007 13:58:58||Preferences limit disk usage to 9.31GB 12-12-2007 13:59:08|climateprediction.net|Scheduler request failed: HTTP internal server error 12-12-2007 13:59:08|climateprediction.net|Deferring communication for 1 min 0 sec 12-12-2007 13:59:08|climateprediction.net|Reason: scheduler request failed 12-12-2007 13:59:13|lhcathome|Sending scheduler request: To fetch work 12-12-2007 13:59:13|lhcathome|Requesting 116640 seconds of new work 12-12-2007 13:59:18|lhcathome|Scheduler RPC succeeded [server version 505] 12-12-2007 13:59:18|lhcathome|Deferring communication for 15 min 9 sec 12-12-2007 13:59:18|lhcathome|Reason: requested by project 12-12-2007 13:59:48|CPDN Seasonal Attribution Project|Sending scheduler request: Requested by user 12-12-2007 13:59:48|CPDN Seasonal Attribution Project|Requesting 116640 seconds of new work 12-12-2007 13:59:56||Project communication failed: attempting access to reference site 12-12-2007 13:59:58||Access to reference site succeeded - project servers may be temporarily down. 12-12-2007 13:59:58|CPDN Seasonal Attribution Project|Scheduler request failed: couldn\'t connect to server 12-12-2007 13:59:58|CPDN Seasonal Attribution Project|Deferring communication for 5 min 15 sec 12-12-2007 13:59:58|CPDN Seasonal Attribution Project|Reason: scheduler request failed 12-12-2007 14:00:08|climateprediction.net|Sending scheduler request: To send trickle-up message 12-12-2007 14:00:08|climateprediction.net|Requesting 116640 seconds of new work 12-12-2007 14:01:13|climateprediction.net|Scheduler request failed: HTTP internal server error 12-12-2007 14:01:13|climateprediction.net|Deferring communication for 1 min 0 sec 12-12-2007 14:01:13|climateprediction.net|Reason: scheduler request failed 12-12-2007 14:01:27||Running CPU benchmarks 12-12-2007 14:01:27||Suspending computation - running CPU benchmarks 12-12-2007 14:01:58||Benchmark results: 12-12-2007 14:01:58|| Number of CPUs: 2 12-12-2007 14:01:58|| 3119 floating point MIPS (Whetstone) per CPU 12-12-2007 14:01:58|| 5713 integer MIPS (Dhrystone) per CPU 12-12-2007 14:01:59||Resuming computation 12-12-2007 14:02:15|climateprediction.net|Sending scheduler request: To send trickle-up message 12-12-2007 14:02:15|climateprediction.net|Requesting 116640 seconds of new work 12-12-2007 14:02:37||Project communication failed: attempting access to reference site 12-12-2007 14:02:38||Access to reference site succeeded - project servers may be temporarily down. 12-12-2007 14:02:40|climateprediction.net|Scheduler request failed: couldn\'t connect to server 12-12-2007 14:02:40|climateprediction.net|Deferring communication for 1 min 0 sec 12-12-2007 14:02:40|climateprediction.net|Reason: scheduler request failed 12-12-2007 14:02:47||Suspending network activity - user request 12-12-2007 14:02:58||Resuming network activity 12-12-2007 14:03:43|climateprediction.net|Sending scheduler request: To send trickle-up message 12-12-2007 14:03:43|climateprediction.net|Requesting 116640 seconds of new work 12-12-2007 14:04:38|climateprediction.net|Scheduler request failed: HTTP internal server error 12-12-2007 14:04:38|climateprediction.net|Deferring communication for 1 min 0 sec 12-12-2007 14:04:38|climateprediction.net|Reason: scheduler request failed 12-12-2007 14:05:18|CPDN Seasonal Attribution Project|Sending scheduler request: Requested by user 12-12-2007 14:05:18|CPDN Seasonal Attribution Project|Requesting 116640 seconds of new work 12-12-2007 14:05:20||Project communication failed: attempting access to reference site 12-12-2007 14:05:21||Access to reference site succeeded - project servers may be temporarily down. 12-12-2007 14:05:23|CPDN Seasonal Attribution Project|Scheduler request failed: couldn\'t connect to server 12-12-2007 14:05:23|CPDN Seasonal Attribution Project|Deferring communication for 8 min 37 sec 12-12-2007 14:05:23|CPDN Seasonal Attribution Project|Reason: scheduler request failed 12-12-2007 14:05:38|climateprediction.net|Sending scheduler request: To send trickle-up message 12-12-2007 14:05:38|climateprediction.net|Requesting 116640 seconds of new work 12-12-2007 14:06:53|climateprediction.net|Scheduler request failed: HTTP internal server error 12-12-2007 14:06:53|climateprediction.net|Deferring communication for 1 min 9 sec 12-12-2007 14:06:53|climateprediction.net|Reason: scheduler request failed 12-12-2007 14:08:03|climateprediction.net|Sending scheduler request: To send trickle-up message 12-12-2007 14:08:03|climateprediction.net|Requesting 116640 seconds of new work 12-12-2007 14:08:58|climateprediction.net|Scheduler request failed: HTTP internal server error 12-12-2007 14:08:58|climateprediction.net|Deferring communication for 1 min 37 sec 12-12-2007 14:08:58|climateprediction.net|Reason: scheduler request failed 12-12-2007 14:10:38|climateprediction.net|Sending scheduler request: To send trickle-up message 12-12-2007 14:10:38|climateprediction.net|Requesting 116640 seconds of new work 12-12-2007 14:11:58|climateprediction.net|Scheduler request failed: HTTP internal server error 12-12-2007 14:11:58|climateprediction.net|Deferring communication for 7 min 29 sec 12-12-2007 14:11:58|climateprediction.net|Reason: scheduler request failed 12-12-2007 14:14:03|CPDN Seasonal Attribution Project|Sending scheduler request: Requested by user 12-12-2007 14:14:03|CPDN Seasonal Attribution Project|Requesting 116640 seconds of new work 12-12-2007 14:14:17||Project communication failed: attempting access to reference site 12-12-2007 14:14:19|CPDN Seasonal Attribution Project|Scheduler request failed: couldn\'t connect to server 12-12-2007 14:14:19|CPDN Seasonal Attribution Project|Deferring communication for 23 min 18 sec 12-12-2007 14:14:19|CPDN Seasonal Attribution Project|Reason: scheduler request failed 12-12-2007 14:14:20||Access to reference site succeeded - project servers may be temporarily down. 12-12-2007 14:14:29|lhcathome|Sending scheduler request: To fetch work 12-12-2007 14:14:29|lhcathome|Requesting 116640 seconds of new work 12-12-2007 14:14:34|lhcathome|Scheduler RPC succeeded [server version 505] 12-12-2007 14:14:34|lhcathome|Deferring communication for 15 min 9 sec 12-12-2007 14:14:34|lhcathome|Reason: requested by project 12-12-2007 14:19:29|climateprediction.net|Sending scheduler request: To send trickle-up message 12-12-2007 14:19:29|climateprediction.net|Requesting 116640 seconds of new work 12-12-2007 14:19:34|climateprediction.net|Scheduler RPC succeeded [server version 509] 12-12-2007 14:19:36|climateprediction.net|[file_xfer] Started download of file hadcm3iozn_cq5n_2000_80_155899668.zip 12-12-2007 14:19:36|climateprediction.net|[file_xfer] Started download of file SULPC_OXIDANTS_19_A2_1990.mod.gz 12-12-2007 14:19:37|climateprediction.net|[file_xfer] Finished download of file hadcm3iozn_cq5n_2000_80_155899668.zip 12-12-2007 14:19:37|climateprediction.net|[file_xfer] Throughput 41629 bytes/sec 12-12-2007 14:19:37|climateprediction.net|[file_xfer] Started download of file DMSNH3SO2A1B_19182082.mod.gz 12-12-2007 14:19:41|climateprediction.net|[file_xfer] Finished download of file DMSNH3SO2A1B_19182082.mod.gz 12-12-2007 14:19:41|climateprediction.net|[file_xfer] Throughput 78363 bytes/sec 12-12-2007 14:19:41|climateprediction.net|[file_xfer] Started download of file spec3a_lw_3_asol2c_hadcm3.gz 12-12-2007 14:19:43|climateprediction.net|[file_xfer] Finished download of file spec3a_lw_3_asol2c_hadcm3.gz 12-12-2007 14:19:43|climateprediction.net|[file_xfer] Throughput 37412 bytes/sec 12-12-2007 14:19:43|climateprediction.net|[file_xfer] Started download of file spec3a_sw_3_asol2b_hadcm3.gz 12-12-2007 14:19:44|climateprediction.net|[file_xfer] Finished download of file spec3a_sw_3_asol2b_hadcm3.gz 12-12-2007 14:19:44|climateprediction.net|[file_xfer] Throughput 29583 bytes/sec 12-12-2007 14:19:44|climateprediction.net|[file_xfer] Started download of file solar_v01.gz 12-12-2007 14:19:45|climateprediction.net|[file_xfer] Finished download of file solar_v01.gz 12-12-2007 14:19:45|climateprediction.net|[file_xfer] Throughput 4134 bytes/sec 12-12-2007 14:19:45|climateprediction.net|[file_xfer] Started download of file ozone_hadcm3_1919_2082.mod.gz 12-12-2007 14:19:46|climateprediction.net|[file_xfer] Finished download of file SULPC_OXIDANTS_19_A2_1990.mod.gz 12-12-2007 14:19:46|climateprediction.net|[file_xfer] Throughput 127227 bytes/sec 12-12-2007 14:19:46|climateprediction.net|[file_xfer] Started download of file DMSNH3SO2A1B_19182082.gz 12-12-2007 14:19:47|climateprediction.net|[file_xfer] Finished download of file ozone_hadcm3_1919_2082.mod.gz 12-12-2007 14:19:47|climateprediction.net|[file_xfer] Throughput 68960 bytes/sec 12-12-2007 14:19:47|climateprediction.net|[file_xfer] Started download of file NAT_VOLC.gz 12-12-2007 14:19:48|climateprediction.net|[file_xfer] Finished download of file NAT_VOLC.gz 12-12-2007 14:19:48|climateprediction.net|[file_xfer] Throughput 13730 bytes/sec 12-12-2007 14:19:48|climateprediction.net|[file_xfer] Started download of file hh48hdck_0108_nickfluxcorr.anc.gz 12-12-2007 14:19:49|climateprediction.net|[file_xfer] Finished download of file DMSNH3SO2A1B_19182082.gz 12-12-2007 14:19:49|climateprediction.net|[file_xfer] Throughput 59071 bytes/sec 12-12-2007 14:19:49|climateprediction.net|[file_xfer] Started download of file atmos_ckau_446_2000.gz 12-12-2007 14:19:51|climateprediction.net|[file_xfer] Finished download of file hh48hdck_0108_nickfluxcorr.anc.gz 12-12-2007 14:19:51|climateprediction.net|[file_xfer] Throughput 158587 bytes/sec 12-12-2007 14:19:51|climateprediction.net|[file_xfer] Started download of file ozone_hadcm3_1919_2082.gz 12-12-2007 14:19:56|climateprediction.net|[file_xfer] Finished download of file ozone_hadcm3_1919_2082.gz 12-12-2007 14:19:56|climateprediction.net|[file_xfer] Throughput 173924 bytes/sec 12-12-2007 14:19:56|climateprediction.net|[file_xfer] Started download of file ghg_a1b.gz 12-12-2007 14:19:57|climateprediction.net|[file_xfer] Finished download of file ghg_a1b.gz 12-12-2007 14:19:57|climateprediction.net|[file_xfer] Throughput 10299 bytes/sec 12-12-2007 14:19:57|climateprediction.net|[file_xfer] Started download of file SULPC_OXIDANTS_19_A2_1990.gz 12-12-2007 14:19:59|climateprediction.net|[file_xfer] Finished download of file SULPC_OXIDANTS_19_A2_1990.gz 12-12-2007 14:19:59|climateprediction.net|[file_xfer] Throughput 55303 bytes/sec 12-12-2007 14:19:59|climateprediction.net|[file_xfer] Started download of file 1002_flux_corr.anc.gz 12-12-2007 14:20:08|climateprediction.net|[file_xfer] Finished download of file 1002_flux_corr.anc.gz 12-12-2007 14:20:08|climateprediction.net|[file_xfer] Throughput 61502 bytes/sec 12-12-2007 14:20:08|climateprediction.net|[file_xfer] Started download of file volc_v01.gz 12-12-2007 14:20:09|climateprediction.net|[file_xfer] Finished download of file volc_v01.gz 12-12-2007 14:20:09|climateprediction.net|[file_xfer] Throughput 22396 bytes/sec 12-12-2007 14:20:09|climateprediction.net|[file_xfer] Started download of file ocean_ckau_446_2000.gz 12-12-2007 14:20:36|climateprediction.net|[file_xfer] Finished download of file ocean_ckau_446_2000.gz 12-12-2007 14:20:36|climateprediction.net|[file_xfer] Throughput 119705 bytes/sec 12-12-2007 14:21:00|climateprediction.net|[file_xfer] Finished download of file atmos_ckau_446_2000.gz 12-12-2007 14:21:00|climateprediction.net|[file_xfer] Throughput 124625 bytes/sec 12-12-2007 14:21:01|climateprediction.net|Starting hadcm3iozn_cq5n_2000_80_155899668_1 12-12-2007 14:21:01|climateprediction.net|Starting task hadcm3iozn_cq5n_2000_80_155899668_1 using hadcm3i version 544 12-12-2007 14:29:47|lhcathome|Sending scheduler request: To fetch work 12-12-2007 14:29:47|lhcathome|Requesting 11156 seconds of new work 12-12-2007 14:29:52|lhcathome|Scheduler RPC succeeded [server version 505] 12-12-2007 14:29:52|lhcathome|Deferring communication for 15 min 9 sec 12-12-2007 14:29:52|lhcathome|Reason: requested by project 12-12-2007 14:37:38|CPDN Seasonal Attribution Project|Sending scheduler request: Requested by user 12-12-2007 14:37:38|CPDN Seasonal Attribution Project|Requesting 11181 seconds of new work 12-12-2007 14:37:46||Project communication failed: attempting access to reference site 12-12-2007 14:37:48||Access to reference site succeeded - project servers may be temporarily down. 12-12-2007 14:37:48|CPDN Seasonal Attribution Project|Scheduler request failed: couldn\'t connect to server 12-12-2007 14:37:48|CPDN Seasonal Attribution Project|Deferring communication for 12 min 41 sec 12-12-2007 14:37:48|CPDN Seasonal Attribution Project|Reason: scheduler request failed 12-12-2007 14:45:03|lhcathome|Sending scheduler request: To fetch work 12-12-2007 14:45:03|lhcathome|Requesting 11205 seconds of new work 12-12-2007 14:45:08|lhcathome|Scheduler RPC succeeded [server version 505] 12-12-2007 14:45:08|lhcathome|Deferring communication for 15 min 9 sec 12-12-2007 14:45:08|lhcathome|Reason: requested by project 12-12-2007 14:50:33|CPDN Seasonal Attribution Project|Sending scheduler request: Requested by user 12-12-2007 14:50:33|CPDN Seasonal Attribution Project|Requesting 11223 seconds of new work 12-12-2007 14:50:41||Project communication failed: attempting access to reference site 12-12-2007 14:50:43||Access to reference site succeeded - project servers may be temporarily down. 12-12-2007 14:50:43|CPDN Seasonal Attribution Project|Scheduler request failed: couldn\'t connect to server 12-12-2007 14:50:43|CPDN Seasonal Attribution Project|Deferring communication for 35 min 54 sec 12-12-2007 14:50:43|CPDN Seasonal Attribution Project|Reason: scheduler request failed 12-12-2007 15:00:18|lhcathome|Sending scheduler request: To fetch work 12-12-2007 15:00:18|lhcathome|Requesting 11255 seconds of new work 12-12-2007 15:00:23|lhcathome|Scheduler RPC succeeded [server version 505] 12-12-2007 15:00:23|lhcathome|Deferring communication for 15 min 9 sec 12-12-2007 15:00:23|lhcathome|Reason: requested by project 12-12-2007 15:15:33|lhcathome|Sending scheduler request: To fetch work 12-12-2007 15:15:33|lhcathome|Requesting 11305 seconds of new work 12-12-2007 15:15:38|lhcathome|Scheduler RPC succeeded [server version 505] 12-12-2007 15:15:38|lhcathome|Deferring communication for 15 min 9 sec 12-12-2007 15:15:38|lhcathome|Reason: requested by project 12-12-2007 15:26:38|CPDN Seasonal Attribution Project|Sending scheduler request: Requested by user 12-12-2007 15:26:38|CPDN Seasonal Attribution Project|Requesting 11339 seconds of new work 12-12-2007 15:26:43|CPDN Seasonal Attribution Project|Scheduler RPC succeeded [server version 505] 12-12-2007 15:26:43|CPDN Seasonal Attribution Project|Deferring communication for 1 min 0 sec 12-12-2007 15:26:43|CPDN Seasonal Attribution Project|Reason: no work from project 12-12-2007 15:27:43|CPDN Seasonal Attribution Project|Fetching scheduler list 12-12-2007 15:27:48|CPDN Seasonal Attribution Project|Master file download succeeded 12-12-2007 15:27:53|CPDN Seasonal Attribution Project|Sending scheduler request: To fetch work 12-12-2007 15:27:53|CPDN Seasonal Attribution Project|Requesting 11343 seconds of new work 12-12-2007 15:27:58|CPDN Seasonal Attribution Project|Scheduler RPC succeeded [server version 505] 12-12-2007 15:27:58|CPDN Seasonal Attribution Project|Deferring communication for 1 min 0 sec 12-12-2007 15:27:58|CPDN Seasonal Attribution Project|Reason: no work from project 12-12-2007 15:28:58|CPDN Seasonal Attribution Project|Sending scheduler request: To fetch work 12-12-2007 15:28:58|CPDN Seasonal Attribution Project|Requesting 11347 seconds of new work 12-12-2007 15:29:03|CPDN Seasonal Attribution Project|Scheduler RPC succeeded [server version 505] 12-12-2007 15:29:03|CPDN Seasonal Attribution Project|Deferring communication for 1 min 0 sec 12-12-2007 15:29:03|CPDN Seasonal Attribution Project|Reason: no work from project 12-12-2007 15:30:03|CPDN Seasonal Attribution Project|Sending scheduler request: To fetch work 12-12-2007 15:30:03|CPDN Seasonal Attribution Project|Requesting 11350 seconds of new work 12-12-2007 15:30:08|CPDN Seasonal Attribution Project|Scheduler RPC succeeded [server version 505] 12-12-2007 15:30:08|CPDN Seasonal Attribution Project|Deferring communication for 1 min 0 sec 12-12-2007 15:30:08|CPDN Seasonal Attribution Project|Reason: no work from project 12-12-2007 15:30:48|lhcathome|Sending scheduler request: To fetch work 12-12-2007 15:30:48|lhcathome|Requesting 11352 seconds of new work 12-12-2007 15:30:53|lhcathome|Scheduler RPC succeeded [server version 505] 12-12-2007 15:30:53|lhcathome|Deferring communication for 15 min 9 sec 12-12-2007 15:30:53|lhcathome|Reason: requested by project 12-12-2007 15:31:08|CPDN Seasonal Attribution Project|Sending scheduler request: To fetch work 12-12-2007 15:31:08|CPDN Seasonal Attribution Project|Requesting 11353 seconds of new work 12-12-2007 15:31:13|CPDN Seasonal Attribution Project|Scheduler RPC succeeded [server version 505] 12-12-2007 15:31:13|CPDN Seasonal Attribution Project|Deferring communication for 1 min 0 sec 12-12-2007 15:31:13|CPDN Seasonal Attribution Project|Reason: no work from project 12-12-2007 15:32:13|CPDN Seasonal Attribution Project|Sending scheduler request: To fetch work 12-12-2007 15:32:13|CPDN Seasonal Attribution Project|Requesting 11357 seconds of new work 12-12-2007 15:32:18|CPDN Seasonal Attribution Project|Scheduler RPC succeeded [server version 505] 12-12-2007 15:32:18|CPDN Seasonal Attribution Project|Deferring communication for 1 min 16 sec 12-12-2007 15:32:18|CPDN Seasonal Attribution Project|Reason: no work from project 12-12-2007 15:33:38|CPDN Seasonal Attribution Project|Sending scheduler request: To fetch work 12-12-2007 15:33:38|CPDN Seasonal Attribution Project|Requesting 11361 seconds of new work 12-12-2007 15:33:43|CPDN Seasonal Attribution Project|Scheduler RPC succeeded [server version 505] 12-12-2007 15:33:43|CPDN Seasonal Attribution Project|Deferring communication for 6 min 34 sec 12-12-2007 15:33:43|CPDN Seasonal Attribution Project|Reason: no work from project 12-12-2007 15:40:19|CPDN Seasonal Attribution Project|Sending scheduler request: To fetch work 12-12-2007 15:40:19|CPDN Seasonal Attribution Project|Requesting 11383 seconds of new work 12-12-2007 15:40:24|CPDN Seasonal Attribution Project|Scheduler RPC succeeded [server version 505] 12-12-2007 15:40:24|CPDN Seasonal Attribution Project|Deferring communication for 15 min 8 sec 12-12-2007 15:40:24|CPDN Seasonal Attribution Project|Reason: no work from project 12-12-2007 15:46:04|lhcathome|Sending scheduler request: To fetch work 12-12-2007 15:46:04|lhcathome|Requesting 11401 seconds of new work 12-12-2007 15:46:09|lhcathome|Scheduler RPC succeeded [server version 505] 12-12-2007 15:46:09|lhcathome|Deferring communication for 15 min 9 sec 12-12-2007 15:46:09|lhcathome|Reason: requested by project 12-12-2007 15:55:34|CPDN Seasonal Attribution Project|Sending scheduler request: To fetch work 12-12-2007 15:55:34|CPDN Seasonal Attribution Project|Requesting 11431 seconds of new work 12-12-2007 15:55:39|CPDN Seasonal Attribution Project|Scheduler RPC succeeded [server version 505] 12-12-2007 15:55:39|CPDN Seasonal Attribution Project|Deferring communication for 13 min 12 sec 12-12-2007 15:55:39|CPDN Seasonal Attribution Project|Reason: no work from project 12-12-2007 16:01:19|lhcathome|Sending scheduler request: To fetch work 12-12-2007 16:01:19|lhcathome|Requesting 11449 seconds of new work 12-12-2007 16:01:24|lhcathome|Scheduler RPC succeeded [server version 505] 12-12-2007 16:01:24|lhcathome|Deferring communication for 15 min 9 sec 12-12-2007 16:01:24|lhcathome|Reason: requested by project 12-12-2007 16:01:24|lhcathome|Deferring communication for 2 hr 7 min 42 sec 12-12-2007 16:01:24|lhcathome|Reason: no work from project 12-12-2007 16:08:54|CPDN Seasonal Attribution Project|Sending scheduler request: To fetch work 12-12-2007 16:08:54|CPDN Seasonal Attribution Project|Requesting 11474 seconds of new work 12-12-2007 16:08:59|CPDN Seasonal Attribution Project|Scheduler RPC succeeded [server version 505] 12-12-2007 16:08:59|CPDN Seasonal Attribution Project|Deferring communication for 1 hr 52 min 46 sec 12-12-2007 16:08:59|CPDN Seasonal Attribution Project|Reason: no work from project 12-12-2007 17:45:25|climateprediction.net|Sending scheduler request: To send trickle-up message 12-12-2007 17:45:25|climateprediction.net|(not requesting new work or reporting completed tasks) 12-12-2007 17:45:30|climateprediction.net|Scheduler RPC succeeded [server version 509] a little long, but feel free to copy the log and delete this msg. :) ChrisD |
44)
Questions and Answers :
Windows :
Missing Work Units.
(Message 31675)
Posted 12 Dec 2007 by ChrisD Post: Today I requested more work and got this WU hadcm3iozn_cq5n_2000_80_155899668_1 Result # 7028784 which my computer has started crunching. However looking at my account for computer# 767991 it shows that another 2 WU\'s have been sent: hadcm3iozn_cq5j_2000_80_155899664_4 Result # 7028755 and hadcm3iozn_cq5k_2000_80_155899665_0 Result # 7028759 These 2 WU\'s does not show on my Task List and my log does not show these WU\'s to have actually been transferred. If this fault has replicated to other users You may have a lot of non existant WU\'s distributed. To solve the problem, is there a way I can get the computer to actually send me the specific units? (It may take a while, but I\'ll crunch them if You pass them on to me. ChrisD |
45)
Questions and Answers :
Windows :
Trikles, where is my Trikles?
(Message 21575)
Posted 25 Mar 2006 by ChrisD Post: The official post from Carl is here about it. Post is dated 15-Dec-05. I missed that one. Thank You for Info. :) ChrisD |
46)
Questions and Answers :
Windows :
Trikles, where is my Trikles?
(Message 21550)
Posted 24 Mar 2006 by ChrisD Post: I have noticed some changes has been introduced to the result pages, and it seems that the list of Trickles has gone. If they are still there, please somebody, direct me to it. These are my \'centrallized\' table of progress, as well as watching that no machine starts slowing down. Please do not omit Trikles from the Computer Page. ChrisD |
47)
Questions and Answers :
Windows :
How to save BOINC CPDN results?
(Message 20353)
Posted 16 Feb 2006 by ChrisD Post:
Sure :) Thanks to Your info about this hidden ctrl + F1, I was able to change the timing for the memory to the 2-2-2-5, instead of the automatically selected 2.5-3-3-6. ChrisD |
48)
Questions and Answers :
Windows :
How to save BOINC CPDN results?
(Message 20310)
Posted 15 Feb 2006 by ChrisD Post: ChrisD, I run the FSB at 166 MHz only, and so does the memory. I am not sure the processor is stable at 200 MHz FSB. If this is the case, then I have to choose a x 10.5 multiplier which is slower than the normal 2167 MHz or OC at x 11. As CPDN is a long experiment I am not keen of risking OC to gain the last ounce. I might loose the whole basket.. Happy crunching ChrisD |
49)
Questions and Answers :
Windows :
How to save BOINC CPDN results?
(Message 20146)
Posted 12 Feb 2006 by ChrisD Post: I used to have that motherboard, but it was quite awhile ago. When in the BIOS main screen, hitting Ctrl and F1 at the same time should give you advanced options in the submenus. Does this give you some option for setting the memory timings? Ctrl + F1 option was unknown to me. I better study the manual one more time :) And: Sure, I am going to check that one out. :)
Sorry, just checked. You are right and my menory is the 3200XL. Seems that my memory failed me. ChrisD |
50)
Questions and Answers :
Windows :
How to save BOINC CPDN results?
(Message 20142)
Posted 12 Feb 2006 by ChrisD Post: Author said: My XP3200+ does about 3.2 s/TS. But how fast the 3000+ goes depends on whether its front side bus is 166 or 200 MHz, what type of motherboard you have, and what timings your memory is running at. If it\'s a 200 MHz front side bus 3000+ running on an NForce2 motherboard with dual channel memory, it\'s probably a little slow. If it\'s otherwise, it might be about right. My XP3000+ is a BARTON Core running 166 MHz FSB with one 256 Mb DDR Module. MB is a GigaByte GA7-VT600. Memory runs FSB+33MHz at 2.5-3-3-7. Memory is Corsair XMS3200LL and should run 2-2-2-5 at 200 MHz, but there is no BIOS options for memory timings other than I can make it run at 200 MHz. Setting memory speed to 166 MHz gives me the same timings. Seems that this MainBoard is no good when using LL RAM :( Thank for the FilZip hint. ChrisD |
51)
Questions and Answers :
Windows :
How to save BOINC CPDN results?
(Message 20139)
Posted 12 Feb 2006 by ChrisD Post: When crunching Classic CPDN THC-runs, my finished experiments were neatly packed up. Then I should be able to look at the experiments later using Martin\'s CPWiew or the Advanced Visualisation packet. I am now running BOINC, crunshing two Sulphur-runs. Reading the posts I get to understand that BOINC erases the data, once the completed run has been uploaded. Has anybody found a way to \'snip\' a copy, for the records (without trashing the results, that is :)). I have an idea of suspending network activity, before the Run is complete. When the run reports ready for upload, I will take a backup, and then alow the result to be uploaded. Is this a way that will work, or is there a better way? Another silly q. In order to look at one of my previous THC runs, I need to extract the whole result-dir. Doing this one file at a time takes forever. I know someone has made a Batch-file for this task. Could I be directed to it? Thanks Folks, sorry if these q. has been asked before, but I just ran out of luck searching through years of posts. One last Q. My Athlon XP3000+ takes 4,03 S/TS and my Athlon64 3500+ takes 2.67 S/TS. How does this compare? Happy Crunching. Chris D |
52)
Questions and Answers :
Windows :
Automatic Backup any good?
(Message 20047)
Posted 8 Feb 2006 by ChrisD Post: Oxford Uni has nothing to do with developing BOINC. Please Pardon me, but I may not have explained my problem correct. As I understand this, BOINC manages the flow of data between my machine and the servers running the various projects. Each project makes an application to do the actual math involved in that project. As I see it, the CPDN application, when restarted after the crash, could not find its Data files and therefore aborted the WU. This has nothing to do with BOINC. When the CPDN application gives up, BOINC faithfully and without delay, sends the required message issued by the CPDN app. reporting the crash and asks for replacement work. What I was asking for is a CPDN client a little more rigid. One that does not give up because the work-area is corrupt, but tries to revert to a known good state. I know it is already there: the files: restart.day restart.month and restart.year holds a restart point, but they are altered repeatedly by the client, and if the crash happens when one of these files are accessed, no salvage is possible unless these files are backed up somewhere safe. When listening to my Computer, data are updated several times/hour. Each time, a disk error will crash the WU. Backing files up once every 24 hours, will reduce the risk by a large factor. The CPDN Server does not state the number of crashed experiments, only the successful compled ones. However looking at the total model Years computed, there are Model Years enough for more than the double amount. Of course there will still be crashes, but looking at the posts, a lot of users mourn the loss of good computing time and the science that goes down the drain with it. If a more fail safe CPDN client were made, more experiments just might make it to the finish line, thus contributing to science. Thank You for Your time. ChrisD |
53)
Questions and Answers :
Windows :
Automatic Backup any good?
(Message 20044)
Posted 8 Feb 2006 by ChrisD Post: After 13 days of crunching, my laptop lost power and did not have the time to save work. :( When BOINC was restarted, my experiment was at once reported as failed, rendering that WU unrecoverable. CPDN Server says result completed, so I do not think it is a good idea to restore any backup from Yesterday and waste another 48 hours before the trikle goes in and gets rejected. So to avoid further trashing of WU\'s I have detatched that computer. Now, with WU-runtimes from 3 weeks to maybe 6 or 8 months, likelihood of crashes are huge. Haven\'t checked statistics, but ratio of successfully completed Runs and crashed ditto must be depressing. Having completed several THC-experiments, I sometimes had to restore a backup after a crash. Here the old client told me about the crash but asked me if the crash should be reported to CPDN. By shutting down and restoring the backup from previous day, I was able to continue crunching. This option is not available in BOINC, trashing even more Runs. How about letting the client do a backup every 24 hours automatically. If the client discovers that the data-files have been corrupted, it should try restoring from the backup, and if this fails, ask the user for permission to report the crash to CPDN. This way the user could restore a further backup if he had made such, and keep the experiment alive. I know that there is one solution available now: Suspend network activity, thus preventing the client from reporting anything until You are sure it is OK, but it is error prone (Error 40, the one behind the keyboard.) So how about implemeting the auto-backup suggested in the next client? ChrisD |
54)
Questions and Answers :
Windows :
I\'ve had it
(Message 7071)
Posted 26 Dec 2004 by ChrisD Post: > I'm now back on classic cpdn, which is working perfectly just as it did before > I tried boinc. I will stick with this until boinc becomes more > Athlon-compatible or until I need a new processor. What I don't know is > whether you can run boinc (for Seti etc) and cpdn classic simultaneously. > You can run CPDN-Classic and BOINC simultaneously. They usually share the resources nicely 50-50. ChrisD |
55)
Questions and Answers :
Windows :
BOINC Client has a security problem. Take a look
(Message 7070)
Posted 26 Dec 2004 by ChrisD Post: > >Of course address 32.255.71.0 is NOT Traceable! > > That address resolves ok in SamSpade... > > http://www.samspade.org/t/lookat?a=32.255.71.0 > Thank You for the link. This has now been added to my Favourites List :) However, to track the person that does the actual hacking is not detectable that easy. I have now filed a claim against the person who used the IP Address at the time the machine crashed. Very interesting, the IP is in UK?? Tanks again for the Link and a Merry Christmas to You from Denmark and ChrisD Of course this wish goes to all participants :) |
56)
Questions and Answers :
Windows :
I\'ve had it
(Message 7068)
Posted 26 Dec 2004 by ChrisD Post: In reply to the following: > Hi Sting > > No, I'm not saying that the boinc version is flawed. I agree with Andrew that > cpdn is a particularly demanding task 1. because the model itself is complex > and 2. the model has to stay put without crashing out for so long (6 weeks+ on > my machine working 24/7, though other people with newer, more powerful > machines crunch much faster). Lots of people are crunching the boinc version > effortlessly. > > What I am saying is that I spent quite a lot of time learning exit the model > and turn off the machine without losing it, then thinking that my continuing > problems were due to version 4.04, and finally concluding when I still had > problems with 4.13 that my Athlon and boinc don't like each other and require > extended therapy. Other people who have come into cpdn-boinc at a later stage > can maybe learn from this experience, not spend so much time losing models, > and take quicker remedial action. > > They will sort out this problem of models crashing, but I've no doubt it will > take time. I'm sure that many problems don't surface until after projects are > launched. Beta-testing isn't enough, because the people who sign up are > experts, not typical of users like me. > did You have a look at Your log-files. Do You just happen to have the same problem as me. Take a look at my post. http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=1472 ChrisD |
57)
Questions and Answers :
Windows :
BOINC Client has a security problem. Take a look
(Message 7067)
Posted 26 Dec 2004 by ChrisD Post: Machine has been processing 24/7 without a single hickup until: We are at the trikle sent 183634 TS into phase 2 Here trouble begins: 2004-12-25 22:16:21 [climateprediction.net] Couldn't read master page for climateprediction.net: error -113 2004-12-25 22:16:21 [climateprediction.net] Master file fetch failed 2004-12-25 22:16:21 [climateprediction.net] Deferring communication with project for 1 hours, 45 minutes, and 33 seconds 2004-12-25 22:34:08 [---] GUI RPC request from non-allowed address 32.255.71.0 2004-12-25 22:34:09 [---] GUI RPC request from non-allowed address 32.255.71.0 2004-12-25 22:34:10 [---] GUI RPC request from non-allowed address 32.255.71.0 2004-12-25 22:34:11 [---] GUI RPC request from non-allowed address 32.255.71.0 2004-12-25 22:34:20 [climateprediction.net] Unrecoverable error for result 2jlw_100139926_4 ( - exit code -2 (0xfffffffe)) 2004-12-25 22:34:20 [climateprediction.net] Deferring communication with project for 1 hours, 46 minutes, and 26 seconds 2004-12-25 22:36:09 [---] GUI RPC request from non-allowed address 32.255.71.0 this goes on at 1 sec. intervals until machines just gives up and crashes. Last lifesign: 2004-12-25 22:37:38 [---] GUI RPC request from non-allowed address 32.255.71.0 That's it Folks. Of course address 32.255.71.0 is NOT Traceable! This is not the first experiment that gets trashed this way. Seems that BOINC Client has a serious security problem. Until this is sorted out I am reverting back to CPDN Classic. ChrisD |
58)
Questions and Answers :
Windows :
WU 316405 lost, or what NOT to do!!
(Message 6012)
Posted 10 Nov 2004 by ChrisD Post: Friends: Look, listen and learn. :( I have ADSL and of course I use a router between my DSL Modem and my LAN. My ISP is TELE2. They charge me for 1M/128K but my bandwidth is 512K/128K only. I have contacted their customer support several times to make them rectify the problem and here it comes: In order to troubleshoot, they insisted that I connected my DSL Modem directly to my LAN Card! Any argumentation about hackers was no good, unless I connected Clean from LAN-Card to Modem, they would not fix my DSL. So I removed my host ATI from my LAN, enabled XP's firewall and connected it direct to the internet and downloaded Tele2's 500 Mb testfile. Within 45 minutes my now, as it turned out, defenceless computer was hacked and XP just showed a window: NT Error, shutting down in 60 seconds. When the computer was restarted cpu useage was 100% without Boinc running and outgoing LAN Traffic was at the maximum 128 Kbps. I tried repairing the XP-install, but as soon as XP initialized the network, the hacker reentered my machine and prevented windows from installing. Only way out: Reconnect machine behind the router, Reformat the HDD and install Windows from scratch. This was the end of WU 316405 :(, 1 trickle away from completing phase One. So: Never setup Windows XP while connected to the internet. XP's built in firewall sucks. (Between us, I don't like Tele2 much either). ChrisD |
59)
Questions and Answers :
Windows :
How to prevent d/l of new experiments?
(Message 5645)
Posted 25 Oct 2004 by ChrisD Post: I have a laptop that is a slow cruncher. It's been running CPDN/Boinc since early August and it is still a week from completing the first model. I intend to relieve it from duty when the model completes, but from my other machines I know that Boinc will fetch a new experiment, some time before completion of the current. How do I prevent Boinc from d/l'ing a new WU without messing the whole ting up (Deleting accounts etc.?) I know I can just detatch when the result is uploaded, but this will trash the model just downloaded. If possible, How do I avoid this? ChrisD |
60)
Questions and Answers :
Windows :
Trickle climateworksessions
(Message 5643)
Posted 25 Oct 2004 by ChrisD Post: At first, make sure Your Internet connection is OK. Just try to start IE and see that it actuallly fetches fresh pages from the internet, not just displaying pages from the cache. This has tricked me a few times :). If this is OK, check that You have not disabled Network traffic in Boinc. My experience is: if IE is working, and Network traffic is enabled in Boinc, the trickles will get through. Check the messages section to see if the project is backed off due to no connection, this will tell You when the trickles will be sent after You fix the Internet Connection. ChrisD |
©2024 climateprediction.net