Posts by Saenger

1) Message boards : Number crunching : UP, DOWN, CPU WU ERRORS (Message 2416)
Posted 16 Apr 2010 by Profile Saenger
Post:
There is no way of monitoring my success or failure, as the project folks decided to delete any information as fast as possible from our view. I can't say whether they can see something for themselves as admins, but as WUs get completely deleted from the database asap, there cannot be any reasonable feedback from us crunchers, i.e. they obviously regard us and our experience as something utterly superfluous.

It has been mentioned before, there is no valid reason not to keep valid results in the database for at least 48h after validation or invalidation, so that we participants have a chance to see anything.

I regard this behaviour as very unfriendly, and as you know about this since quie some time, it's deliberate unfriendliness.
2) Message boards : Number crunching : cannot see valid credits (Message 2415)
Posted 16 Apr 2010 by Profile Saenger
Post:
I have asked that before, it had been corrected, but only for a few days obviously.

The projects doesn't seem to want feedback from it's participants, we should stfu and crunch. Not nice.
3) Message boards : Number crunching : Validated WUs disappear asap, why? (Message 2414)
Posted 16 Apr 2010 by Profile Saenger
Post:
I take my thanks back, as you did the wrong thing again, it seemed to have lasted only a few days.

Why do you do such unfriendly things?
How is anyone supposed to see anything about his/her WUs?

I just happened to report one WU and went here asap, and that was very necessary, as you decided to grant no credits for a valid (probably) WU as it had "Too many total results" It was this WU: 563398, but it's vanished now as well.

I haven't done a screenshot, will do so in the furure if I happen to see such behaviour again, only it will be quite futile with this inexapable behaviour of deletion asap.

It had 2 probably valid results, one aborted, one calculation error and 4 non-sends. Max of totals is 8, so this was just reached but not surpassed. Why did you create 8 WUS if you don't want them?
4) Message boards : Number crunching : UP, DOWN, CPU WU ERRORS (Message 2388)
Posted 28 Mar 2010 by Profile Saenger
Post:
All my last ones crash after considerably crunching time, see this thread
5) Message boards : Number crunching : Error in Ubuntu 9.04 X86_64 (Message 2387)
Posted 28 Mar 2010 by Profile Saenger
Post:
Same here with karmic64 (Ubuntu 9.10 X86_64):

<core_client_version>6.10.17</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)
</message>
<stderr_txt>
wrapper: starting
10:20:03 (22210): wrapper: running unzip.exe (-qq -o "./*.zip" -d ".")

2 archives were successfully processed.
10:20:06 (22210): wrapper: running ./Python25/python.exe (make_sitecustomize.py ".")
10:20:06 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/Support/sitecustomize.py")
10:20:06 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_ligand4.py" -l ligand.mol2 -o ligand.pdbqt)
10:20:07 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_gpf4.py" -l ligand.pdbqt -r receptor_1.pdbqt -p custom_parameter_file=1 -p parameter_file=AD4_parameters.dat)
10:20:08 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_dpf4.py" -l ligand.pdbqt -r receptor_1.pdbqt -p compute_unbound_extended_flag=0 -p ga_run=10 -p ga_num_evals=1000000 -p seed=309246)
10:20:09 (22210): wrapper: running ../../projects/boinc.drugdiscoveryathome.com/autogrid_1.401_x86_64-pc-linux-gnu (-p receptor_1.gpf -l out.glg)
10:20:18 (22210): wrapper: running ../../projects/boinc.drugdiscoveryathome.com/autodock_1.410_x86_64-pc-linux-gnu (-p ligand_receptor_1.dpf -l out_1.dlg)
10:23:53 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/summarize_docking.py" -l out_1.dlg -r receptor_1.pdbqt -o summary_1.txt)
10:23:55 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_gpf4.py" -l ligand.pdbqt -r receptor_2.pdbqt -p custom_parameter_file=1 -p parameter_file=AD4_parameters.dat)
10:23:57 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_dpf4.py" -l ligand.pdbqt -r receptor_2.pdbqt -p compute_unbound_extended_flag=0 -p ga_run=10 -p ga_num_evals=1000000 -p seed=371485)
10:23:58 (22210): wrapper: running ../../projects/boinc.drugdiscoveryathome.com/autogrid_1.401_x86_64-pc-linux-gnu (-p receptor_2.gpf -l out.glg)
10:24:07 (22210): wrapper: running ../../projects/boinc.drugdiscoveryathome.com/autodock_1.410_x86_64-pc-linux-gnu (-p ligand_receptor_2.dpf -l out_2.dlg)
10:27:48 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/summarize_docking.py" -l out_2.dlg -r receptor_2.pdbqt -o summary_2.txt)
10:27:50 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_gpf4.py" -l ligand.pdbqt -r receptor_3.pdbqt -p custom_parameter_file=1 -p parameter_file=AD4_parameters.dat)
10:27:52 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_dpf4.py" -l ligand.pdbqt -r receptor_3.pdbqt -p compute_unbound_extended_flag=0 -p ga_run=10 -p ga_num_evals=1000000 -p seed=122029)
10:27:53 (22210): wrapper: running ../../projects/boinc.drugdiscoveryathome.com/autogrid_1.401_x86_64-pc-linux-gnu (-p receptor_3.gpf -l out.glg)
10:28:06 (22210): wrapper: running ../../projects/boinc.drugdiscoveryathome.com/autodock_1.410_x86_64-pc-linux-gnu (-p ligand_receptor_3.dpf -l out_3.dlg)
10:31:52 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/summarize_docking.py" -l out_3.dlg -r receptor_3.pdbqt -o summary_3.txt)
10:31:54 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_gpf4.py" -l ligand.pdbqt -r receptor_4.pdbqt -p custom_parameter_file=1 -p parameter_file=AD4_parameters.dat)
10:31:56 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_dpf4.py" -l ligand.pdbqt -r receptor_4.pdbqt -p compute_unbound_extended_flag=0 -p ga_run=10 -p ga_num_evals=1000000 -p seed=540877)
10:31:57 (22210): wrapper: running ../../projects/boinc.drugdiscoveryathome.com/autogrid_1.401_x86_64-pc-linux-gnu (-p receptor_4.gpf -l out_4.glg)
10:32:09 (22210): wrapper: running ../../projects/boinc.drugdiscoveryathome.com/autodock_1.410_x86_64-pc-linux-gnu (-p ligand_receptor_4.dpf -l out_4.dlg)
10:35:46 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/summarize_docking.py" -l out_4.dlg -r receptor_4.pdbqt -o summary_4.txt)
10:35:48 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_gpf4.py" -l ligand.pdbqt -r receptor_5.pdbqt -p custom_parameter_file=1 -p parameter_file=AD4_parameters.dat)
10:35:50 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_dpf4.py" -l ligand.pdbqt -r receptor_5.pdbqt -p compute_unbound_extended_flag=0 -p ga_run=10 -p ga_num_evals=1000000 -p seed=965231)
10:35:51 (22210): wrapper: running ../../projects/boinc.drugdiscoveryathome.com/autogrid_1.401_x86_64-pc-linux-gnu (-p receptor_5.gpf -l out.glg)
10:36:03 (22210): wrapper: running ../../projects/boinc.drugdiscoveryathome.com/autodock_1.410_x86_64-pc-linux-gnu (-p ligand_receptor_5.dpf -l out_5.dlg)
10:39:26 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/summarize_docking.py" -l out_5.dlg -r receptor_5.pdbqt -o summary_5.txt)
10:39:28 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_gpf4.py" -l ligand.pdbqt -r receptor_6.pdbqt -p custom_parameter_file=1 -p parameter_file=AD4_parameters.dat)
10:39:29 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_dpf4.py" -l ligand.pdbqt -r receptor_6.pdbqt -p compute_unbound_extended_flag=0 -p ga_run=10 -p ga_num_evals=1000000 -p seed=589685)
10:39:30 (22210): wrapper: running ../../projects/boinc.drugdiscoveryathome.com/autogrid_1.401_x86_64-pc-linux-gnu (-p receptor_6.gpf -l out.glg)
10:39:41 (22210): wrapper: running ../../projects/boinc.drugdiscoveryathome.com/autodock_1.410_x86_64-pc-linux-gnu (-p ligand_receptor_6.dpf -l out_6.dlg)
10:42:57 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/summarize_docking.py" -l out_6.dlg -r receptor_6.pdbqt -o summary_6.txt)
10:42:58 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_gpf4.py" -l ligand.pdbqt -r receptor_7.pdbqt -p custom_parameter_file=1 -p parameter_file=AD4_parameters.dat)
10:43:00 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_dpf4.py" -l ligand.pdbqt -r receptor_7.pdbqt -p compute_unbound_extended_flag=0 -p ga_run=10 -p ga_num_evals=1000000 -p seed=371634)
10:43:01 (22210): wrapper: running ../../projects/boinc.drugdiscoveryathome.com/autogrid_1.401_x86_64-pc-linux-gnu (-p receptor_7.gpf -l out.glg)
10:43:11 (22210): wrapper: running ../../projects/boinc.drugdiscoveryathome.com/autodock_1.410_x86_64-pc-linux-gnu (-p ligand_receptor_7.dpf -l out_7.dlg)
10:46:45 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/summarize_docking.py" -l out_7.dlg -r receptor_7.pdbqt -o summary_7.txt)
10:46:47 (22210): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_gpf4.py" -l ligand.pdbqt -r receptor_8.pdbqt -p custom_parameter_file=1 -p parameter_file=AD4_parameters.dat)
app exit status: 0x100
10:46:48 (22210): called boinc_finish

</stderr_txt>
]]>



If it would happen immediately, it would be finer, but it takes between 20 and 40 minutes to crash, and there aren't even any error messages in the messages tab:
So 28 Mär 2010 15:54:10 CEST	DrugDiscovery	Sending scheduler request: To fetch work.
So 28 Mär 2010 15:54:10 CEST	DrugDiscovery	Reporting 1 completed tasks, requesting new tasks for CPU
So 28 Mär 2010 15:54:15 CEST	DrugDiscovery	Scheduler request completed: got 1 new tasks
So 28 Mär 2010 15:54:17 CEST	DrugDiscovery	Started download of 31773_ChemDiv_5400-0816_1269717080909630000.txt
So 28 Mär 2010 15:54:17 CEST	DrugDiscovery	Started download of PMC1IJY.zip_1269735510575743000.zip
So 28 Mär 2010 15:54:20 CEST	DrugDiscovery	Finished download of 31773_ChemDiv_5400-0816_1269717080909630000.txt
So 28 Mär 2010 15:54:20 CEST	DrugDiscovery	Started download of job_10_1269735510575743000.txt
So 28 Mär 2010 15:54:23 CEST	DrugDiscovery	Finished download of job_10_1269735510575743000.txt
So 28 Mär 2010 15:54:23 CEST	DrugDiscovery	Started download of top_summary_1269735510575743000.txt
So 28 Mär 2010 15:54:25 CEST	DrugDiscovery	Finished download of top_summary_1269735510575743000.txt
So 28 Mär 2010 15:54:27 CEST	DrugDiscovery	Finished download of PMC1IJY.zip_1269735510575743000.zip
So 28 Mär 2010 16:11:57 CEST	DrugDiscovery	Starting rcs_ga_run_10_bt_PMC1IJY.zip_lig_31773_ChemDiv_5400-0816_ts_1269717080909630000_0
So 28 Mär 2010 16:11:58 CEST	DrugDiscovery	Starting task rcs_ga_run_10_bt_PMC1IJY.zip_lig_31773_ChemDiv_5400-0816_ts_1269717080909630000_0 using autodock_mgl version 517
So 28 Mär 2010 16:31:19 CEST	DrugDiscovery	Computation for task rcs_ga_run_10_bt_PMC1IJY.zip_lig_31773_ChemDiv_5400-0816_ts_1269717080909630000_0 finished
6) Message boards : Number crunching : Validated WUs disappear asap, why? (Message 2313)
Posted 5 Mar 2010 by Profile Saenger
Post:
Thanks for fixing this bug!
Now I can as well see those WUs that went through fine and validated properly, as expected :)
7) Message boards : Number crunching : Unable to join a team... (Message 2290)
Posted 28 Feb 2010 by Profile Saenger
Post:
Okay, I tried that URL and the respond is 'Unable to handle". Might be best for me to wait a couple of days, get some credits and it may work.


OK, I tried this with some other teams as well, and as the long link ist this:
http://boinc.drugdiscoveryathome.com/team_join.php?&tnow=1267347880&ttok=87368e6e458feecab443c52eeb6d8b8c&teamid=16
it probably includes some timestamp and session-ID. Often such URLs work without the session-ID, this one obviously not.
I don't know whether they will be valid for longer, but you can try the long version and say what happened.
8) Message boards : Number crunching : Unable to join a team... (Message 2287)
Posted 28 Feb 2010 by Profile Saenger
Post:
If you know the team number, you can always create your "join team" link in the URL direct:

http://boinc.drugdiscoveryathome.com/team_join.php?&teamid=16

It's in general always the same with all projects (except WCG):
Project.url/team_join.php?&teamid=123
9) Message boards : Number crunching : UP, DOWN, CPU WU ERRORS (Message 2279)
Posted 25 Feb 2010 by Profile Saenger
Post:
Update in the morning:
Some more autodock_ga... have been unable to reach my machine because of a download error.
Some of the rcs_ga... have been unsuccessful to finish, they got "Error while computing". They erred after 120 to 210 seconds. The have this stderr (example is #2101137:

<core_client_version>6.10.17</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)
</message>
<stderr_txt>
wrapper: starting
22:02:54 (932): wrapper: running unzip.exe (-qq -o "./*.zip" -d ".")

2 archives were successfully processed.
22:02:56 (932): wrapper: running ./Python25/python.exe (make_sitecustomize.py ".")
22:02:56 (932): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/Support/sitecustomize.py")
22:02:57 (932): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_ligand4.py" -l ligand.mol2 -o ligand.pdbqt)
22:02:58 (932): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_gpf4.py" -l ligand.pdbqt -r receptor_1.pdbqt -p custom_parameter_file=1 -p parameter_file=AD4_parameters.dat)
22:02:59 (932): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/prepare_dpf4.py" -l ligand.pdbqt -r receptor_1.pdbqt -p compute_unbound_extended_flag=0 -p ga_run=10 -p ga_num_evals=1000000 -p seed=498826)
22:03:00 (932): wrapper: running ../../projects/boinc.drugdiscoveryathome.com/autogrid_1.401_x86_64-pc-linux-gnu (-p receptor_1.gpf -l out.glg)
22:03:06 (932): wrapper: running ../../projects/boinc.drugdiscoveryathome.com/autodock_1.410_x86_64-pc-linux-gnu (-p ligand_receptor_1.dpf -l out_1.dlg)
22:05:11 (932): wrapper: running ./Python25/python.exe ("./MGLToolsPckgs/AutoDockTools/Utilities24/summarize_docking.py" -l out_1.dlg -r receptor_1.pdbqt -o summary_1.txt)
app exit status: 0x200
22:05:11 (932): called boinc_finish

</stderr_txt>
]]>


But not all of them erred, and one nsteps from mdrun is waiting for validation as well.
And I don't have any idea whether there were as well some successful validated WUs during the night, as you mindless delete those asap.
10) Message boards : Number crunching : UP, DOWN, CPU WU ERRORS (Message 2277)
Posted 24 Feb 2010 by Profile Saenger
Post:
Got a bunch of download errors just yet:
stderr:
<core_client_version>6.10.17</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
  <file_name>job_10_1266800102540857000.txt</file_name>
  <error_code>-119</error_code>
  <error_message>MD5 check failed</error_message>
</file_xfer_error>

</message>
]]>

messages tab:
Mi 24 Feb 2010 19:25:49 CET	DrugDiscovery	Finished download of Fzd2.zip_1266987074168186000.zip
Mi 24 Feb 2010 19:25:49 CET	DrugDiscovery	Finished download of top_summary_1266987074168186000.txt
Mi 24 Feb 2010 19:25:49 CET	DrugDiscovery	Started download of 32144_ChemDiv_5928-0_1266800102540857000.txt
Mi 24 Feb 2010 19:25:49 CET	DrugDiscovery	Started download of receptor.pdb_1266800102540857000.txt
Mi 24 Feb 2010 19:25:50 CET	DrugDiscovery	Finished download of 32144_ChemDiv_5928-0_1266800102540857000.txt
Mi 24 Feb 2010 19:25:50 CET	DrugDiscovery	Started download of job_10_1266800102540857000.txt
Mi 24 Feb 2010 19:25:52 CET	DrugDiscovery	Finished download of receptor.pdb_1266800102540857000.txt
Mi 24 Feb 2010 19:25:52 CET	DrugDiscovery	Finished download of job_10_1266800102540857000.txt
Mi 24 Feb 2010 19:25:52 CET	DrugDiscovery	Started download of receptor.psf_1266800102540857000.txt
Mi 24 Feb 2010 19:25:52 CET	DrugDiscovery	Started download of ligand.psf_1266800102540857000.txt
Mi 24 Feb 2010 19:25:52 CET	DrugDiscovery	[error] MD5 check failed for job_10_1266800102540857000.txt
Mi 24 Feb 2010 19:25:52 CET	DrugDiscovery	[error] expected 8ec85ec43b3f2d4a872deeb82f09b814, got 3b9cc3ba5f257e3c792d517bbcddbd97
Mi 24 Feb 2010 19:25:52 CET	DrugDiscovery	[error] Checksum or signature error for job_10_1266800102540857000.txt
Mi 24 Feb 2010 19:25:53 CET	DrugDiscovery	Finished download of receptor.psf_1266800102540857000.txt
Mi 24 Feb 2010 19:25:53 CET	DrugDiscovery	Finished download of ligand.psf_1266800102540857000.txt
Mi 24 Feb 2010 19:25:53 CET	DrugDiscovery	Started download of ligand.pdb_1266800102540857000.txt
Mi 24 Feb 2010 19:25:53 CET	DrugDiscovery	Started download of 31976_ChemDiv_6574-0_1266800102540857000.txt
Mi 24 Feb 2010 19:25:54 CET	DrugDiscovery	Incomplete read of 2607.000000 < 5KB for ligand.pdb_1266800102540857000.txt - truncating
Mi 24 Feb 2010 19:25:54 CET	DrugDiscovery	Finished download of ligand.pdb_1266800102540857000.txt
Mi 24 Feb 2010 19:25:54 CET	DrugDiscovery	Finished download of 31976_ChemDiv_6574-0_1266800102540857000.txt
Mi 24 Feb 2010 19:25:54 CET	DrugDiscovery	Started download of 40412_ChemDiv_K906-3620_1266948975059381000.txt
Mi 24 Feb 2010 19:25:54 CET	DrugDiscovery	Started download of PMC1IJY.zip_1266993012338214000.zip
Mi 24 Feb 2010 19:25:54 CET	DrugDiscovery	[error] File ligand.pdb_1266800102540857000.txt has wrong size: expected 2405, got 0
Mi 24 Feb 2010 19:25:54 CET	DrugDiscovery	[error] Checksum or signature error for ligand.pdb_1266800102540857000.txt


They are autodoc_ga... as well.
I still have a bunch of rcs_ga on my machine, none already running, but at least downloaded properly.
11) Message boards : Number crunching : Validated WUs disappear asap, why? (Message 2276)
Posted 24 Feb 2010 by Profile Saenger
Post:
how many wu's is your computer doing per day?

Probably one or two dozens. Not much, but I crunch in several dozen projects on a single computer, and this behaviour doesn't make your project more trustworthy.
I can't tell exactly how much, as only those "Waiting for validation" (or recently a lot of "Error while downloading") are shown, and I don't sit at my computer all the time and watch for DD-WUs.
12) Message boards : Number crunching : Validated WUs disappear asap, why? (Message 2269)
Posted 24 Feb 2010 by Profile Saenger
Post:
I still can't tell whether my WUs were successful or not, as they disappear before I have a chance to look at them after the validator gets to them. I only see those WUs, that I only claim to be right, and I see my credits climbing from time to time, but that's worth nothing.

Why don't you want our help in this regard? There is absolutely no need to delete every validated WU, you can have them in your other database without deleting them here and giving your "testers" nothing to validate their testing.
13) Message boards : Number crunching : Validated WUs disappear asap, why? (Message 2246)
Posted 14 Feb 2010 by Profile Saenger
Post:
it's done this way so that jack can see the results as they come out. and we are heading in the right direction. i'm going to post the weekly stats on all apps. here is a bit after the nascar race goes off.

No problem with a fast processing, you can validate, assimilate and transition them as fast as you want to, as long as you keep the file-deleter a bit more on slow motion.
14) Message boards : Number crunching : Validated WUs disappear asap, why? (Message 2243)
Posted 14 Feb 2010 by Profile Saenger
Post:
I've crunched several WUs lately, not much, but there are not so many ;)
I can see them in my tasks list as long as they are either still in work or not validated. As soo as the validator gets to them they disappear from the list.
How can anyone say anything useful about ones work if there is nothing to be seen?
Why can't they stay in the list for 1 or 2 days, as every other project does, even non-beta ones?
What's the use of crunching here some beta WUs if you can't say anything about their performance?
15) Message boards : Number crunching : UP, DOWN, CPU WU ERRORS (Message 2123)
Posted 14 Jan 2010 by Profile Saenger
Post:
Do 14 Jan 2010 19:20:21 CET	DrugDiscovery	Sending scheduler request: Requested by user.
Do 14 Jan 2010 19:20:21 CET	DrugDiscovery	Reporting 11 completed tasks, not requesting new tasks
Do 14 Jan 2010 19:20:26 CET	DrugDiscovery	Scheduler request completed
Do 14 Jan 2010 19:20:26 CET	DrugDiscovery	Message from server: Project is temporarily shut down for maintenance

And a wee peek at the server_status shows this:
data-driven web pages	vps	Running
upload/download server	vps	Running
scheduler	vps	Not Running
feeder	vps	Not Running
transitioner	vps	Not Running
file_deleter	vps	Not Running


What's wrong? Not that any deadline is looming, but...
16) Message boards : Number crunching : UP, DOWN, CPU WU ERRORS (Message 1536)
Posted 14 Oct 2009 by Profile Saenger
Post:
Only DL-errors at last (example 936568):
<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
  <file_name>27303_ChemDiv_1725-0046_1255421347278762264.7z</file_name>
  <error_code>-224</error_code>
  <error_message>file not found</error_message>
</file_xfer_error>
<file_xfer_error>
  <file_name>fzd8min_renum_SS.pdb1255421347278762264</file_name>
  <error_code>-224</error_code>
  <error_message>file not found</error_message>
</file_xfer_error>

</message>
]]>
17) Message boards : Number crunching : Status at 108.181% (Message 1514)
Posted 12 Oct 2009 by Profile Saenger
Post:
I open a new thread just to report a bug with the progress bar. Feel free to merge/move it to a more appropriate thread if you feel like it.

In my Ubuntu 64bit machine, autodock_*** workunits achieve a staggering 108.181% in the progress bar. The WUs crunch and validate well, so no problem on the crunching side; it's just the display on the progress bar that goes a bit beyond what it should before finishing at 100%. Obviously, this also has an effect on the 'Time to completion' tab of the WUs.
Version of autodock executable is 1.410.


that version is outdated, and the linux(64) version is at 5.10.(oct 6). do you have an id of the wu that ran on your systems.?

I've just got the same here, Version is 5.10 (in BOINC, the process is called autodock_1.410_x86_64-pc-linux-gnu). After it finished it went back to 100%. It's this one here: 898867
18) Message boards : Number crunching : UP, DOWN, CPU WU ERRORS (Message 1484)
Posted 9 Oct 2009 by Profile Saenger
Post:
Can you please activate homogeneous redundancy for autodock with mgltools scripts v5.10?
It seems, that they run only on Penguins, not in Redmond. I lost one probably valid WU (263380) because all other puters were Redmond-infested ;)

I've got some errors on mdrun v2.05 as well (besides DL-errors):
886708:
08:21:53 (16919): wrapper: running 7za.exe (a out.7z md.gro md.trr)
terminate called after throwing an instance of 'std::out_of_range'
what(): basic_string::substr
SIGABRT: abort called
Stack trace (16 frames):
mdrun_0.205_x86_64-pc-linux-gnu(boinc_catch_signal+0x67)[0x805c7d7]
[0xffffe500]
[0xffffe410]
/lib32/libc.so.6(gsignal+0x50)[0xf7db49a0]
/lib32/libc.so.6(abort+0x188)[0xf7db6368]
mdrun_0.205_x86_64-pc-linux-gnu[0x8053a80]
mdrun_0.205_x86_64-pc-linux-gnu[0x8051b45]
mdrun_0.205_x86_64-pc-linux-gnu[0x8051b82]
mdrun_0.205_x86_64-pc-linux-gnu[0x8051a2a]
mdrun_0.205_x86_64-pc-linux-gnu[0x804d900]
mdrun_0.205_x86_64-pc-linux-gnu[0x804fab4]
mdrun_0.205_x86_64-pc-linux-gnu[0x804a898]
mdrun_0.205_x86_64-pc-linux-gnu[0x804aa42]
mdrun_0.205_x86_64-pc-linux-gnu[0x804b9bf]
/lib32/libc.so.6(__libc_start_main+0xe5)[0xf7d9f775]
mdrun_0.205_x86_64-pc-linux-gnu[0x804a4a1]

Exiting...


and 886736:

08:39:58 (17572): wrapper: running 7za.exe (a out.7z md.gro md.trr)
terminate called after throwing an instance of 'std::out_of_range'
what(): basic_string::substr
SIGABRT: abort called
Stack trace (16 frames):
mdrun_0.205_x86_64-pc-linux-gnu(boinc_catch_signal+0x67)[0x805c7d7]
[0xffffe500]
[0xffffe410]
/lib32/libc.so.6(gsignal+0x50)[0xf7db19a0]
/lib32/libc.so.6(abort+0x188)[0xf7db3368]
mdrun_0.205_x86_64-pc-linux-gnu[0x8053a80]
mdrun_0.205_x86_64-pc-linux-gnu[0x8051b45]
mdrun_0.205_x86_64-pc-linux-gnu[0x8051b82]
mdrun_0.205_x86_64-pc-linux-gnu[0x8051a2a]
mdrun_0.205_x86_64-pc-linux-gnu[0x804d900]
mdrun_0.205_x86_64-pc-linux-gnu[0x804fab4]
mdrun_0.205_x86_64-pc-linux-gnu[0x804a898]
mdrun_0.205_x86_64-pc-linux-gnu[0x804aa42]
mdrun_0.205_x86_64-pc-linux-gnu[0x804b9bf]
/lib32/libc.so.6(__libc_start_main+0xe5)[0xf7d9c775]
mdrun_0.205_x86_64-pc-linux-gnu[0x804a4a1]

Exiting...


Though not all seem to crash, this one (886583) finished and got validated:
07:18:19 (14454): wrapper: running 7za.exe (a out.7z md.gro md.trr)
07:18:28 (14454): called boinc_finish
19) Message boards : Number crunching : Estimated WU duration = 00:00:00 - WU hasn't even started (Message 1351)
Posted 19 Sep 2009 by Profile Saenger
Post:
Before I set it to accept work again: Have you as well limited the amount of WUs per core significantly? Otherwise it's bad behaviour towards the other dozen projects on my computer will not make it possible to reactivate it. As long as I got 200 WUs at once this project is plainly not working properly.

The problem is not the number of results per WU but the number of results per core, that makes the computer unavailable for other projects.
Restrict it to no more than 5 per core at the same time, an it should be fine.
20) Message boards : Number crunching : Estimated WU duration = 00:00:00 - WU hasn't even started (Message 1343)
Posted 18 Sep 2009 by Profile Saenger
Post:
Last time I looked it was at 100 on my machine, a project reset brought it back down to 1.

The main problem with this estimate is that the computer gets loaded with tons of WUs, because they lie to the manager and the scheduler that they will take no time, but soon after starting they will change to panic mode and block the puter for all other projects.
I don't know how this could be done, but the estimate needs to be set to something far higher or the maximum number of WUs per core has to be set to something far lower to keep this project remotely friendly in a multi-project environment.

Best: fix estimate to proper values.
As long as that's not possible: No more than 5 WU per core at the same time.


Next 20


©2017 All rights reserved | Design by Digital BioPharm Ltd