Unable to Update Seti@Home (No Scheduler Responded)

Author	Message
Nuwanda Send message Joined: 2 Aug 03 Posts: 71 Credit: 1,337,642 RAC: 0	Message 132162 - Posted: 3 Jul 2005, 20:12:34 UTC Here's the problem. I've read through all the other posts here. There are already 2 of them on the first page of this forum and I've tried everything people mentioned, from trying different proxies, to turning off my firewall, to "ipconfig /flushdns" and nothing seems to work. It used to happen earlier, but would normally sort itself out. But its very irritating. Also, my laptop (which shares the internet connection of this pc) has around 20 results to return for about 2 days now. This is what my messages look like : 7/3/2005 11:16:03 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/3/2005 11:16:03 PM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/3/2005 11:16:20 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/3/2005 11:16:20 PM\|SETI@home\|No schedulers responded 7/3/2005 11:16:21 PM\|SETI@home\|Deferring communication with project for 2 hours, 57 minutes, and 27 seconds 7/3/2005 11:27:24 PM\|\|request_reschedule_cpus: project op 7/3/2005 11:27:25 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/3/2005 11:27:25 PM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/3/2005 11:27:38 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/3/2005 11:27:38 PM\|SETI@home\|No schedulers responded 7/3/2005 11:27:39 PM\|SETI@home\|Deferring communication with project for 58 seconds 7/3/2005 11:28:38 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/3/2005 11:28:38 PM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/3/2005 11:29:02 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/3/2005 11:29:02 PM\|SETI@home\|No schedulers responded 7/3/2005 11:29:03 PM\|SETI@home\|Deferring communication with project for 58 seconds 7/3/2005 11:30:02 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/3/2005 11:30:02 PM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/3/2005 11:30:29 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/3/2005 11:30:29 PM\|SETI@home\|No schedulers responded 7/3/2005 11:30:30 PM\|SETI@home\|Deferring communication with project for 58 seconds 7/3/2005 11:31:29 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/3/2005 11:31:29 PM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/3/2005 11:31:44 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/3/2005 11:31:44 PM\|SETI@home\|No schedulers responded 7/3/2005 11:31:45 PM\|SETI@home\|Deferring communication with project for 58 seconds 7/3/2005 11:32:19 PM\|Pirates@Home\|Deferring communication with project for 6 days, 4 hours, 4 minutes, and 27 seconds 7/3/2005 11:32:20 PM\|\|Insufficient work; requesting more 7/3/2005 11:32:45 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/3/2005 11:32:45 PM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/3/2005 11:32:55 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/3/2005 11:32:55 PM\|SETI@home\|No schedulers responded 7/3/2005 11:32:56 PM\|SETI@home\|Deferring communication with project for 1 minutes and 54 seconds 7/3/2005 11:34:50 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/3/2005 11:34:50 PM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/3/2005 11:35:05 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/3/2005 11:35:05 PM\|SETI@home\|No schedulers responded 7/3/2005 11:35:06 PM\|SETI@home\|Deferring communication with project for 3 minutes and 58 seconds 7/3/2005 11:39:06 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/3/2005 11:39:06 PM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/3/2005 11:39:37 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/3/2005 11:39:37 PM\|SETI@home\|No schedulers responded 7/3/2005 11:39:38 PM\|SETI@home\|Deferring communication with project for 6 minutes and 26 seconds 7/3/2005 11:46:05 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/3/2005 11:46:05 PM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/3/2005 11:46:30 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/3/2005 11:46:30 PM\|SETI@home\|No schedulers responded 7/3/2005 11:46:31 PM\|SETI@home\|Deferring communication with project for 24 minutes and 52 seconds 7/4/2005 12:11:24 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 12:11:24 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 12:11:40 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 12:11:40 AM\|SETI@home\|No schedulers responded 7/4/2005 12:11:41 AM\|SETI@home\|Deferring communication with project for 1 hours, 38 minutes, and 37 seconds 7/4/2005 12:32:19 AM\|Pirates@Home\|Deferring communication with project for 6 days, 3 hours, 4 minutes, and 26 seconds 7/4/2005 12:32:21 AM\|\|Insufficient work; requesting more 7/4/2005 12:38:04 AM\|\|request_reschedule_cpus: project op 7/4/2005 12:38:05 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 12:38:05 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 12:38:21 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 12:38:21 AM\|SETI@home\|No schedulers responded 7/4/2005 12:38:22 AM\|SETI@home\|Deferring communication with project for 3 hours, 52 minutes, and 42 seconds 7/4/2005 12:38:27 AM\|\|request_reschedule_cpus: project op 7/4/2005 12:38:27 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 12:38:27 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 12:38:59 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 12:38:59 AM\|SETI@home\|No schedulers responded 7/4/2005 12:39:01 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 12:40:00 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 12:40:00 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 12:40:31 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 12:40:31 AM\|SETI@home\|No schedulers responded 7/4/2005 12:40:33 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 12:40:45 AM\|\|request_reschedule_cpus: project op 7/4/2005 12:40:46 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 12:40:46 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 12:41:32 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 12:41:32 AM\|SETI@home\|No schedulers responded 7/4/2005 12:41:33 AM\|SETI@home\|Deferring communication with project for 59 seconds 7/4/2005 12:42:32 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 12:42:32 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 12:43:12 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 12:43:12 AM\|SETI@home\|No schedulers responded 7/4/2005 12:43:13 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 12:44:13 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 12:44:13 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 12:44:44 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 12:44:44 AM\|SETI@home\|No schedulers responded 7/4/2005 12:44:45 AM\|SETI@home\|Deferring communication with project for 59 seconds 7/4/2005 12:45:45 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 12:45:45 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 12:46:51 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 12:46:51 AM\|SETI@home\|No schedulers responded 7/4/2005 12:46:52 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 12:47:52 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 12:47:52 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 12:48:30 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 12:48:30 AM\|SETI@home\|No schedulers responded 7/4/2005 12:48:31 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 12:49:30 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 12:49:30 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 12:50:12 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 12:50:12 AM\|SETI@home\|No schedulers responded 7/4/2005 12:50:13 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 12:51:12 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 12:51:12 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 12:52:01 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 12:52:01 AM\|SETI@home\|No schedulers responded 7/4/2005 12:52:02 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 12:53:02 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 12:53:02 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 12:53:34 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 12:53:34 AM\|SETI@home\|No schedulers responded 7/4/2005 12:53:35 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 12:54:34 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 12:54:34 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 12:55:12 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 12:55:12 AM\|SETI@home\|No schedulers responded 7/4/2005 12:55:13 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 12:56:12 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 12:56:12 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 12:56:44 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 12:56:44 AM\|SETI@home\|No schedulers responded 7/4/2005 12:56:45 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 12:57:44 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 12:57:44 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 12:58:27 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 12:58:27 AM\|SETI@home\|No schedulers responded 7/4/2005 12:58:28 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 12:59:28 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 12:59:28 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:00:16 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:00:16 AM\|SETI@home\|No schedulers responded 7/4/2005 1:00:17 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:01:03 AM\|\|request_reschedule_cpus: project op 7/4/2005 1:01:04 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:01:04 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:01:53 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:01:53 AM\|SETI@home\|No schedulers responded 7/4/2005 1:01:54 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:02:53 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:02:53 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:03:34 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:03:34 AM\|SETI@home\|No schedulers responded 7/4/2005 1:03:35 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:04:34 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:04:34 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:04:57 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:04:57 AM\|SETI@home\|No schedulers responded 7/4/2005 1:04:58 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:05:57 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:05:57 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:06:45 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:06:45 AM\|SETI@home\|No schedulers responded 7/4/2005 1:06:46 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:07:38 AM\|\|request_reschedule_cpus: project op 7/4/2005 1:07:38 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:07:38 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:08:00 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:08:00 AM\|SETI@home\|No schedulers responded 7/4/2005 1:08:01 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:09:01 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:09:01 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:09:23 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:09:23 AM\|SETI@home\|No schedulers responded 7/4/2005 1:09:24 AM\|SETI@home\|Deferring communication with project for 59 seconds 7/4/2005 1:10:24 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:10:24 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:10:45 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:10:45 AM\|SETI@home\|No schedulers responded 7/4/2005 1:10:47 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:11:45 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:11:45 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:12:07 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:12:07 AM\|SETI@home\|No schedulers responded 7/4/2005 1:12:08 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:13:08 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:13:08 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:13:22 AM\|\|request_reschedule_cpus: project op 7/4/2005 1:13:30 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:13:30 AM\|SETI@home\|No schedulers responded 7/4/2005 1:13:31 AM\|SETI@home\|Deferring communication with project for 59 seconds 7/4/2005 1:14:31 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:14:31 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:15:19 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:15:19 AM\|SETI@home\|No schedulers responded 7/4/2005 1:15:20 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:16:19 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:16:19 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:17:04 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:17:04 AM\|SETI@home\|No schedulers responded 7/4/2005 1:17:05 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:18:04 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:18:04 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:18:42 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:18:42 AM\|SETI@home\|No schedulers responded 7/4/2005 1:18:43 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:19:43 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:19:43 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:20:41 AM\|\|request_reschedule_cpus: project op 7/4/2005 1:20:54 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:20:54 AM\|SETI@home\|No schedulers responded 7/4/2005 1:20:56 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:21:31 AM\|\|request_reschedule_cpus: project op 7/4/2005 1:21:32 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:21:32 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:22:00 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:22:00 AM\|SETI@home\|No schedulers responded 7/4/2005 1:22:01 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:22:14 AM\|\|request_reschedule_cpus: project op 7/4/2005 1:22:14 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:22:14 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:24:25 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:24:25 AM\|SETI@home\|No schedulers responded 7/4/2005 1:24:26 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:25:25 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:25:25 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:26:24 AM\|\|request_reschedule_cpus: project op 7/4/2005 1:29:27 AM\|\|request_reschedule_cpus: project op 7/4/2005 1:32:37 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:32:37 AM\|SETI@home\|No schedulers responded 7/4/2005 1:32:38 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:32:38 AM\|\|Insufficient work; requesting more 7/4/2005 1:32:38 AM\|Pirates@Home\|Deferring communication with project for 6 days, 2 hours, 4 minutes, and 8 seconds 7/4/2005 1:33:37 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:33:37 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:33:46 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:33:46 AM\|SETI@home\|No schedulers responded 7/4/2005 1:33:47 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:34:46 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:34:46 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:35:04 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:35:04 AM\|SETI@home\|No schedulers responded 7/4/2005 1:35:05 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:36:05 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:36:05 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results 7/4/2005 1:36:49 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/4/2005 1:36:49 AM\|SETI@home\|No schedulers responded 7/4/2005 1:36:50 AM\|SETI@home\|Deferring communication with project for 58 seconds 7/4/2005 1:37:45 AM\|\|request_reschedule_cpus: project op 7/4/2005 1:37:45 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 7/4/2005 1:37:45 AM\|SETI@home\|Requesting 0 seconds of work, returning 4 results Please help me out... Sorry for creating a new thread, but the other one was getting too long. You guys can continue discussions here. Thanks. ID: 132162 ·

SURVEYOR Volunteer tester Send message Joined: 19 Oct 02 Posts: 375 Credit: 608,422 RAC: 0	Message 132163 - Posted: 3 Jul 2005, 20:16:54 UTC what boinc version are you using? Fred BOINC Alpha, BOINC Beta, LHC Alpha, Einstein Alpha ID: 132163 ·

dave015702 Send message Joined: 13 Feb 05 Posts: 271 Credit: 2,341 RAC: 0	Message 132182 - Posted: 3 Jul 2005, 21:10:44 UTC - in response to Message 132163. Have you tried rebooting? What happens if you run tracert setiboinc.ssl.berkeley.edu from a command prompt? Help and BOINC documentation is available here. ID: 132182 ·

Nuwanda Send message Joined: 2 Aug 03 Posts: 71 Credit: 1,337,642 RAC: 0	Message 132332 - Posted: 4 Jul 2005, 3:56:36 UTC Last modified: 4 Jul 2005, 4:00:04 UTC I'm using the optimized boinc client and seti app with boinc mgr 4.45. I did try rebooting, but that didnt really help. Tracert works fine, trace completes uptil 66.28.250.124. Any ideas? ID: 132332 ·

The Gas Giant Volunteer tester Send message Joined: 22 Nov 01 Posts: 1904 Credit: 2,646,654 RAC: 0	Message 132353 - Posted: 4 Jul 2005, 5:11:19 UTC Nuwanda. I have exactly the same problem. So far the only way I can report the results back (uploads work OK) is by using a proxy. Some proxies can be found here -> http://www.iantighe.com/boincers.htm I hope this helps a little and if you overcome your problem please let us know how you did it. Live long and crunch. Paul (S@H1 8888) And proud of it! ID: 132353 ·

cjsoftuk Volunteer tester Send message Joined: 3 Sep 04 Posts: 248 Credit: 183,721 RAC: 0	Message 132358 - Posted: 4 Jul 2005, 5:19:39 UTC Me thinks, somebody cut the cables again! ID: 132358 ·

MattDavis Volunteer tester Send message Joined: 11 Nov 99 Posts: 919 Credit: 934,161 RAC: 0	Message 132359 - Posted: 4 Jul 2005, 5:28:40 UTC - in response to Message 132358. Me thinks, somebody cut the cables again! I use 4.45 and I just downloaded a unit without problems. Maybe it's because yours is optimized and mine is from the website. ----- ID: 132359 ·

Mike Volunteer tester Send message Joined: 17 Feb 01 Posts: 34258 Credit: 79,922,639 RAC: 80	Message 132434 - Posted: 4 Jul 2005, 13:20:07 UTC Hi IÂ´m using optimized 4.45 client and uploaded 40 results on three machines yet without any problems. IÂ´m for sure the optimized clients doesnÂ´t affect this. greetz Mike With each crime and every kindness we birth our future. ID: 132434 ·

hallen Send message Joined: 12 Jan 02 Posts: 13 Credit: 226,506 RAC: 0	Message 132489 - Posted: 4 Jul 2005, 17:14:55 UTC Clients get put on ignore by the scheduler when they stray from the work profile maintained by Seti 2. There isn't much you can do about it but turn off the computer so you don't waste time and money. Dial up is more prone to being ignored because of the varibility in connecting. Wait a day and try again. If you are really pressed, save the BOINC directory and start another from scratch then ping pong back and forth from time to time. It is a pain and a waste of your time but hey, the developers give you what you paid, nothing. <br><img src="http://boinc.mundayweb.com/one/stats.php/userID:1726/prj:1"> ID: 132489 ·

Skip Da Shu Volunteer tester Send message Joined: 28 Jun 04 Posts: 233 Credit: 431,047 RAC: 0	Message 132496 - Posted: 4 Jul 2005, 17:39:30 UTC - in response to Message 132332. I'm using the optimized boinc client and seti app with boinc mgr 4.45. I did try rebooting, but that didnt really help. Tracert works fine, trace completes uptil 66.28.250.124. Any ideas? What about other projects? What are they doing? ID: 132496 ·

dave015702 Send message Joined: 13 Feb 05 Posts: 271 Credit: 2,341 RAC: 0	Message 132513 - Posted: 4 Jul 2005, 18:38:42 UTC - in response to Message 132489. Clients get put on ignore by the scheduler when they stray from the work profile maintained by Seti 2. I don't understand what you're talking about. What "work profile"? Help and BOINC documentation is available here. ID: 132513 ·

Tigher Volunteer tester Send message Joined: 18 Mar 04 Posts: 1547 Credit: 760,577 RAC: 0	Message 132527 - Posted: 4 Jul 2005, 19:29:21 UTC @Nuwanda Hi. I noticed you are failing to talk to Pirates also......? As you seem to be able to tracert OK I guess its something your end tbh. Firewall perhaps......drop the firewall and try it. ID: 132527 ·

SURVEYOR Volunteer tester Send message Joined: 19 Oct 02 Posts: 375 Credit: 608,422 RAC: 0	Message 132529 - Posted: 4 Jul 2005, 19:33:10 UTC pirates@home project is discontinue. Fred BOINC Alpha, BOINC Beta, LHC Alpha, Einstein Alpha ID: 132529 ·

Urs Echternacht Volunteer tester Send message Joined: 15 May 99 Posts: 692 Credit: 135,197,781 RAC: 211	Message 132577 - Posted: 4 Jul 2005, 22:18:12 UTC Last modified: 4 Jul 2005, 22:18:53 UTC @Nuwanda Hi. I had (and sometimes still have) the same problem you described. A week ago it was even worse. But some errors to this issue (error 500) seem to be occurring no longer here. Reporting is still a pain on two of my hosts. Be patient, maybe the next version of BOINC will not have these problems anymore. _\\|/_ U r s ID: 132577 ·

The Gas Giant Volunteer tester Send message Joined: 22 Nov 01 Posts: 1904 Credit: 2,646,654 RAC: 0	Message 132590 - Posted: 4 Jul 2005, 23:01:50 UTC - in response to Message 132489. Clients get put on ignore by the scheduler when they stray from the work profile maintained by Seti 2. There isn't much you can do about it but turn off the computer so you don't waste time and money. Dial up is more prone to being ignored because of the varibility in connecting. Wait a day and try again. If you are really pressed, save the BOINC directory and start another from scratch then ping pong back and forth from time to time. It is a pain and a waste of your time but hey, the developers give you what you paid, nothing. What on earth are you talking about! I've been crunching BOINC nearing 2 yrs and this is the first I've heard of this. Are you talking about the max wu's/day setting? For me all other projects work fine. I just have trouble contacting the scheduler at SETI and the only way it will work for me is to connect via a proxy and not use the same proxy for more than a day at a time. Me thinks Berkeley don't like me....lol. Paul. ID: 132590 ·

Nuwanda Send message Joined: 2 Aug 03 Posts: 71 Credit: 1,337,642 RAC: 0	Message 133350 - Posted: 6 Jul 2005, 13:17:13 UTC Sorry for not replying the last couple of days. Had cable problems (but thats not what caused the errors i'm sure). Anyway, since my computer has not contacted the project in nearly 2 days, i'm positive its no client ignore thing. i haven't tried any other projects and since pirate is down, that doesnt show anything. I'll try another project which i signed up for previously. The funny part is the computer which is connected to the internet directly works fine sometimes...for the most part it wont connect but every 1-2 days it will manage to upload and download wu's but my laptop which shares this connection won't update itself. Its uploaded all the 27 results, but it just shows as ready to report with the 'No Schedulers Responded' error...i got till the 10th to figure this out or i loose all credit for those :( ID: 133350 ·

Pascal, K G Volunteer tester Send message Joined: 3 Apr 99 Posts: 2343 Credit: 150,491 RAC: 0	Message 133363 - Posted: 6 Jul 2005, 15:54:16 UTC - in response to Message 132489. Clients get put on ignore by the scheduler when they stray from the work profile maintained by Seti 2. There isn't much you can do about it but turn off the computer so you don't waste time and money. Dial up is more prone to being ignored because of the varibility in connecting. Wait a day and try again. If you are really pressed, save the BOINC directory and start another from scratch then ping pong back and forth from time to time. It is a pain and a waste of your time but hey, the developers give you what you paid, nothing. Can you say conspiracy theory. I am forever fascinated by the people who try to put the square peg into the round hole, and blame their failure to do so on the hole..... Semper Eadem So long Paul, it has been a hell of a ride. Park your ego's, fire up the computers, Science YES, Credits No. ID: 133363 ·

Urs Echternacht Volunteer tester Send message Joined: 15 May 99 Posts: 692 Credit: 135,197,781 RAC: 211	Message 133381 - Posted: 6 Jul 2005, 16:48:40 UTC - in response to Message 133350. ... The funny part is the computer which is connected to the internet directly works fine sometimes...for the most part it wont connect but every 1-2 days it will manage to upload and download wu's but my laptop which shares this connection won't update itself. Its uploaded all the 27 results, but it just shows as ready to report with the 'No Schedulers Responded' error...i got till the 10th to figure this out or i loose all credit for those :( @Nuwanda: Hi. Have you tried to connect your laptop directly ? Maybe the connection-sharing is a problem in your case. _\\|/_ U r s ID: 133381 ·

Paul D. Buck Volunteer tester Send message Joined: 19 Jul 00 Posts: 3898 Credit: 1,158,042 RAC: 0	Message 133428 - Posted: 6 Jul 2005, 22:14:27 UTC IF you are using DHCP and attach and detach the computers, they could both be trying to use the same IP Address. If that is the case, you will see problems like this ... ID: 133428 ·

Urs Echternacht Volunteer tester Send message Joined: 15 May 99 Posts: 692 Credit: 135,197,781 RAC: 211	Message 134012 - Posted: 7 Jul 2005, 23:28:25 UTC Hi. Error 500 is back after the last outage. Three hosts starving for new work (in about a day). Rom, you got email. _\\|/_ U r s ID: 134012 ·

©2024 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.