Message boards : Number crunching : Error while computing
Author | Message |
---|---|
Waldmeisda Send message Joined: 2 Apr 20 Posts: 4 Credit: 784,060 RAC: 0 |
Hi, is this https://boinc.bakerlab.org/rosetta/results.php?hostid=4012859&offset=0&show_names=0&state=6&appid= something I should be worried about? BR |
Grant (SSSF) Send message Joined: 28 Mar 20 Posts: 1673 Credit: 17,603,339 RAC: 22,064 |
Hi,Nope. There is a dodgy batch of Rosetta Mini work out there at the moment. Instant crash & burn. Grant Darwin NT |
JAMES Send message Joined: 5 May 07 Posts: 8 Credit: 275,386 RAC: 0 |
I am wondering why this WU failed. The reason for the failure is listed as ERROR: Cannot determine file type. Is the flaw in the WU itself or is there something wrong with my machine. Name ee27414dde8c97a82e07d60c68ffe3c8_dock_ens_20_04_15_28_09_localDocking_0_SAVE_ALL_OUT_910172_13_0y Workunit 1032284779 Created 12 Apr 2020, 0:35:52 UTC Sent 12 Apr 2020, 1:04:16 UTC Report deadline 15 Apr 2020, 1:04:16 UTC Received 12 Apr 2020, 20:39:41 UTC Server state Over Outcome Computation error Client state Compute error Exit status 1 (0x00000001) Unknown error code Computer ID 4053797 Run time 1 min 10 sec CPU time 21 sec Validate state Invalid Credit 0.00 Device peak FLOPS 3.26 GFLOPS Application version Rosetta v4.15 windows_x86_64 Peak working set size 95.40 MB Peak swap size 77.22 MB Peak disk usage 0.01 MB Stderr output <core_client_version>7.14.2</core_client_version> <![CDATA[ <message> Incorrect function. (0x1) - exit code 1 (0x1)</message> <stderr_txt> command: projects/boinc.bakerlab.org_rosetta/rosetta_4.15_windows_x86_64.exe -silent_gz -mute all -s chainA_chainB_20_04_15_28_09.pdb -run:protocol jd2_scripting -jd2:dd_parser -parser:protocol local_docking_20_04_15_28_09.xml -out:nstruct 10000 -jd2:ntrials 100 -ex1 -ex2aro -beta -use_input_sc -in:file:native chainA_chainB_20_04_15_28_09.pdb -out:file:silent default.out -out:file:silent_struct_type protein -run:write_failures false -nstruct 10000 -cpu_run_time 28800 -watchdog -boinc:max_nstruct 600 -checkpoint_interval 120 -database minirosetta_database -in::file::zip minirosetta_database.zip -boinc::watchdog -run::rng mt19937 -constant_seed -jran 3996948 ERROR: Cannot determine file type. Current supported types are: PDB, CIF, SRLZ, MMTF ERROR:: Exit from: ......srccoreimport_poseimport_pose.cc line: 380 BOINC:: Error reading and gzipping output datafile: default.out 15:39:17 (172): called boinc_finish(1) </stderr_txt> |
Grant (SSSF) Send message Joined: 28 Mar 20 Posts: 1673 Credit: 17,603,339 RAC: 22,064 |
I am wondering why this WU failed. The reason for the failure is listed as ERROR: Cannot determine file type. Is the flaw in the WU itself or is there something wrong with my machine.Dodgy Task, plenty about. _localDocking_ are broken. _globalDocking_ are OK (or at least the one i did was). Grant Darwin NT |
Grant (SSSF) Send message Joined: 28 Mar 20 Posts: 1673 Credit: 17,603,339 RAC: 22,064 |
I am wondering why this WU failed. The reason for the failure is listed as ERROR: Cannot determine file type. Is the flaw in the WU itself or is there something wrong with my machine.See the second post in this thread. Grant Darwin NT |
JAMES Send message Joined: 5 May 07 Posts: 8 Credit: 275,386 RAC: 0 |
I am wondering why this WU failed. The reason for the failure is listed as ERROR: Cannot determine file type. Is the flaw in the WU itself or is there something wrong with my machine.See the second post in this thread. Thanks. At least they crash fast (1m 10sec) and don't waste a lot CPU time. |
Holdolin Send message Joined: 19 Mar 20 Posts: 4 Credit: 2,431,917 RAC: 0 |
I am wondering why this WU failed. The reason for the failure is listed as ERROR: Cannot determine file type. Is the flaw in the WU itself or is there something wrong with my machine.See the second post in this thread. Indeed. Came to this thread like the rest of you looking for a reason. |
Message boards :
Number crunching :
Error while computing
©2024 University of Washington
https://www.bakerlab.org