No work units from Einstein

Tern
Tern
Joined: 27 Jul 05
Posts: 309
Credit: 93405878
RAC: 137

RE: I'm also not receiving

Message 21783 in response to message 21781

Quote:

I'm also not receiving work from Eistein, but I think mine is a time debt issue. A few days ago when I increased my work queue to 3 days instead of .5 days Rosetta was the first to respond and sent me about 30 work units while the other projects only sent me 2-3 (Even though SETI is my largest resource share).

Now only SETI is accepting new work

Yep - going from .5 to 3 in "one jump", the first project got 3 days worth of work (resource share is NOT considered in work fetch...) then you had enough work on the computer to stay busy, so the other projects didn't need as much. This meant you did more Rosetta, and apparently Einstein, than you "should have" per resource share, so now it's letting SETI catch up.

Nothing But Idle Time
Nothing But Idl...
Joined: 24 Aug 05
Posts: 158
Credit: 289204
RAC: 0

RE: (resource share is NOT

Message 21784 in response to message 21783

Quote:
(resource share is NOT considered in work fetch)

Is this known as a "feature" in system design parlance? Ignoring resource share when requesting new work is a huge oversight IMO; why fill up your queue entirely w/one project?

Tern
Tern
Joined: 27 Jul 05
Posts: 309
Credit: 93405878
RAC: 137

RE: Is this known as a

Message 21785 in response to message 21784

Quote:
Is this known as a "feature" in system design parlance? Ignoring resource share when requesting new work is a huge oversight IMO; why fill up your queue entirely w/one project?

Um... it's actually known as a "bug". Seems like at one point the calculation was done on the client, it was moved to the server and taken out of the client, then somehow was taken off of the server... (or vice-versa, working from memory here). Everyone on both ends "knew" it was being done by the other end, and the complaints were just from people who didn't understand what was happening. Someone finally looked at the code (gravywavy?) and said "wait a minute" (comment said "removed here, done there", but other end didn't), and the devs realized "oops". It's on the list now to be fixed.

Rush
Rush
Joined: 6 Mar 05
Posts: 43
Credit: 185361
RAC: 0

OK all, am I missing

OK all, am I missing something here? Einstein ain't downloading any new work, it's been like 48 hours now. I've checked the FAQs and settings, am I not seeing the obvious?

1/4/2006 4:37:33 PM||Starting BOINC client version 5.2.11 for windows_intelx86
1/4/2006 4:37:33 PM||libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
1/4/2006 4:37:33 PM||Data directory: C:\\Program Files\\BOINC
1/4/2006 4:37:34 PM|Einstein@Home|Found app_info.xml; using anonymous platform
1/4/2006 4:37:34 PM|SETI@home|Found app_info.xml; using anonymous platform
1/4/2006 4:37:36 PM||Processor: 1 GenuineIntel Intel(R) Pentium(R) M processor 1500MHz
1/4/2006 4:37:36 PM||Memory: 1022.92 MB physical, 2.40 GB virtual
1/4/2006 4:37:36 PM||Disk: 34.25 GB total, 14.49 GB free
1/4/2006 4:37:36 PM|Einstein@Home|Computer ID: 460285; location: school; project prefs: default
1/4/2006 4:37:36 PM|SETI@home|Computer ID: 1710222; location: school; project prefs: default
1/4/2006 4:37:37 PM||General prefs: from SETI@home (last modified 2005-12-15 08:46:32)
1/4/2006 4:37:37 PM||General prefs: using separate prefs for school
1/4/2006 4:37:38 PM||Remote control not allowed; using loopback address
1/4/2006 4:37:38 PM|SETI@home|Resuming computation for result 19mr05aa.25423.10385.692336.1.178_2 using setiathome version 418
1/4/2006 4:37:40 PM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
1/4/2006 4:37:40 PM|Einstein@Home|Reason: To fetch work
1/4/2006 4:37:40 PM|Einstein@Home|Requesting 43200 seconds of new work
1/4/2006 4:37:43 PM||Couldn't resolve hostname [einstein.phys.uwm.edu]
1/4/2006 4:37:44 PM|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed with a return value of -113
1/4/2006 4:37:44 PM|Einstein@Home|No schedulers responded
1/4/2006 4:37:49 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
1/4/2006 4:37:49 PM|SETI@home|Reason: To fetch work
1/4/2006 4:37:49 PM|SETI@home|Requesting 5788 seconds of new work
1/4/2006 4:37:51 PM||Couldn't resolve hostname [setiboinc.ssl.berkeley.edu]
1/4/2006 4:37:54 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -113
1/4/2006 4:37:54 PM|SETI@home|No schedulers responded
1/4/2006 4:38:44 PM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
1/4/2006 4:38:44 PM|Einstein@Home|Reason: To fetch work
1/4/2006 4:38:44 PM|Einstein@Home|Requesting 43200 seconds of new work
1/4/2006 4:38:54 PM|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
1/4/2006 4:38:54 PM|Einstein@Home|Message from server: No work sent
1/4/2006 4:38:54 PM|Einstein@Home|No work from project
1/4/2006 4:39:09 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
1/4/2006 4:39:09 PM|SETI@home|Reason: To fetch work
1/4/2006 4:39:09 PM|SETI@home|Requesting 6057 seconds of new work
1/4/2006 4:39:43 PM||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
1/4/2006 4:39:44 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
1/4/2006 4:39:44 PM|SETI@home|No schedulers responded
1/4/2006 4:42:39 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
1/4/2006 4:42:39 PM|SETI@home|Reason: To fetch work
1/4/2006 4:42:39 PM|SETI@home|Requesting 6815 seconds of new work
1/4/2006 4:43:03 PM||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
1/4/2006 4:43:05 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
1/4/2006 4:43:05 PM|SETI@home|No schedulers responded
1/4/2006 4:55:26 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
1/4/2006 4:55:26 PM|SETI@home|Reason: To fetch work
1/4/2006 4:55:26 PM|SETI@home|Requesting 9310 seconds of new work
1/4/2006 4:55:48 PM||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
1/4/2006 4:55:51 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
1/4/2006 4:55:51 PM|SETI@home|No schedulers responded
1/4/2006 4:58:39 PM||request_reschedule_cpus: process exited
1/4/2006 4:58:39 PM|SETI@home|Computation for result 19mr05aa.25423.10385.692336.1.178_2 finished
1/4/2006 4:58:39 PM|SETI@home|Starting result 04mr05ab.21948.5489.142324.1.36_1 using setiathome version 418
1/4/2006 4:58:41 PM|SETI@home|Started upload of 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 4:59:07 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 4:59:07 PM|SETI@home|Temporarily failed upload of 19mr05aa.25423.10385.692336.1.178_2_0: system I/O
1/4/2006 4:59:07 PM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 5:00:07 PM|SETI@home|Started upload of 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 5:00:30 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:00:30 PM|SETI@home|Temporarily failed upload of 19mr05aa.25423.10385.692336.1.178_2_0: system I/O
1/4/2006 5:00:30 PM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 5:00:34 PM||request_reschedule_cpus: process exited
1/4/2006 5:00:34 PM|SETI@home|Computation for result 04mr05ab.21948.5489.142324.1.36_1 finished
1/4/2006 5:00:34 PM|SETI@home|Starting result 17mr05aa.29591.2240.722160.1.191_1 using setiathome version 418
1/4/2006 5:00:36 PM|SETI@home|Started upload of 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:00:58 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:00:58 PM|SETI@home|Temporarily failed upload of 04mr05ab.21948.5489.142324.1.36_1_0: system I/O
1/4/2006 5:00:58 PM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:01:30 PM|SETI@home|Started upload of 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 5:01:53 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:01:53 PM|SETI@home|Temporarily failed upload of 19mr05aa.25423.10385.692336.1.178_2_0: system I/O
1/4/2006 5:01:53 PM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 5:01:58 PM|SETI@home|Started upload of 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:02:20 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:02:20 PM|SETI@home|Temporarily failed upload of 04mr05ab.21948.5489.142324.1.36_1_0: system I/O
1/4/2006 5:02:20 PM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:02:54 PM|SETI@home|Started upload of 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 5:03:17 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:03:17 PM|SETI@home|Temporarily failed upload of 19mr05aa.25423.10385.692336.1.178_2_0: system I/O
1/4/2006 5:03:17 PM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 5:03:20 PM|SETI@home|Started upload of 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:03:42 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:03:42 PM|SETI@home|Temporarily failed upload of 04mr05ab.21948.5489.142324.1.36_1_0: system I/O
1/4/2006 5:03:42 PM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:04:17 PM|SETI@home|Started upload of 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 5:04:32 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
1/4/2006 5:04:32 PM|SETI@home|Reason: To fetch work
1/4/2006 5:04:32 PM|SETI@home|Requesting 32470 seconds of new work
1/4/2006 5:04:38 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:04:38 PM|SETI@home|Temporarily failed upload of 19mr05aa.25423.10385.692336.1.178_2_0: system I/O
1/4/2006 5:04:38 PM|SETI@home|Backing off 1 minutes and 56 seconds on upload of file 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 5:04:42 PM|SETI@home|Started upload of 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:04:55 PM||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
1/4/2006 5:04:57 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
1/4/2006 5:04:57 PM|SETI@home|No schedulers responded
1/4/2006 5:05:05 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:05:05 PM|SETI@home|Temporarily failed upload of 04mr05ab.21948.5489.142324.1.36_1_0: system I/O
1/4/2006 5:05:05 PM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:06:05 PM|SETI@home|Started upload of 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:06:27 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:06:27 PM|SETI@home|Temporarily failed upload of 04mr05ab.21948.5489.142324.1.36_1_0: system I/O
1/4/2006 5:06:27 PM|SETI@home|Backing off 1 minutes and 21 seconds on upload of file 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:06:35 PM|SETI@home|Started upload of 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 5:06:45 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:06:45 PM|SETI@home|Temporarily failed upload of 19mr05aa.25423.10385.692336.1.178_2_0: system I/O
1/4/2006 5:06:45 PM|SETI@home|Backing off 4 minutes and 0 seconds on upload of file 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 5:07:50 PM|SETI@home|Started upload of 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:08:13 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:08:13 PM|SETI@home|Temporarily failed upload of 04mr05ab.21948.5489.142324.1.36_1_0: system I/O
1/4/2006 5:08:13 PM|SETI@home|Backing off 3 minutes and 54 seconds on upload of file 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:10:46 PM|SETI@home|Started upload of 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 5:11:07 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:11:08 PM|SETI@home|Temporarily failed upload of 19mr05aa.25423.10385.692336.1.178_2_0: system I/O
1/4/2006 5:11:08 PM|SETI@home|Backing off 14 minutes and 19 seconds on upload of file 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 5:12:07 PM|SETI@home|Started upload of 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:12:29 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:12:29 PM|SETI@home|Temporarily failed upload of 04mr05ab.21948.5489.142324.1.36_1_0: system I/O
1/4/2006 5:12:29 PM|SETI@home|Backing off 7 minutes and 54 seconds on upload of file 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:20:24 PM|SETI@home|Started upload of 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:20:47 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:20:47 PM|SETI@home|Temporarily failed upload of 04mr05ab.21948.5489.142324.1.36_1_0: system I/O
1/4/2006 5:20:47 PM|SETI@home|Backing off 20 minutes and 20 seconds on upload of file 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:25:28 PM|SETI@home|Started upload of 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 5:25:51 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:25:51 PM|SETI@home|Temporarily failed upload of 19mr05aa.25423.10385.692336.1.178_2_0: system I/O
1/4/2006 5:25:51 PM|SETI@home|Backing off 23 minutes and 22 seconds on upload of file 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 5:38:56 PM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
1/4/2006 5:38:56 PM|Einstein@Home|Reason: To fetch work
1/4/2006 5:38:56 PM|Einstein@Home|Requesting 43200 seconds of new work
1/4/2006 5:39:01 PM|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
1/4/2006 5:39:01 PM|Einstein@Home|Message from server: No work sent
1/4/2006 5:39:01 PM|Einstein@Home|No work from project
1/4/2006 5:41:08 PM|SETI@home|Started upload of 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:41:25 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:41:25 PM|SETI@home|Temporarily failed upload of 04mr05ab.21948.5489.142324.1.36_1_0: system I/O
1/4/2006 5:41:25 PM|SETI@home|Backing off 2 hours, 8 minutes, and 18 seconds on upload of file 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 5:49:14 PM|SETI@home|Started upload of 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 5:49:36 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 5:49:36 PM|SETI@home|Temporarily failed upload of 19mr05aa.25423.10385.692336.1.178_2_0: system I/O
1/4/2006 5:49:36 PM|SETI@home|Backing off 45 minutes and 45 seconds on upload of file 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 6:07:17 PM||request_reschedule_cpus: process exited
1/4/2006 6:07:17 PM|SETI@home|Computation for result 17mr05aa.29591.2240.722160.1.191_1 finished
1/4/2006 6:07:19 PM|SETI@home|Started upload of 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 6:07:42 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 6:07:42 PM|SETI@home|Temporarily failed upload of 17mr05aa.29591.2240.722160.1.191_1_0: system I/O
1/4/2006 6:07:42 PM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 6:08:42 PM|SETI@home|Started upload of 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 6:09:04 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 6:09:04 PM|SETI@home|Temporarily failed upload of 17mr05aa.29591.2240.722160.1.191_1_0: system I/O
1/4/2006 6:09:04 PM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 6:10:04 PM|SETI@home|Started upload of 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 6:10:27 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 6:10:27 PM|SETI@home|Temporarily failed upload of 17mr05aa.29591.2240.722160.1.191_1_0: system I/O
1/4/2006 6:10:27 PM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 6:11:27 PM|SETI@home|Started upload of 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 6:11:50 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 6:11:50 PM|SETI@home|Temporarily failed upload of 17mr05aa.29591.2240.722160.1.191_1_0: system I/O
1/4/2006 6:11:50 PM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 6:12:50 PM|SETI@home|Started upload of 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 6:13:13 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 6:13:13 PM|SETI@home|Temporarily failed upload of 17mr05aa.29591.2240.722160.1.191_1_0: system I/O
1/4/2006 6:13:13 PM|SETI@home|Backing off 1 minutes and 19 seconds on upload of file 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 6:14:33 PM|SETI@home|Started upload of 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 6:14:55 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 6:14:55 PM|SETI@home|Temporarily failed upload of 17mr05aa.29591.2240.722160.1.191_1_0: system I/O
1/4/2006 6:14:55 PM|SETI@home|Backing off 4 minutes and 32 seconds on upload of file 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 6:19:29 PM|SETI@home|Started upload of 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 6:19:50 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 6:19:50 PM|SETI@home|Temporarily failed upload of 17mr05aa.29591.2240.722160.1.191_1_0: system I/O
1/4/2006 6:19:50 PM|SETI@home|Backing off 9 minutes and 5 seconds on upload of file 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 6:28:57 PM|SETI@home|Started upload of 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 6:29:20 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 6:29:20 PM|SETI@home|Temporarily failed upload of 17mr05aa.29591.2240.722160.1.191_1_0: system I/O
1/4/2006 6:29:20 PM|SETI@home|Backing off 34 minutes and 34 seconds on upload of file 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 6:35:22 PM|SETI@home|Started upload of 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 6:35:44 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 6:35:45 PM|SETI@home|Temporarily failed upload of 19mr05aa.25423.10385.692336.1.178_2_0: system I/O
1/4/2006 6:35:45 PM|SETI@home|Backing off 1 hours, 26 minutes, and 36 seconds on upload of file 19mr05aa.25423.10385.692336.1.178_2_0
1/4/2006 6:39:01 PM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
1/4/2006 6:39:01 PM|Einstein@Home|Reason: To fetch work
1/4/2006 6:39:01 PM|Einstein@Home|Requesting 43200 seconds of new work
1/4/2006 6:39:12 PM|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
1/4/2006 6:39:12 PM|Einstein@Home|Message from server: No work sent
1/4/2006 6:39:12 PM|Einstein@Home|No work from project
1/4/2006 7:03:55 PM|SETI@home|Started upload of 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 7:04:18 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 7:04:18 PM|SETI@home|Temporarily failed upload of 17mr05aa.29591.2240.722160.1.191_1_0: system I/O
1/4/2006 7:04:18 PM|SETI@home|Backing off 43 minutes and 24 seconds on upload of file 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 7:19:25 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
1/4/2006 7:19:25 PM|SETI@home|Reason: To fetch work
1/4/2006 7:19:25 PM|SETI@home|Requesting 43200 seconds of new work
1/4/2006 7:19:46 PM||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
1/4/2006 7:19:50 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
1/4/2006 7:19:50 PM|SETI@home|No schedulers responded
1/4/2006 7:39:12 PM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
1/4/2006 7:39:12 PM|Einstein@Home|Reason: To fetch work
1/4/2006 7:39:12 PM|Einstein@Home|Requesting 43200 seconds of new work
1/4/2006 7:39:17 PM|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
1/4/2006 7:39:17 PM|Einstein@Home|Message from server: No work sent
1/4/2006 7:39:17 PM|Einstein@Home|No work from project
1/4/2006 7:47:43 PM|SETI@home|Started upload of 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 7:48:06 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 7:48:06 PM|SETI@home|Temporarily failed upload of 17mr05aa.29591.2240.722160.1.191_1_0: system I/O
1/4/2006 7:48:06 PM|SETI@home|Backing off 1 hours, 24 minutes, and 41 seconds on upload of file 17mr05aa.29591.2240.722160.1.191_1_0
1/4/2006 7:49:45 PM|SETI@home|Started upload of 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 7:50:08 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
1/4/2006 7:50:08 PM|SETI@home|Temporarily failed upload of 04mr05ab.21948.5489.142324.1.36_1_0: system I/O
1/4/2006 7:50:08 PM|SETI@home|Backing off 3 hours, 27 minutes, and 5 seconds on upload of file 04mr05ab.21948.5489.142324.1.36_1_0
1/4/2006 7:57:15 PM||Suspending computation and network activity - user is active

Cordially,
Rush

elrushbo-[at]-theobviousadelphia.net
Remove the obvious...

Chipper Q
Chipper Q
Joined: 20 Feb 05
Posts: 1540
Credit: 708571
RAC: 0

I haven't been getting any

I haven't been getting any work either. I noticed the E@H LHO and LLO work generators haven't been running for the past few days (checking the server status page). What happened??

Michael Karlinsky
Michael Karlinsky
Joined: 22 Jan 05
Posts: 888
Credit: 23502182
RAC: 0

RE: 1/4/2006 4:37:34

Quote:

1/4/2006 4:37:34 PM|SETI@home|Found app_info.xml; using anonymous platform

You probably need to remove app_info.xml.

Michael

Tern
Tern
Joined: 27 Jul 05
Posts: 309
Credit: 93405878
RAC: 137

RE: RE: 1/4/2006 4:37:34

Message 21789 in response to message 21788

Quote:
Quote:

1/4/2006 4:37:34 PM|SETI@home|Found app_info.xml; using anonymous platform

You probably need to remove app_info.xml.

What? NO - NO - NO! DO NOT REMOVE APP_INFO.XML!

That message is from SETI and says you're running an optimized app there. Is not related to Einstein.

Looking further, you have the same message _from_ Einstein, which means you're running a 'beta' version there - which means you will not get the "Albert" WUs, so you _will_ need to delete _that_ app_info.xml file WHEN the project says to.

The connection failures you're showing are for multiple projects, so I would suspect something on your end; firewall, network hardware, etc.

Michael Karlinsky
Michael Karlinsky
Joined: 22 Jan 05
Posts: 888
Credit: 23502182
RAC: 0

RE: What? NO - NO - NO! DO

Message 21790 in response to message 21789

Quote:

What? NO - NO - NO! DO NOT REMOVE APP_INFO.XML!

D'oh! This was meant to be a reply to Chippers post.

Just wanted to quote something...

Michael

Chipper Q
Chipper Q
Joined: 20 Feb 05
Posts: 1540
Credit: 708571
RAC: 0

RE: RE: RE: 1/4/2006

Message 21791 in response to message 21789

Quote:
Quote:
Quote:

1/4/2006 4:37:34 PM|SETI@home|Found app_info.xml; using anonymous platform

You probably need to remove app_info.xml.

What? NO - NO - NO! DO NOT REMOVE APP_INFO.XML!

That message is from SETI and says you're running an optimized app there. Is not related to Einstein.

Looking further, you have the same message _from_ Einstein, which means you're running a 'beta' version there - which means you will not get the "Albert" WUs, so you _will_ need to delete _that_ app_info.xml file WHEN the project says to.

The connection failures you're showing are for multiple projects, so I would suspect something on your end; firewall, network hardware, etc.


Thanks Bill, Michael. The gateway router for the lan I'm on is acting froggy, but there's a web server and at least one fixed IP address going through it too, so I've got some work to do to figure all that out. I've seen requests to delete WUs before and I thought you didn't have to do anything - BOINC would handle it. So am I supposed to be looking for a request to delete app_info.xml?

Michael Karlinsky
Michael Karlinsky
Joined: 22 Jan 05
Posts: 888
Credit: 23502182
RAC: 0

RE: So am I supposed to be

Message 21792 in response to message 21791

Quote:
So am I supposed to be looking for a request to delete app_info.xml?

AFAIK you have to delete the app_info.xml from the Einstein directory manually
before the scheduler sends you the Albert application and new WUs. The Einstein
work generators are offline, so I suspect there will be no new work for
the Einstein application.

Correct me if I'am wrong.

Michael

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.