Project communication failure
Questions and Answers :
Windows :
Project communication failure
Message board moderation
Previous · 1 · 2
| Author | Message |
|---|---|
John McLeod VII  Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 
|
Hi John, It is suopposed to generate some extra log detail.   BOINC WIKI ID: 598376 ·  |
 AllenIN  Send message Joined: 5 Dec 00 Posts: 292 Credit: 58,297,005 RAC: 311
 |
Hi John, Okay, then I guess I did it right......surprisingly. Here is what I have today.......... 7/3/07 8:51:39 PM||Starting BOINC client version 5.10.7 for windows_intelx86 7/3/07 8:51:39 PM||log flags: task, file_xfer, sched_ops 7/3/07 8:51:39 PM||Libraries: libcurl/7.16.1 OpenSSL/0.9.8e zlib/1.2.3 7/3/07 8:51:39 PM||Data directory: C:\\PROGRAM FILES\\BOINC 7/3/07 8:51:39 PM|SETI@home|Found app_info.xml; using anonymous platform 7/3/07 8:51:39 PM||Processor: 1 AuthenticAMD AMD Athlon(tm) XP 2600+ [AMD Athlon(tm) XP 2600+] 7/3/07 8:51:39 PM||Processor features: fpu sse 3dnow mmx 7/3/07 8:51:39 PM||Memory: 511.43 MB physical, 1.00 GB virtual 7/3/07 8:51:39 PM||Disk: 114.46 GB total, 93.50 GB free 7/3/07 8:51:39 PM|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 1934978; location: home; project prefs: home 7/3/07 8:51:39 PM||No general preferences found - using BOINC defaults 7/3/07 8:51:39 PM||Reading preferences override file 7/3/07 8:51:39 PM||Preferences limit memory usage when active to 255.72MB 7/3/07 8:51:39 PM||Preferences limit memory usage when idle to 460.29MB 7/3/07 8:51:39 PM||Preferences limit disk usage to 9.31GB 7/3/07 8:51:39 PM|SETI@home|Restarting task 24no99aa.27926.10480.1003414.3.121_2 using setiathome_enhanced version 515 7/3/07 8:51:39 PM|SETI@home|Sending scheduler request: Requested by user 7/3/07 8:51:39 PM|SETI@home|Requesting 109188 seconds of new work, and reporting 3 completed tasks 7/3/07 8:52:24 PM||Project communication failed: attempting access to reference site 7/3/07 8:52:25 PM||Access to reference site succeeded - project servers may be temporarily down. 7/3/07 8:52:26 PM|SETI@home|Scheduler request failed: couldn't connect to server 7/3/07 8:52:26 PM|SETI@home|Deferring communication for 3 min 40 sec 7/3/07 8:52:26 PM|SETI@home|Reason: scheduler request failed 7/3/07 8:52:58 PM|SETI@home|Sending scheduler request: Requested by user 7/3/07 8:52:58 PM|SETI@home|Requesting 109212 seconds of new work, and reporting 3 completed tasks 7/3/07 8:53:44 PM||Project communication failed: attempting access to reference site 7/3/07 8:53:45 PM||Access to reference site succeeded - project servers may be temporarily down. 7/3/07 8:53:46 PM|SETI@home|Scheduler request failed: couldn't connect to server 7/3/07 8:53:46 PM|SETI@home|Deferring communication for 12 min 48 sec 7/3/07 8:53:46 PM|SETI@home|Reason: scheduler request failed 7/3/07 8:59:41 PM|SETI@home|Sending scheduler request: Requested by user 7/3/07 8:59:41 PM|SETI@home|Requesting 109615 seconds of new work, and reporting 3 completed tasks 7/3/07 9:00:27 PM||Project communication failed: attempting access to reference site 7/3/07 9:00:27 PM|SETI@home|Scheduler request failed: couldn't connect to server 7/3/07 9:00:27 PM|SETI@home|Deferring communication for 25 min 45 sec 7/3/07 9:00:27 PM|SETI@home|Reason: scheduler request failed 7/3/07 9:00:29 PM||Access to reference site succeeded - project servers may be temporarily down. 7/3/07 9:26:15 PM|SETI@home|Sending scheduler request: Requested by user 7/3/07 9:26:15 PM|SETI@home|Requesting 111192 seconds of new work, and reporting 3 completed tasks 7/3/07 9:27:02 PM||Project communication failed: attempting access to reference site 7/3/07 9:27:02 PM|SETI@home|Scheduler request failed: couldn't connect to server 7/3/07 9:27:02 PM|SETI@home|Deferring communication for 1 hr 29 min 45 sec 7/3/07 9:27:02 PM|SETI@home|Reason: scheduler request failed 7/3/07 9:27:05 PM||Access to reference site succeeded - project servers may be temporarily down. 7/3/07 9:31:18 PM|SETI@home|Computation for task 24no99aa.27926.10480.1003414.3.121_2 finished 7/3/07 9:31:18 PM|SETI@home|Starting 24no99aa.27926.10480.1003414.3.243_2 7/3/07 9:31:18 PM|SETI@home|Starting task 24no99aa.27926.10480.1003414.3.243_2 using setiathome_enhanced version 515 7/3/07 9:31:20 PM|SETI@home|[file_xfer] Started upload of file 24no99aa.27926.10480.1003414.3.121_2_0 7/3/07 9:31:26 PM|SETI@home|[file_xfer] Finished upload of file 24no99aa.27926.10480.1003414.3.121_2_0 7/3/07 9:31:26 PM|SETI@home|[file_xfer] Throughput 30046 bytes/sec 7/3/07 10:56:51 PM|SETI@home|Sending scheduler request: Requested by user 7/3/07 10:56:51 PM|SETI@home|Requesting 128438 seconds of new work, and reporting 4 completed tasks 7/3/07 10:57:38 PM||Project communication failed: attempting access to reference site 7/3/07 10:57:38 PM|SETI@home|Scheduler request failed: couldn't connect to server 7/3/07 10:57:38 PM|SETI@home|Deferring communication for 2 hr 37 min 11 sec 7/3/07 10:57:38 PM|SETI@home|Reason: scheduler request failed 7/3/07 10:57:40 PM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 1:34:50 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 1:34:50 AM|SETI@home|Requesting 139983 seconds of new work, and reporting 4 completed tasks 7/4/07 1:35:36 AM||Project communication failed: attempting access to reference site 7/4/07 1:35:36 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 1:35:36 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 1:35:36 AM|SETI@home|Reason: scheduler request failed 7/4/07 1:35:40 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 1:36:39 AM|SETI@home|Fetching scheduler list 7/4/07 1:36:44 AM|SETI@home|Master file download succeeded 7/4/07 1:36:50 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 1:36:50 AM|SETI@home|Requesting 140149 seconds of new work, and reporting 4 completed tasks 7/4/07 1:37:37 AM||Project communication failed: attempting access to reference site 7/4/07 1:37:37 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 1:37:37 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 1:37:37 AM|SETI@home|Reason: scheduler request failed 7/4/07 1:37:41 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 1:38:39 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 1:38:39 AM|SETI@home|Requesting 140318 seconds of new work, and reporting 4 completed tasks 7/4/07 1:39:25 AM||Project communication failed: attempting access to reference site 7/4/07 1:39:26 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 1:39:26 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 1:39:26 AM|SETI@home|Reason: scheduler request failed 7/4/07 1:39:29 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 1:40:29 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 1:40:29 AM|SETI@home|Requesting 140479 seconds of new work, and reporting 4 completed tasks 7/4/07 1:41:17 AM||Project communication failed: attempting access to reference site 7/4/07 1:41:20 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 1:41:21 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 1:41:21 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 1:41:21 AM|SETI@home|Reason: scheduler request failed 7/4/07 1:42:24 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 1:42:24 AM|SETI@home|Requesting 140665 seconds of new work, and reporting 4 completed tasks 7/4/07 1:43:10 AM||Project communication failed: attempting access to reference site 7/4/07 1:43:11 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 1:43:11 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 1:43:11 AM|SETI@home|Reason: scheduler request failed 7/4/07 1:43:13 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 1:44:14 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 1:44:14 AM|SETI@home|Requesting 140815 seconds of new work, and reporting 4 completed tasks 7/4/07 1:45:02 AM||Project communication failed: attempting access to reference site 7/4/07 1:45:05 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 1:45:06 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 1:45:06 AM|SETI@home|Deferring communication for 2 min 11 sec 7/4/07 1:45:06 AM|SETI@home|Reason: scheduler request failed 7/4/07 1:47:22 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 1:47:22 AM|SETI@home|Requesting 141085 seconds of new work, and reporting 4 completed tasks 7/4/07 1:48:10 AM||Project communication failed: attempting access to reference site 7/4/07 1:48:13 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 1:48:14 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 1:48:14 AM|SETI@home|Deferring communication for 6 min 36 sec 7/4/07 1:48:14 AM|SETI@home|Reason: scheduler request failed 7/4/07 1:54:51 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 1:54:51 AM|SETI@home|Requesting 141867 seconds of new work, and reporting 4 completed tasks 7/4/07 1:55:39 AM||Project communication failed: attempting access to reference site 7/4/07 1:55:43 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 1:55:44 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 1:55:44 AM|SETI@home|Deferring communication for 17 min 11 sec 7/4/07 1:55:44 AM|SETI@home|Reason: scheduler request failed 7/4/07 2:12:58 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 2:12:58 AM|SETI@home|Requesting 143472 seconds of new work, and reporting 4 completed tasks 7/4/07 2:13:45 AM||Project communication failed: attempting access to reference site 7/4/07 2:13:45 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 2:13:45 AM|SETI@home|Deferring communication for 1 min 1 sec 7/4/07 2:13:45 AM|SETI@home|Reason: scheduler request failed 7/4/07 2:13:48 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 2:14:48 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 2:14:48 AM|SETI@home|Requesting 143647 seconds of new work, and reporting 4 completed tasks 7/4/07 2:15:36 AM||Project communication failed: attempting access to reference site 7/4/07 2:15:39 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 2:15:40 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 2:15:40 AM|SETI@home|Deferring communication for 1 hr 10 min 31 sec 7/4/07 2:15:40 AM|SETI@home|Reason: scheduler request failed 7/4/07 3:26:12 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 3:26:12 AM|SETI@home|Requesting 149850 seconds of new work, and reporting 4 completed tasks 7/4/07 3:26:59 AM||Project communication failed: attempting access to reference site 7/4/07 3:26:59 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 3:26:59 AM|SETI@home|Deferring communication for 3 hr 14 min 12 sec 7/4/07 3:26:59 AM|SETI@home|Reason: scheduler request failed 7/4/07 3:27:02 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 4:41:31 AM|SETI@home|Computation for task 24no99aa.27926.10480.1003414.3.243_2 finished 7/4/07 4:41:31 AM|SETI@home|Starting 13ap99aa.28524.20498.54842.3.204_3 7/4/07 4:41:31 AM|SETI@home|Starting task 13ap99aa.28524.20498.54842.3.204_3 using setiathome_enhanced version 515 7/4/07 4:41:33 AM|SETI@home|[file_xfer] Started upload of file 24no99aa.27926.10480.1003414.3.243_2_0 7/4/07 4:41:41 AM|SETI@home|[file_xfer] Finished upload of file 24no99aa.27926.10480.1003414.3.243_2_0 7/4/07 4:41:41 AM|SETI@home|[file_xfer] Throughput 29637 bytes/sec 7/4/07 6:41:12 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 6:41:12 AM|SETI@home|Requesting 173153 seconds of new work, and reporting 5 completed tasks 7/4/07 6:41:58 AM||Project communication failed: attempting access to reference site 7/4/07 6:41:59 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 6:41:59 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 6:41:59 AM|SETI@home|Reason: scheduler request failed 7/4/07 6:42:01 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 6:43:02 AM|SETI@home|Fetching scheduler list 7/4/07 6:43:07 AM|SETI@home|Master file download succeeded 7/4/07 6:43:12 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 6:43:12 AM|SETI@home|Requesting 173253 seconds of new work, and reporting 5 completed tasks 7/4/07 6:43:59 AM||Project communication failed: attempting access to reference site 7/4/07 6:43:59 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 6:43:59 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 6:43:59 AM|SETI@home|Reason: scheduler request failed 7/4/07 6:44:03 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 6:45:02 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 6:45:02 AM|SETI@home|Requesting 173336 seconds of new work, and reporting 5 completed tasks 7/4/07 6:45:49 AM||Project communication failed: attempting access to reference site 7/4/07 6:45:49 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 6:45:49 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 6:45:49 AM|SETI@home|Reason: scheduler request failed 7/4/07 6:45:52 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 6:46:52 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 6:46:52 AM|SETI@home|Requesting 173428 seconds of new work, and reporting 5 completed tasks 7/4/07 6:47:39 AM||Project communication failed: attempting access to reference site 7/4/07 6:47:39 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 6:47:39 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 6:47:39 AM|SETI@home|Reason: scheduler request failed 7/4/07 6:47:42 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 6:48:42 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 6:48:42 AM|SETI@home|Requesting 173520 seconds of new work, and reporting 5 completed tasks 7/4/07 6:49:30 AM||Project communication failed: attempting access to reference site 7/4/07 6:49:33 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 6:49:34 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 6:49:34 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 6:49:34 AM|SETI@home|Reason: scheduler request failed 7/4/07 6:50:36 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 6:50:36 AM|SETI@home|Requesting 173684 seconds of new work, and reporting 5 completed tasks 7/4/07 6:51:25 AM||Project communication failed: attempting access to reference site 7/4/07 6:51:28 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 6:51:29 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 6:51:29 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 6:51:29 AM|SETI@home|Reason: scheduler request failed 7/4/07 6:52:31 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 6:52:31 AM|SETI@home|Requesting 173927 seconds of new work, and reporting 5 completed tasks 7/4/07 6:53:19 AM||Project communication failed: attempting access to reference site 7/4/07 6:53:23 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 6:53:24 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 6:53:24 AM|SETI@home|Deferring communication for 6 min 9 sec 7/4/07 6:53:24 AM|SETI@home|Reason: scheduler request failed 7/4/07 6:59:35 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 6:59:35 AM|SETI@home|Requesting 174289 seconds of new work, and reporting 5 completed tasks 7/4/07 7:00:22 AM||Project communication failed: attempting access to reference site 7/4/07 7:00:22 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 7:00:22 AM|SETI@home|Deferring communication for 3 min 41 sec 7/4/07 7:00:22 AM|SETI@home|Reason: scheduler request failed 7/4/07 7:00:25 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 7:04:06 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 7:04:06 AM|SETI@home|Requesting 174508 seconds of new work, and reporting 5 completed tasks 7/4/07 7:04:53 AM||Project communication failed: attempting access to reference site 7/4/07 7:04:53 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 7:04:53 AM|SETI@home|Deferring communication for 42 min 40 sec 7/4/07 7:04:53 AM|SETI@home|Reason: scheduler request failed 7/4/07 7:04:56 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 7:47:39 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 7:47:39 AM|SETI@home|Requesting 176982 seconds of new work, and reporting 5 completed tasks 7/4/07 7:48:26 AM||Project communication failed: attempting access to reference site 7/4/07 7:48:26 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 7:48:26 AM|SETI@home|Deferring communication for 7 min 57 sec 7/4/07 7:48:26 AM|SETI@home|Reason: scheduler request failed 7/4/07 7:48:30 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 7:56:26 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 7:56:26 AM|SETI@home|Requesting 177606 seconds of new work, and reporting 5 completed tasks 7/4/07 7:57:13 AM||Project communication failed: attempting access to reference site 7/4/07 7:57:13 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 7:57:13 AM|SETI@home|Deferring communication for 4 min 20 sec 7/4/07 7:57:13 AM|SETI@home|Reason: scheduler request failed 7/4/07 7:57:16 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 8:01:35 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 8:01:35 AM|SETI@home|Requesting 177959 seconds of new work, and reporting 5 completed tasks 7/4/07 8:02:22 AM||Project communication failed: attempting access to reference site 7/4/07 8:02:22 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 8:02:22 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 8:02:22 AM|SETI@home|Reason: scheduler request failed 7/4/07 8:02:25 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 8:03:24 AM|SETI@home|Fetching scheduler list 7/4/07 8:03:30 AM|SETI@home|Master file download succeeded 7/4/07 8:03:35 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 8:03:35 AM|SETI@home|Requesting 178119 seconds of new work, and reporting 5 completed tasks 7/4/07 8:04:23 AM||Project communication failed: attempting access to reference site 7/4/07 8:04:26 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 8:04:27 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 8:04:27 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 8:04:27 AM|SETI@home|Reason: scheduler request failed 7/4/07 8:05:30 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 8:05:30 AM|SETI@home|Requesting 178278 seconds of new work, and reporting 5 completed tasks 7/4/07 8:06:17 AM||Project communication failed: attempting access to reference site 7/4/07 8:06:17 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 8:06:17 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 8:06:17 AM|SETI@home|Reason: scheduler request failed 7/4/07 8:06:20 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 8:07:20 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 8:07:20 AM|SETI@home|Requesting 178429 seconds of new work, and reporting 5 completed tasks 7/4/07 8:08:07 AM||Project communication failed: attempting access to reference site 7/4/07 8:08:07 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 8:08:07 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 8:08:07 AM|SETI@home|Reason: scheduler request failed 7/4/07 8:08:09 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 8:09:09 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 8:09:09 AM|SETI@home|Requesting 178581 seconds of new work, and reporting 5 completed tasks 7/4/07 8:09:57 AM||Project communication failed: attempting access to reference site 7/4/07 8:10:00 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 8:10:02 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 8:10:02 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 8:10:02 AM|SETI@home|Reason: scheduler request failed 7/4/07 8:11:04 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 8:11:04 AM|SETI@home|Requesting 178739 seconds of new work, and reporting 5 completed tasks 7/4/07 8:11:50 AM||Project communication failed: attempting access to reference site 7/4/07 8:11:51 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 8:11:51 AM|SETI@home|Deferring communication for 1 min 58 sec 7/4/07 8:11:51 AM|SETI@home|Reason: scheduler request failed 7/4/07 8:11:53 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 8:13:51 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 8:13:51 AM|SETI@home|Requesting 178964 seconds of new work, and reporting 5 completed tasks 7/4/07 8:14:39 AM||Project communication failed: attempting access to reference site 7/4/07 8:14:43 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 8:14:44 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 8:14:44 AM|SETI@home|Deferring communication for 1 min 23 sec 7/4/07 8:14:44 AM|SETI@home|Reason: scheduler request failed 7/4/07 8:16:13 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 8:16:13 AM|SETI@home|Requesting 179176 seconds of new work, and reporting 5 completed tasks 7/4/07 8:16:58 AM||Project communication failed: attempting access to reference site 7/4/07 8:16:59 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 8:16:59 AM|SETI@home|Deferring communication for 8 min 42 sec 7/4/07 8:16:59 AM|SETI@home|Reason: scheduler request failed 7/4/07 8:17:02 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 8:25:47 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 8:25:47 AM|SETI@home|Requesting 179956 seconds of new work, and reporting 5 completed tasks 7/4/07 8:26:35 AM||Project communication failed: attempting access to reference site 7/4/07 8:26:38 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 8:26:39 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 8:26:39 AM|SETI@home|Deferring communication for 4 min 24 sec 7/4/07 8:26:39 AM|SETI@home|Reason: scheduler request failed 7/4/07 8:31:06 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 8:31:06 AM|SETI@home|Requesting 180466 seconds of new work, and reporting 5 completed tasks 7/4/07 8:31:53 AM||Project communication failed: attempting access to reference site 7/4/07 8:31:53 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 8:31:53 AM|SETI@home|Deferring communication for 1 hr 43 min 0 sec 7/4/07 8:31:53 AM|SETI@home|Reason: scheduler request failed 7/4/07 8:31:56 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 10:14:54 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 10:14:54 AM|SETI@home|Requesting 188158 seconds of new work, and reporting 5 completed tasks 7/4/07 10:15:41 AM||Project communication failed: attempting access to reference site 7/4/07 10:15:41 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 10:15:41 AM|SETI@home|Deferring communication for 2 min 55 sec 7/4/07 10:15:41 AM|SETI@home|Reason: scheduler request failed 7/4/07 10:15:45 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 10:18:39 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 10:18:39 AM|SETI@home|Requesting 188366 seconds of new work, and reporting 5 completed tasks 7/4/07 10:19:25 AM||Project communication failed: attempting access to reference site 7/4/07 10:19:25 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 10:19:25 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 10:19:25 AM|SETI@home|Reason: scheduler request failed 7/4/07 10:19:29 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 10:20:28 AM|SETI@home|Fetching scheduler list 7/4/07 10:20:33 AM|SETI@home|Master file download succeeded 7/4/07 10:20:39 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 10:20:39 AM|SETI@home|Requesting 188472 seconds of new work, and reporting 5 completed tasks 7/4/07 10:21:26 AM||Project communication failed: attempting access to reference site 7/4/07 10:21:26 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 10:21:26 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 10:21:26 AM|SETI@home|Reason: scheduler request failed 7/4/07 10:21:29 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 10:22:28 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 10:22:28 AM|SETI@home|Requesting 188578 seconds of new work, and reporting 5 completed tasks 7/4/07 10:23:14 AM||Project communication failed: attempting access to reference site 7/4/07 10:23:15 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 10:23:15 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 10:23:15 AM|SETI@home|Reason: scheduler request failed 7/4/07 10:23:17 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 10:24:18 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 10:24:18 AM|SETI@home|Requesting 188680 seconds of new work, and reporting 5 completed tasks 7/4/07 10:25:06 AM||Project communication failed: attempting access to reference site 7/4/07 10:25:09 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 10:25:10 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 10:25:10 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 10:25:10 AM|SETI@home|Reason: scheduler request failed 7/4/07 10:26:13 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 10:26:13 AM|SETI@home|Requesting 188784 seconds of new work, and reporting 5 completed tasks 7/4/07 10:26:59 AM||Project communication failed: attempting access to reference site 7/4/07 10:27:00 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 10:27:00 AM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 10:27:00 AM|SETI@home|Reason: scheduler request failed 7/4/07 10:27:02 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 10:28:03 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 10:28:03 AM|SETI@home|Requesting 188868 seconds of new work, and reporting 5 completed tasks 7/4/07 10:28:51 AM||Project communication failed: attempting access to reference site 7/4/07 10:28:54 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 10:28:55 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 10:28:55 AM|SETI@home|Deferring communication for 2 min 9 sec 7/4/07 10:28:55 AM|SETI@home|Reason: scheduler request failed 7/4/07 10:31:06 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 10:31:06 AM|SETI@home|Requesting 189030 seconds of new work, and reporting 5 completed tasks 7/4/07 10:31:54 AM||Project communication failed: attempting access to reference site 7/4/07 10:31:57 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 10:31:58 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 10:31:58 AM|SETI@home|Deferring communication for 6 min 15 sec 7/4/07 10:31:58 AM|SETI@home|Reason: scheduler request failed 7/4/07 10:35:06 AM|SETI@home|Computation for task 13ap99aa.28524.20498.54842.3.204_3 finished 7/4/07 10:35:06 AM|SETI@home|Starting 13ap99aa.28524.31584.540910.3.35_0 7/4/07 10:35:06 AM|SETI@home|Starting task 13ap99aa.28524.31584.540910.3.35_0 using setiathome_enhanced version 515 7/4/07 10:35:08 AM|SETI@home|[file_xfer] Started upload of file 13ap99aa.28524.20498.54842.3.204_3_0 7/4/07 10:35:14 AM|SETI@home|[file_xfer] Finished upload of file 13ap99aa.28524.20498.54842.3.204_3_0 7/4/07 10:35:14 AM|SETI@home|[file_xfer] Throughput 29094 bytes/sec 7/4/07 10:38:15 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 10:38:15 AM|SETI@home|Requesting 190063 seconds of new work, and reporting 6 completed tasks 7/4/07 10:39:02 AM||Project communication failed: attempting access to reference site 7/4/07 10:39:02 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 10:39:02 AM|SETI@home|Deferring communication for 8 min 52 sec 7/4/07 10:39:02 AM|SETI@home|Reason: scheduler request failed 7/4/07 10:39:05 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 10:47:56 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 10:47:56 AM|SETI@home|Requesting 189987 seconds of new work, and reporting 6 completed tasks 7/4/07 10:48:44 AM||Project communication failed: attempting access to reference site 7/4/07 10:48:47 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 10:48:48 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 10:48:48 AM|SETI@home|Deferring communication for 25 min 52 sec 7/4/07 10:48:48 AM|SETI@home|Reason: scheduler request failed 7/4/07 11:14:45 AM|SETI@home|Sending scheduler request: Requested by user 7/4/07 11:14:45 AM|SETI@home|Requesting 190200 seconds of new work, and reporting 6 completed tasks 7/4/07 11:15:33 AM||Project communication failed: attempting access to reference site 7/4/07 11:15:37 AM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 11:15:38 AM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 11:15:38 AM|SETI@home|Deferring communication for 1 hr 15 min 6 sec 7/4/07 11:15:38 AM|SETI@home|Reason: scheduler request failed 7/4/07 12:12:30 PM|SETI@home|Sending scheduler request: Requested by user 7/4/07 12:12:30 PM|SETI@home|Requesting 190674 seconds of new work, and reporting 6 completed tasks 7/4/07 12:13:16 PM||Project communication failed: attempting access to reference site 7/4/07 12:13:17 PM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 12:13:17 PM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 12:13:17 PM|SETI@home|Deferring communication for 2 hr 53 min 33 sec 7/4/07 12:13:17 PM|SETI@home|Reason: scheduler request failed 7/4/07 12:20:10 PM|SETI@home|Sending scheduler request: Requested by user 7/4/07 12:20:10 PM|SETI@home|Requesting 190661 seconds of new work, and reporting 6 completed tasks 7/4/07 12:20:55 PM||Project communication failed: attempting access to reference site 7/4/07 12:20:56 PM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 12:20:56 PM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 12:20:56 PM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 12:20:56 PM|SETI@home|Reason: scheduler request failed 7/4/07 12:21:59 PM|SETI@home|Fetching scheduler list 7/4/07 12:22:04 PM|SETI@home|Master file download succeeded 7/4/07 12:22:09 PM|SETI@home|Sending scheduler request: Requested by user 7/4/07 12:22:09 PM|SETI@home|Requesting 190634 seconds of new work, and reporting 6 completed tasks 7/4/07 12:22:55 PM||Project communication failed: attempting access to reference site 7/4/07 12:22:55 PM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 12:22:55 PM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 12:22:55 PM|SETI@home|Reason: scheduler request failed 7/4/07 12:22:56 PM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 12:23:58 PM|SETI@home|Sending scheduler request: Requested by user 7/4/07 12:23:58 PM|SETI@home|Requesting 190687 seconds of new work, and reporting 6 completed tasks 7/4/07 12:24:44 PM||Project communication failed: attempting access to reference site 7/4/07 12:24:44 PM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 12:24:44 PM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 12:24:44 PM|SETI@home|Reason: scheduler request failed 7/4/07 12:24:45 PM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 12:25:46 PM|SETI@home|Sending scheduler request: Requested by user 7/4/07 12:25:46 PM|SETI@home|Requesting 190655 seconds of new work, and reporting 6 completed tasks It looks like it accepted one u/l, but when I checked my numbers, nothing changed, however, it could be that that WU is pending and hasn't shown up yet. Do you see anything in this? Thanks, Allen ID: 598414 · |
|
AllenIN Send message Joined: 5 Dec 00 Posts: 292 Credit: 58,297,005 RAC: 311
|
Hi John, In desperation, I thought I would go back to an earlier version to see if reinstalling it might have some positive effect on the situation. Having done so, I don't see any difference, but I thought you might. As you can see, I switched from 5.10.7 to 5.8.16, which is their recommended version. 7/4/07 1:40:09 PM||Starting BOINC client version 5.8.16 for windows_intelx86 7/4/07 1:40:09 PM||log flags: task, file_xfer, sched_ops 7/4/07 1:40:09 PM||Libraries: libcurl/7.16.0 OpenSSL/0.9.8a zlib/1.2.3 7/4/07 1:40:09 PM||Data directory: C:\\PROGRAM FILES\\BOINC 7/4/07 1:40:09 PM|SETI@home|Found app_info.xml; using anonymous platform 7/4/07 1:40:09 PM||Processor: 1 AuthenticAMD AMD Athlon(tm) XP 2600+ [AMD Athlon(tm) XP 2600+] [fpu sse 3dnow mmx] 7/4/07 1:40:09 PM||Memory: 511.43 MB physical, 1.00 GB virtual 7/4/07 1:40:09 PM||Disk: 114.46 GB total, 93.49 GB free 7/4/07 1:40:09 PM||Version change (5.10.7 -> 5.8.16) 7/4/07 1:40:09 PM|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 1934978; location: home; project prefs: home 7/4/07 1:40:09 PM||General prefs: from SETI@home (last modified 2007-06-23 23:45:09) 7/4/07 1:40:09 PM||Host location: home 7/4/07 1:40:09 PM||General prefs: using separate prefs for home 7/4/07 1:40:09 PM||Reading preferences override file 7/4/07 1:40:09 PM||Running CPU benchmarks 7/4/07 1:41:12 PM||Benchmark results: 7/4/07 1:41:12 PM|| Number of CPUs: 1 7/4/07 1:41:12 PM|| 1804 floating point MIPS (Whetstone) per CPU 7/4/07 1:41:12 PM|| 3211 integer MIPS (Dhrystone) per CPU 7/4/07 1:41:13 PM|SETI@home|Restarting task 13ap99aa.28524.31584.540910.3.35_0 using setiathome_enhanced version 515 7/4/07 1:41:53 PM|SETI@home|Sending scheduler request: Requested by user 7/4/07 1:41:53 PM|SETI@home|Reporting 6 tasks 7/4/07 1:42:39 PM||Project communication failed: attempting access to reference site 7/4/07 1:42:40 PM||Access to reference site succeeded - project servers may be temporarily down. 7/4/07 1:42:41 PM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 1:42:41 PM|SETI@home|Deferring communication for 1 min 0 sec 7/4/07 1:42:41 PM|SETI@home|Reason: scheduler request failed 7/4/07 1:43:45 PM|SETI@home|Fetching scheduler list 7/4/07 1:43:50 PM|SETI@home|Master file download succeeded 7/4/07 1:43:55 PM|SETI@home|Sending scheduler request: Requested by user 7/4/07 1:43:55 PM|SETI@home|Reporting 6 tasks 7/4/07 1:44:41 PM||Project communication failed: attempting access to reference site 7/4/07 1:44:41 PM|SETI@home|Scheduler request failed: couldn't connect to server 7/4/07 1:44:41 PM|SETI@home|Sending scheduler request: Requested by user 7/4/07 1:44:41 PM|SETI@home|Reporting 6 tasks 7/4/07 1:44:42 PM||Access to reference site succeeded - project servers may be temporarily down. ID: 598477 · |
|
AllenIN Send message Joined: 5 Dec 00 Posts: 292 Credit: 58,297,005 RAC: 311
|
Hi John, Just thought I would give you an update. I totally shutdown the computer 3 times and restarted Boinc each time and on the third time, I got this..... 7/4/07 4:12:56 PM||Starting BOINC client version 5.8.16 for windows_intelx86 7/4/07 4:12:56 PM||log flags: task, file_xfer, sched_ops 7/4/07 4:12:56 PM||Libraries: libcurl/7.16.0 OpenSSL/0.9.8a zlib/1.2.3 7/4/07 4:12:56 PM||Data directory: C:\\PROGRAM FILES\\BOINC 7/4/07 4:12:56 PM|SETI@home|Found app_info.xml; using anonymous platform 7/4/07 4:12:56 PM||Processor: 1 AuthenticAMD AMD Athlon(tm) XP 2600+ [AMD Athlon(tm) XP 2600+] [fpu sse 3dnow mmx] 7/4/07 4:12:56 PM||Memory: 511.43 MB physical, 1.00 GB virtual 7/4/07 4:12:56 PM||Disk: 114.46 GB total, 93.50 GB free 7/4/07 4:12:56 PM|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 1934978; location: home; project prefs: home 7/4/07 4:12:56 PM||General prefs: from SETI@home (last modified 2007-06-23 23:45:09) 7/4/07 4:12:56 PM||Host location: home 7/4/07 4:12:56 PM||General prefs: using separate prefs for home 7/4/07 4:12:56 PM||Reading preferences override file 7/4/07 4:12:57 PM|SETI@home|Restarting task 13ap99aa.28524.31584.540910.3.35_0 using setiathome_enhanced version 515 7/4/07 4:29:22 PM|SETI@home|Sending scheduler request: Requested by user 7/4/07 4:29:22 PM|SETI@home|Reporting 6 tasks 7/4/07 4:29:26 PM|SETI@home|Scheduler request failed: HTTP file not found 7/4/07 4:29:26 PM|SETI@home|Sending scheduler request: Requested by user 7/4/07 4:29:26 PM|SETI@home|Reporting 6 tasks 7/4/07 4:29:31 PM|SETI@home|Scheduler RPC succeeded [server version 509] 7/4/07 4:29:31 PM|SETI@home|Deferring communication for 11 sec 7/4/07 4:29:31 PM|SETI@home|Reason: requested by project 7/4/07 4:30:29 PM|SETI@home|Sending scheduler request: Requested by user 7/4/07 4:30:29 PM|SETI@home|(not requesting new work or reporting completed tasks) 7/4/07 4:30:34 PM|SETI@home|Scheduler request failed: HTTP file not found 7/4/07 4:30:34 PM|SETI@home|Sending scheduler request: Requested by user 7/4/07 4:30:34 PM|SETI@home|(not requesting new work or reporting completed tasks) 7/4/07 4:30:39 PM|SETI@home|Scheduler RPC succeeded [server version 509] 7/4/07 4:30:39 PM|SETI@home|Deferring communication for 11 sec 7/4/07 4:30:39 PM|SETI@home|Reason: requested by project All uploaded fine, but like the last time, I still don't know why. I'm just grateful that it started working again. Sure is strange though. Any thoughts??????......grin Happy 4th !!!! ID: 598617 · |
|
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0
|
I am not seeing the extra debug messages mixed in with the normal messages. Somehow, you must not have create the cc_config.xml file correctly. BOINC WIKI ID: 598737 · |
|
AllenIN Send message Joined: 5 Dec 00 Posts: 292 Credit: 58,297,005 RAC: 311
|
I am not seeing the extra debug messages mixed in with the normal messages. Somehow, you must not have create the cc_config.xml file correctly. John, Right you are! I had a hyphen instead of an underscore in the file name. I'm really slipping. Anyway, here is what I got after correcting that error. Naturally everything seems to be working now, but I thought I would pass it along anyway, just in case you might notice some other flaw. Also, do you think that it would be safe for me to reinstall the newer BoincManager or should I just leave well enough alone for now? Thanks, Allen 7/5/07 11:35:29 AM||Starting BOINC client version 5.8.16 for windows_intelx86 7/5/07 11:35:29 AM||log flags: task, file_xfer, sched_ops, sched_op_debug, http_debug, http_xfer_debug 7/5/07 11:35:29 AM||Libraries: libcurl/7.16.0 OpenSSL/0.9.8a zlib/1.2.3 7/5/07 11:35:29 AM||Data directory: C:\\PROGRAM FILES\\BOINC 7/5/07 11:35:29 AM|SETI@home|Found app_info.xml; using anonymous platform 7/5/07 11:35:29 AM||Processor: 1 AuthenticAMD AMD Athlon(tm) XP 2600+ [AMD Athlon(tm) XP 2600+] [fpu sse 3dnow mmx] 7/5/07 11:35:29 AM||Memory: 511.43 MB physical, 1.00 GB virtual 7/5/07 11:35:29 AM||Disk: 114.46 GB total, 93.50 GB free 7/5/07 11:35:29 AM|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 1934978; location: home; project prefs: home 7/5/07 11:35:29 AM||General prefs: from SETI@home (last modified 2007-06-23 23:45:09) 7/5/07 11:35:29 AM||Host location: home 7/5/07 11:35:29 AM||General prefs: using separate prefs for home 7/5/07 11:35:29 AM||Reading preferences override file 7/5/07 11:35:29 AM|SETI@home|Restarting task 24no99aa.27926.23170.829808.3.223_1 using setiathome_enhanced version 515 7/5/07 11:36:16 AM||[sched_op_debug] SCHEDULER_OP::init_op_project(): starting op for http://setiathome.berkeley.edu/ 7/5/07 11:36:16 AM|SETI@home|Sending scheduler request: Requested by user 7/5/07 11:36:16 AM|SETI@home|(not requesting new work or reporting completed tasks) 7/5/07 11:36:16 AM||[http_debug] HTTP_OP::init_post(): http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi"> 7/5/07 11:36:16 AM||[http_debug] [ID#0] info: About to connect() to setiboinc.ssl.berkeley.edu port 80 (#0) 7/5/07 11:36:16 AM||[http_debug] [ID#0] info: Trying 208.68.240.17... 7/5/07 11:36:16 AM||[http_debug] [ID#0] info: Connected to setiboinc.ssl.berkeley.edu (208.68.240.17) port 80 (#0) 7/5/07 11:36:16 AM||[http_debug] [ID#0] Sent header to server: POST /sah_cgi/cgi"> HTTP/1.1 User-Agent: BOINC client (windows_intelx86 5.8.16) Host: setiboinc.ssl.berkeley.edu Accept: */* Accept-Encoding: deflate, gzip Content-Type: application/x-www-form-urlencoded Content-Length: 11972 7/5/07 11:36:17 AM||[http_debug] [ID#0] Received header from server: HTTP/1.1 404 Not Found 7/5/07 11:36:17 AM||[http_debug] [ID#0] Received header from server: Date: Thu, 05 Jul 2007 15:36:16 GMT 7/5/07 11:36:17 AM||[http_debug] [ID#0] Received header from server: Server: Apache/2.2.4 (Fedora) 7/5/07 11:36:17 AM||[http_debug] [ID#0] Received header from server: Content-Length: 310 7/5/07 11:36:17 AM||[http_debug] [ID#0] Received header from server: Connection: close 7/5/07 11:36:17 AM||[http_debug] [ID#0] Received header from server: Content-Type: text/html; charset=iso-8859-1 7/5/07 11:36:17 AM||[http_xfer_debug] HTTP: wrote 310 bytes 7/5/07 11:36:17 AM||[http_debug] [ID#0] info: Expire cleared 7/5/07 11:36:21 AM|SETI@home|Scheduler request failed: HTTP file not found 7/5/07 11:36:21 AM|SETI@home|Sending scheduler request: Requested by user 7/5/07 11:36:21 AM|SETI@home|(not requesting new work or reporting completed tasks) 7/5/07 11:36:21 AM||[http_debug] HTTP_OP::init_post(): http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/5/07 11:36:21 AM||[http_debug] [ID#1] info: Examining connection #0 for reuse 7/5/07 11:36:21 AM||[http_debug] [ID#1] info: Connection #0 seems to be dead! 7/5/07 11:36:21 AM||[http_debug] [ID#1] info: Closing connection #0 7/5/07 11:36:21 AM||[http_debug] [ID#1] info: About to connect() to setiboinc.ssl.berkeley.edu port 80 (#0) 7/5/07 11:36:21 AM||[http_debug] [ID#1] info: Trying 208.68.240.17... 7/5/07 11:36:21 AM||[http_debug] [ID#1] info: Connected to setiboinc.ssl.berkeley.edu (208.68.240.17) port 80 (#0) 7/5/07 11:36:21 AM||[http_debug] [ID#1] Sent header to server: POST /sah_cgi/cgi HTTP/1.1 User-Agent: BOINC client (windows_intelx86 5.8.16) Host: setiboinc.ssl.berkeley.edu Accept: */* Accept-Encoding: deflate, gzip Content-Type: application/x-www-form-urlencoded Content-Length: 11972 7/5/07 11:36:22 AM||[http_debug] [ID#1] Received header from server: HTTP/1.1 200 OK 7/5/07 11:36:22 AM||[http_debug] [ID#1] Received header from server: Date: Thu, 05 Jul 2007 15:36:21 GMT 7/5/07 11:36:22 AM||[http_debug] [ID#1] Received header from server: Server: Apache/2.2.4 (Fedora) 7/5/07 11:36:22 AM||[http_debug] [ID#1] Received header from server: Connection: close 7/5/07 11:36:22 AM||[http_debug] [ID#1] Received header from server: Transfer-Encoding: chunked 7/5/07 11:36:22 AM||[http_debug] [ID#1] Received header from server: Content-Type: text/xml 7/5/07 11:36:22 AM||[http_xfer_debug] HTTP: wrote 1272 bytes 7/5/07 11:36:22 AM||[http_xfer_debug] HTTP: wrote 1436 bytes 7/5/07 11:36:22 AM||[http_xfer_debug] HTTP: wrote 1436 bytes 7/5/07 11:36:22 AM||[http_xfer_debug] HTTP: wrote 1436 bytes 7/5/07 11:36:22 AM||[http_xfer_debug] HTTP: wrote 696 bytes 7/5/07 11:36:22 AM||[http_debug] [ID#1] info: Expire cleared 7/5/07 11:36:26 AM|SETI@home|Scheduler RPC succeeded [server version 509] 7/5/07 11:36:26 AM|SETI@home|Project requested delay of 11.000000 seconds 7/5/07 11:36:26 AM|SETI@home|Deferring communication for 11 sec 7/5/07 11:36:26 AM|SETI@home|Reason: requested by project ID: 599087 · |
Aurora Borealis  Send message Joined: 14 Jan 01 Posts: 3075 Credit: 5,631,463 RAC: 0 
|
Version 5.8.16 is the current recomended Boinc client. The V5.10.x was quickly withdrawn because of a bug that was overlooked by the testers as a random windows problem. ID: 599092 · |
|
Alinator Send message Joined: 19 Apr 05 Posts: 4178 Credit: 4,647,982 RAC: 0
|
Except for the fact his last test was with 5.8.16. FWIW, I just checked on my host which is running 5.10.7, and it got through to the scheduler fine. In fact with http debug enabled my log snippet looks just like yours for target url and IP, but I don't get the 404. Maybe there's a transparent proxy between you and the project. Did you try a traceroute? <edit> LOL... Never mind, I missed the part where you got it working! However, as I said 5.10.7 has been working on mine. Alinator ID: 599100 · |
|
AllenIN Send message Joined: 5 Dec 00 Posts: 292 Credit: 58,297,005 RAC: 311
|
Except for the fact his last test was with 5.8.16. It was working fine on mine too, but then it started screwing up. Even 5.8.16 was giving me the same result. Suddenly everything just started working again. This is the second time that it just started working again for no good reason on my end. ID: 599126 · |
|
Alinator Send message Joined: 19 Apr 05 Posts: 4178 Credit: 4,647,982 RAC: 0
|
It was working fine on mine too, but then it started screwing up. Even 5.8.16 was giving me the same result. Suddenly everything just started working again. This is the second time that it just started working again for no good reason on my end. OK, then this is definitely starting to sound like the problem is your ISP may not be honoring the DNS TTL. I've read that some of them do that in order to reduce their overhead traffic and peering charges. One way you could test for that would be to try setting up to use a diiferent DNS server than the one(s) your ISP provides by default. You can Google for free publically available ones. If you find that you stop getting the 404, then you can be pretty sure you found the problem. ;-) HTH, Alinator ID: 599147 · |
|
AllenIN Send message Joined: 5 Dec 00 Posts: 292 Credit: 58,297,005 RAC: 311
|
It was working fine on mine too, but then it started screwing up. Even 5.8.16 was giving me the same result. Suddenly everything just started working again. This is the second time that it just started working again for no good reason on my end. That wouldn't surprise me at all. AT&T (SBC) has always had a habit of dropping or changing IP addresses whenever they feel like it and then my router is screwed until I cycle both it and the modem. It gets the new IP address and then all is well for a while. Any other odd thing that they might do doesn't surprise me in the least, but I'd rather put up with this than pay Comcast twice as much for the same service. Thanks, Allen ID: 599789 · |
©2026 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.