Mon 02 Jan 2006 01:45:20 AM CET|Einstein@Home|signature verification failed for albert_4.38_i686-pc-linux-gnu
Mon 02 Jan 2006 01:45:20 AM CET|Einstein@Home|Checksum or signature error for albert_4.38_i686-pc-linux-gnu
Mon 02 Jan 2006 01:45:21 AM CET|Einstein@Home|Unrecoverable error for result r1_0438.0__66_S4R2a_0 (app_version download error: couldn't get input files: albert_4.38_i686-pc-linux-gnu -120 signature verification failed)
I have been getting this error as well on 4 [this one, seti, rosetta and Climateprediction] ... but only on certain PC's, others work fine
I have also been getting this message lately
"03/01/2006 10:55:11 AM||Remote control not allowed; using loopback address"
I have 30+ boxes running boinc and it is a pain in the butt to come in to work and have to go and check each one to see if I have the checksum error or that remote control error.
The only way I have found to get BOINC back up and running is to uninstall, delete the boinc directory then reinstall ... anybody else have any ideas as to an easier way to correct this?
I have also been getting this message lately
"03/01/2006 10:55:11 AM||Remote control not allowed; using loopback address"
This is an information message. It tells you that you aren't using this computer for remote control. You can use one PC on the network to control the others, using the remoste_hosts.cfg file. Once you do that, the message will change to "Remote control allowed".
Now it's Boinc Manager telling you that it's only using the loopback address of localhost or 127.0.0.1, or the computer you are on. Not another computer out there.
Quote:
I have 30+ boxes running boinc and it is a pain in the butt to come in to work and have to go and check each one to see if I have the checksum error or that remote control error.
So instead of walking past all 30 computers, go sit down at your desk with your cup of coffee, after you set your computer with BOINC up to use Remote Control, using the Remote Hosts File.
You can then either use one Boinc Manager to check up on all the computers, or you can open 30 Boinc Managers all pointing to the others. ;)
I had (still have) the same Problem, it's the German Mirror Server for Mid-European Users screwing up badly.
Either suspend EAH (like I did) until they fix their Mirror or change the Timezone to get sorted into the UK area (the UK Mirror server reportedly works fine).
RE: Mon 02 Jan 2006
)
I have been getting this error as well on 4 [this one, seti, rosetta and Climateprediction] ... but only on certain PC's, others work fine
I have also been getting this message lately
"03/01/2006 10:55:11 AM||Remote control not allowed; using loopback address"
I have 30+ boxes running boinc and it is a pain in the butt to come in to work and have to go and check each one to see if I have the checksum error or that remote control error.
The only way I have found to get BOINC back up and running is to uninstall, delete the boinc directory then reinstall ... anybody else have any ideas as to an easier way to correct this?
Thanks
Darren
RE: I have also been
)
This is an information message. It tells you that you aren't using this computer for remote control. You can use one PC on the network to control the others, using the remoste_hosts.cfg file. Once you do that, the message will change to "Remote control allowed".
Now it's Boinc Manager telling you that it's only using the loopback address of localhost or 127.0.0.1, or the computer you are on. Not another computer out there.
So instead of walking past all 30 computers, go sit down at your desk with your cup of coffee, after you set your computer with BOINC up to use Remote Control, using the Remote Hosts File.
You can then either use one Boinc Manager to check up on all the computers, or you can open 30 Boinc Managers all pointing to the others. ;)
My client has also a problem
)
My client has also a problem with MD5 checksum here is the log.
I'm running on win XP.
[pre]04.01.2006 1:33:45|Einstein@Home|signature verification failed for albert_4.37_windows_intelx86.pdb
04.01.2006 1:33:45|Einstein@Home|Checksum or signature error for albert_4.37_windows_intelx86.pdb
04.01.2006 1:33:49|Einstein@Home|Finished download of skygrid_1210_r_T09.dat
04.01.2006 1:33:49|Einstein@Home|Throughput 109960 bytes/sec
04.01.2006 1:33:49|Einstein@Home|MD5 check failed for skygrid_1210_r_T09.dat
04.01.2006 1:33:49|Einstein@Home|expected 7052b1e7f2a139efb3403d49dbd3e6fb, got da1b92340e55e09551e4c16d5ffbd0d4
04.01.2006 1:33:49|Einstein@Home|Checksum or signature error for skygrid_1210_r_T09.dat
04.01.2006 1:34:09|Einstein@Home|Finished download of r1_1204.0
04.01.2006 1:34:09|Einstein@Home|Throughput 183356 bytes/sec
04.01.2006 1:34:09|Einstein@Home|MD5 check failed for r1_1204.0
04.01.2006 1:34:09|Einstein@Home|expected a49ed75181889ae68391f28907bc119e, got 9e486dd0a8d716f14e5e68e29d9dea55
04.01.2006 1:34:09|Einstein@Home|Checksum or signature error for r1_1204.0[/pre]
RE: My client has also a
)
You also appear to be in the timezone to be using the .de server?
I had (still have) the same
)
I had (still have) the same Problem, it's the German Mirror Server for Mid-European Users screwing up badly.
Either suspend EAH (like I did) until they fix their Mirror or change the Timezone to get sorted into the UK area (the UK Mirror server reportedly works fine).
I'm having the same problem,
)
I'm having the same problem, and the time zone thing I don't think will work, everyone's changing to Eastern, and I am in Eastern.
"Fiction reveals truth that reality obscures."
-Jessamyn West
Nevermind, I fixed it by
)
Nevermind, I fixed it by editing the client_state and scheduler_reply to temporarily remove the server that was failing for me...
"Fiction reveals truth that reality obscures."
-Jessamyn West
Seems someone fixed it, this
)
Seems someone fixed it, this evening I downloaded quite a number of WorkUnits with (so far) not a single one failing :)
RE: Seems someone fixed it,
)
And maybe not :( Please note, the download was suspended for CPU
benchmarks.
2006-01-07 17:16:52 [Einstein@Home] Started download of albert_4.40_i686-pc-linux-gnu
2006-01-07 17:17:21 [Einstein@Home] Finished upload of r1_1146.0__1417_S4R2a_1_0
2006-01-07 17:17:21 [Einstein@Home] Throughput 5531 bytes/sec
2006-01-07 17:17:21 [Einstein@Home] Started download of albert_4.40_i686-pc-linux-gnu.so
2006-01-07 17:22:24 [Einstein@Home] Finished download of albert_4.40_i686-pc-linux-gnu.so
2006-01-07 17:22:24 [Einstein@Home] Throughput 3088 bytes/sec
2006-01-07 17:22:44 [---] Suspending computation and network activity - running CPU benchmarks
2006-01-07 17:22:47 [---] Running CPU benchmarks
2006-01-07 17:23:46 [---] Benchmark results:
2006-01-07 17:23:46 [---] Number of CPUs: 1
2006-01-07 17:23:46 [---] 943 double precision MIPS (Whetstone) per CPU
2006-01-07 17:23:46 [---] 1562 integer MIPS (Dhrystone) per CPU
2006-01-07 17:23:46 [---] Finished CPU benchmarks
2006-01-07 17:23:47 [---] Resuming computation and network activity
2006-01-07 17:23:47 [---] request_reschedule_cpus: Resuming activities
2006-01-07 17:23:47 [Einstein@Home] Started download of albert_4.40_i686-pc-linux-gnu
2006-01-07 17:24:12 [Einstein@Home] Finished download of albert_4.40_i686-pc-linux-gnu
2006-01-07 17:24:12 [Einstein@Home] Throughput 4999 bytes/sec
2006-01-07 17:24:12 [Einstein@Home] signature verification failed for albert_4.40_i686-pc-linux-gnu
2006-01-07 17:24:12 [Einstein@Home] signature verification failed for albert_4.40_i686-pc-linux-gnu
2006-01-07 17:24:12 [Einstein@Home] Checksum or signature error for albert_4.40_i686-pc-linux-gnu
2006-01-07 17:24:12 [Einstein@Home] Checksum or signature error for albert_4.40_i686-pc-linux-gnu
Team Linux Users Everywhere
One of my team mates hat a
)
One of my team mates hat a problem with his DSL MTU size on the Berkeley server. Reducing it to 1300 in the registry fixed the problem for him.
Maybe some similar problem here