Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 15
Posts: 15   Pages: 2   [ Previous Page | 1 2 ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 3953 times and has 14 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Why are these considered errors?

Well, I do have the problems on Linux (Debian), Windows 2008 server and Vista as well, I haven't seen the problem on the Mac yet...
[Jan 23, 2009 4:11:29 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Why are these considered errors?

Hi Harreld,
You might have run into a problem when the URL to the server changed. Were you successfully connecting to the server after it moved from Boulder, Colorado, United States to Toronto, Ontario, Canada? Some people had the old URL cached on their system and needed to reboot.

Lawrence
[Jan 23, 2009 5:16:28 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Why are these considered errors?

Hi Lawrence,

It became a long story... wink

I've digged a bit more in the errors and I think I can split it into 2 categories:

1: Errors due to the WCG platform move
2: Errors due to calculation errors.

1:
These errors seem to be due to the fact that they were returned too late, because nothing unusual can be seen in the results and copies have been sent out. All these WU have been sent out on the 7th, 8th and 9th of january.
Question here is: Why aren't these being marked as "Too late"?
Here is a result from HPF2 and one from FA@H:

HPF2:
<core_client_version>5.4.11</core_client_version>
<stderr_txt>
called boinc_finish

</stderr_txt>

FA@H:
<core_client_version>5.4.11</core_client_version>
<stderr_txt>
INFO:[04:18:26] Start AutoGrid...

autogrid: autogrid4: Successful Completion.
INFO:[04:18:51] End AutoGrid...
Beginning AutoDock...

autodock4: *** WARNING! Non-integral total charge (-0.07 e) on ligand! ***

INFO: Setting num_generations: 10000
About to enter main loop...(dockings already completed: 0)
_maxGenSeenSoFar changed: 2500
_maxGenSeenSoFar changed: 2626
_maxGenSeenSoFar changed: 2758
_maxGenSeenSoFar changed: 2896
_maxGenSeenSoFar changed: 3041
_maxGenSeenSoFar changed: 3194
_maxGenSeenSoFar changed: 3354
_maxGenSeenSoFar changed: 3522
_maxGenSeenSoFar changed: 3699
_maxGenSeenSoFar changed: 3885
_maxGenSeenSoFar changed: 4080
_maxGenSeenSoFar changed: 4285
_maxGenSeenSoFar changed: 4500
_maxGenSeenSoFar changed: 4726
_maxGenSeenSoFar changed: 4963
_maxGenSeenSoFar changed: 5212
_maxGenSeenSoFar changed: 5473
_maxGenSeenSoFar changed: 5747
_maxGenSeenSoFar changed: 6035
_maxGenSeenSoFar changed: 6337
_maxGenSeenSoFar changed: 6654
_maxGenSeenSoFar changed: 6987
_maxGenSeenSoFar changed: 7337
_maxGenSeenSoFar changed: 7704
_maxGenSeenSoFar changed: 8090
_maxGenSeenSoFar changed: 8495
_maxGenSeenSoFar changed: 8920
_maxGenSeenSoFar changed: 9367
_maxGenSeenSoFar changed: 9836
_maxGenSeenSoFar changed: 10328
Updating Best Energy for WU: 0.00
Finished Docking number 0
Updating Best Energy for WU: -8.96
Finished Docking number 1
Finished Docking number 2
Finished Docking number 3
Finished Docking number 4
Finished Docking number 5
Finished Docking number 6
Finished Docking number 7
Finished Docking number 8
Finished Docking number 9
Finished Docking number 10
Finished Docking number 11
Finished Docking number 12
Finished Docking number 13
Finished Docking number 14
Updating Best Energy for WU: -10.05
Finished Docking number 15
Finished Docking number 16
Finished Docking number 17
Finished Docking number 18
Finished Docking number 19
Finished Docking number 20
Finished Docking number 21
Finished Docking number 22
Finished Docking number 23
Finished Docking number 24
Finished Docking number 25
Finished Docking number 26
Finished Docking number 27
Finished Docking number 28
Finished Docking number 29
Finished Docking number 30
Finished Docking number 31
Finished Docking number 32
Finished Docking number 33
Finished Docking number 34
Finished Docking number 35
Finished Docking number 36
Finished Docking number 37
Finished Docking number 38
Finished Docking number 39
Finished Docking number 40
Finished Docking number 41
Finished Docking number 42
Finished Docking number 43
Finished Docking number 44
Finished Docking number 45
Finished Docking number 46
Finished Docking number 47
Finished Docking number 48
Finished Docking number 49
Finished Docking number 50

________________________________________________________________________________

autodock4: Successful Completion on "World Community Grid device"

________________________________________________________________________________

INFO:[11:19:03] Start AutoGrid...

autogrid: autogrid4: Successful Completion.
INFO:[11:19:28] End AutoGrid...
Beginning AutoDock...
INFO: Setting num_generations: 27000
About to enter main loop...(dockings already completed: 51)
Finished Docking number 0

________________________________________________________________________________

autodock4: Successful Completion on "World Community Grid device"

________________________________________________________________________________

called boinc_finish

</stderr_txt>


2:
Since the 14th of January I sometimes get Errors on Windows machines only, mainly for the project HPF2 with the following error:

<core_client_version>6.2.18</core_client_version>
<![CDATA[
<message>
Onjuiste functie. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
ERROR:: Exit at: .\dock_structure.cc line:401

</stderr_txt>
]]>

On the DDDT project I've had one error due to an file unlock error:
<<<snippet from DDDT log>>>
Finished Docking number 20
Finished Docking number 21
Finished Docking number 22
Finished Docking number 23
Can't acquire lockfile - exiting
FILE_LOCK::unlock(): close failed.: No error
Can't acquire lockfile - exiting
FILE_LOCK::unlock(): close failed.: No error
Can't acquire lockfile - exiting
FILE_LOCK::unlock(): close failed.: No error
Can't acquire lockfile - exiting
FILE_LOCK::unlock(): close failed.: No error
<<<end snippet>>>

Before this I can't remember that I had errors except for some Beta's on Linux :-)
A second question here that maybe shouldn't be asked here is:
Does this huge amount of error affect the reliability state of my machines for Beta-testing? If so, can the errors occured due to the move of WCG being discarded?
Just a thougt...

Harreld.
[Jan 23, 2009 7:35:34 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Why are these considered errors?

Hello Harreld,
Yes, there have been some HPF2 errors recently that looked like yours. You can reed about them on the HPF2 Forum.

As for Beta testing, once your machine has returned 15 validated results in a row, you are eligible if the turn-around time is short. CEP is giving us a lot of Beta work these days.

Lawrence
[Jan 23, 2009 8:52:12 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Why are these considered errors?

Sorry about those errors, saw the other posts too late.

And 15 in a row???
Hmmm... with dual-quadcores is that done in less than a day... biggrin

/Harreld.
----------------------------------------
[Edit 1 times, last edit by Former Member at Jan 23, 2009 8:56:56 PM]
[Jan 23, 2009 8:56:05 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 15   Pages: 2   [ Previous Page | 1 2 ]
[ Jump to Last Post ]
Post new Thread