Message boards : Number crunching : jiiippeee the first WU from LHC!
Message board moderation

To post messages, you must log in.

AuthorMessage
ric

Send message
Joined: 17 Sep 04
Posts: 190
Credit: 649,637
RAC: 0
Message 5678 - Posted: 21 Feb 2005, 15:21:25 UTC

Thankyou LHC Dev!

21.02.2005 16:16:29|LHC@home|Requesting 43200.00 seconds of work
21.02.2005 16:16:29|LHC@home|Sending request to scheduler: http://lxfsrk4101.cern.ch/scheduler/cgi
21.02.2005 16:16:47|LHC@home|Scheduler RPC to http://lxfsrk4101.cern.ch/scheduler/cgi succeeded
21.02.2005 16:16:47|LHC@home|Message from server: You may have an outdated code verification key. This may prevent you from accepting new executables. If the problem persists, detach/attach the project.
21.02.2005 16:16:47|LHC@home|New host venue: school
21.02.2005 16:16:47|LHC@home|Host location: school
21.02.2005 16:16:47|LHC@home|Using separate project prefs for school
21.02.2005 16:16:48|LHC@home|Started download of sixtrack_4.63_windows_intelx86.exe
21.02.2005 16:16:48|LHC@home|Started download of v64boince6ib1-39s14_16615_1_sixvf_1666.zip
21.02.2005 16:17:03||May run out of work in 0.50 days; requesting more
21.02.2005 16:17:03|Einstein@Home|Requesting 4140.92 seconds of work
21.02.2005 16:17:03|Einstein@Home|Sending request to scheduler: http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
21.02.2005 16:17:06|Einstein@Home|Scheduler RPC to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
21.02.2005 16:17:07|LHC@home|Finished download of v64boince6ib1-39s14_16615_1_sixvf_1666.zip
21.02.2005 16:17:07|LHC@home|Throughput 20703 bytes/sec
21.02.2005 16:17:07|LHC@home|Started download of v64boince6ib1-39s14_16630_1_sixvf_1667.zip
21.02.2005 16:17:24|LHC@home|Finished download of sixtrack_4.63_windows_intelx86.exe
21.02.2005 16:17:24|LHC@home|Throughput 75538 bytes/sec
21.02.2005 16:17:24|LHC@home|Finished download of v64boince6ib1-39s14_16630_1_sixvf_1667.zip
21.02.2005 16:17:24|LHC@home|Throughput 23223 bytes/sec
21.02.2005 16:17:24|LHC@home|signature verification error for sixtrack_4.63_windows_intelx86.exe
21.02.2005 16:17:24|LHC@home|Checksum or signature error for sixtrack_4.63_windows_intelx86.exe
21.02.2005 16:17:24|LHC@home|Unrecoverable error for result v64boince6ib1-39s14_16615_1_sixvf_1666_1 (app_version download error: couldn't get input files: sixtrack_4.63_windows_intelx86.exe -120 signature verification error)
21.02.2005 16:17:24|LHC@home|Unrecoverable error for result v64boince6ib1-39s14_16630_1_sixvf_1667_0 (app_version download error: couldn't get input files: sixtrack_4.63_windows_intelx86.exe -120 signature verification error)
21.02.2005 16:17:25|LHC@home|Deferring communication with project for 59 seconds

OK there where DL error and probaly it's on initial delivering tests

Thats a good outlook!

keep on and good luck
ID: 5678 · Report as offensive     Reply Quote
Profile sysfried

Send message
Joined: 27 Sep 04
Posts: 282
Credit: 1,415,417
RAC: 0
Message 5679 - Posted: 21 Feb 2005, 15:40:30 UTC - in response to Message 5678.  

I got some errors too, but my client managed to fetch some work! :-)

> Thankyou LHC Dev!
>
> 21.02.2005 16:16:29|LHC@home|Requesti......
ID: 5679 · Report as offensive     Reply Quote
Profile Markku Degerholm

Send message
Joined: 3 Sep 04
Posts: 212
Credit: 4,545
RAC: 0
Message 5681 - Posted: 21 Feb 2005, 17:39:55 UTC - in response to Message 5678.  

> 21.02.2005 16:16:47|LHC@home|Message from server: You may have an outdated
> code verification key. This may prevent you from accepting new executables.
> If the problem persists, detach/attach the project.
...
> 21.02.2005 16:17:24|LHC@home|Checksum or signature error for
> sixtrack_4.63_windows_intelx86.exe

This is because we are using new server-side sign keys. But there should be a mechanism in BOINC which allows updating the keys by signing of the new public code sign key using the old private code sign key. But apparently there is something wrong in the setup. Must look upon the matter.


Markku Degerholm
LHC@home admin
ID: 5681 · Report as offensive     Reply Quote
Profile Markku Degerholm

Send message
Joined: 3 Sep 04
Posts: 212
Credit: 4,545
RAC: 0
Message 5683 - Posted: 21 Feb 2005, 18:00:45 UTC

I think I fixed that now. However, I'm unable to test it. Please inform if any of you still gets "You may have an outdated code verification key." message.

Generally speaking, it's not a good idea to accept a badly-signed executable (by resetting the project)... If somebody is able to hack into our server, the hacker is able to send the users any code he wants to be executed (like password sniffer, smap server, etc).

Markku Degerholm
LHC@home admin
ID: 5683 · Report as offensive     Reply Quote
Profile [SETI.USA]Tank_Master
Avatar

Send message
Joined: 17 Sep 04
Posts: 22
Credit: 983,416
RAC: 0
Message 5691 - Posted: 21 Feb 2005, 18:38:03 UTC

I am running a P4 3.2 on boinc 4.66 and server 2003 (w/ SP1)

I have gotten the following messages 3 times, all for the same file (sixtrack_4.63_windows_intelx86.exe). Times are in Pacific Time:

2/21/2005 10:25:39 AM|LHC@home|Finished download of sixtrack_4.63_windows_intelx86.exe
2/21/2005 10:25:39 AM|LHC@home|Throughput 54142 bytes/sec
2/21/2005 10:25:39 AM|LHC@home|signature verification error for sixtrack_4.63_windows_intelx86.exe
2/21/2005 10:25:39 AM|LHC@home|Checksum or signature error for sixtrack_4.63_windows_intelx86.exe
2/21/2005 10:25:39 AM|LHC@home|Unrecoverable error for result v64boince6ib1-15s18_20660_1_sixvf_719_9 (app_version download error: couldn't get input files: sixtrack_4.63_windows_intelx86.exe -120 signature verification error)
2/21/2005 10:25:39 AM|LHC@home|Unrecoverable error for result v64boince6ib1-21s10_12660_1_sixvf_939_8 (app_version download error: couldn't get input files: sixtrack_4.63_windows_intelx86.exe -120 signature verification error)
2/21/2005 10:25:40 AM|LHC@home|Deferring communication with project for 59 seconds


In between each one, I got the error "project is down" (most likely do to the database overload)


After the third fail of the "checksum error" I got for 2 times in a row (I forced an update about 5 min after this failed attempt and got the same message):

2/21/2005 10:30:07 AM|LHC@home|Message from server: You may have an outdated code verification key. This may prevent you from accepting new executables. If the problem persists, detach/attach the project.
2/21/2005 10:30:07 AM|LHC@home|No work from project
2/21/2005 10:30:07 AM|LHC@home|Deferring communication with project for 1 hours, 0 minutes, and 0 seconds

~Keith
ID: 5691 · Report as offensive     Reply Quote
Profile [SETI.USA]Tank_Master
Avatar

Send message
Joined: 17 Sep 04
Posts: 22
Credit: 983,416
RAC: 0
Message 5692 - Posted: 21 Feb 2005, 18:48:14 UTC

I detached and reattached the project like the last error message said to do, after 3 attempts to reattach, it finally did, and the checksum error did NOT reappear. All files downloaded ok. Both work units are now in "ready to run" status. Its computing for other projects at the moment.

~Keith
ID: 5692 · Report as offensive     Reply Quote
Profile Thierry Van Driessche
Avatar

Send message
Joined: 1 Sep 04
Posts: 157
Credit: 82,604
RAC: 0
Message 5693 - Posted: 21 Feb 2005, 18:49:23 UTC - in response to Message 5683.  
Last modified: 21 Feb 2005, 18:50:35 UTC

> I think I fixed that now. However, I'm unable to test it. Please inform if any
> of you still gets "You may have an outdated code verification key." message.
>
> Generally speaking, it's not a good idea to accept a badly-signed executable
> (by resetting the project)... If somebody is able to hack into our server, the
> hacker is able to send the users any code he wants to be executed (like
> password sniffer, smap server, etc).

Nice to see you back Markku.

LHC@home - 2005-02-21 19:30:06 - Message from server: You may have an outdated code verification key. This may prevent you from accepting new executables. If the problem persists, detach/attach the project.
LHC@home - 2005-02-21 19:30:35 - Message from server: You may have an outdated code verification key. This may prevent you from accepting new executables. If the problem persists, detach/attach the project.

Time is UTC +1h.

I detached and attached again. By doing so, it went fine. Only had to merge PC as an identical one was creating by detach/attach. All files were downloaded without any problem.
Ready to crunch.

Best greetings from Belgium
Thierry
ID: 5693 · Report as offensive     Reply Quote
Astro

Send message
Joined: 17 Sep 04
Posts: 69
Credit: 26,714
RAC: 0
Message 5696 - Posted: 21 Feb 2005, 18:52:56 UTC

I'm right there with you. I'm downloading 6 WU as we speak.

Hi all

tony
Formerly
mmciastro. Name and avatar changed for a change

The New Online Helpsytem help is just a call away.
ID: 5696 · Report as offensive     Reply Quote
Professor Desty Nova
Avatar

Send message
Joined: 27 Sep 04
Posts: 34
Credit: 198,110
RAC: 10
Message 5698 - Posted: 21 Feb 2005, 18:55:56 UTC

After noticing those errors with the signing key, and detaching/ trying to reatach several times, I finally got several WU :-))))


Professor Desty Nova
Researching Karma the Hard Way
ID: 5698 · Report as offensive     Reply Quote

Message boards : Number crunching : jiiippeee the first WU from LHC!


©2022 CERN