Message boards :
Sixtrack Application :
Error fort.93
Message board moderation
Author | Message |
---|---|
![]() Send message Joined: 15 Jun 08 Posts: 2285 Credit: 207,450,084 RAC: 141,448 ![]() ![]() ![]() |
The recent Sixtrack batch causes lots of errors. See the examples below. This may be checked by the project team. https://lhcathome.cern.ch/lhcathome/result.php?resultid=181945166 https://lhcathome.cern.ch/lhcathome/result.php?resultid=181945168 https://lhcathome.cern.ch/lhcathome/result.php?resultid=181944837 https://lhcathome.cern.ch/lhcathome/result.php?resultid=181940413 process exited with code 255 (0xff, -1)</message> <stderr_txt> 14:06:03 (43477): called boinc_finish(-1) ******* Last 40 lines of file 'fort.93': ******* UNIT 82 opened F UNIT 83 opened F etc etc etc |
Send message Joined: 11 Dec 09 Posts: 27 Credit: 236,713,617 RAC: 0 |
Hello, Same for me! All the task i recently received (+800) got this error: <core_client_version>7.6.9</core_client_version> <![CDATA[ <message> process exited with code 255 (0xff, -1) </message> <stderr_txt> 14:38:53 (4947): called boinc_finish(-1) ******* Last 40 lines of file 'fort.93 ': ******* UNIT 82 opened F UNIT 83 opened F UNIT 84 opened F UNIT 85 opened F UNIT 86 opened F UNIT 87 opened F UNIT 88 opened F UNIT 89 opened F UNIT 90 opened F UNIT 91 opened F UNIT 92 opened F UNIT 93 opened T UNIT 94 opened F UNIT 95 opened F UNIT 96 opened F UNIT 97 opened F UNIT 98 opened F UNIT 99 opened F UNIT 100 opened F UNIT 101 opened F UNIT 102 opened F UNIT 103 opened F UNIT 104 opened F UNIT 105 opened F UNIT 106 opened F UNIT 107 opened F UNIT 108 opened F UNIT 109 opened F UNIT 110 opened F UNIT 111 opened F UNIT 112 opened F UNIT 113 opened F UNIT 114 opened F UNIT 115 opened F UNIT 116 opened F UNIT 117 opened F UNIT 118 opened F UNIT 119 opened F UNIT 120 opened F ******* Done writing tail of file 'fort.93 ' to stderr ******* ******* Last 40 lines of file 'fort.6 ': ******* RANDOM NUMBERS GENERATED: 3000000 MEAN VALUE= -0.0001176 - DEVIATION= 0.9867194 Random distribution has been cut to: 3 sigma. ----------------------------------------------------------------------------------------------------------------------------------- Multipole errors read in from external file From file fort.16 : 4792 values read in. Alignment errors read in from external file From file fort.8 : 104 values read in. Un-identified SINGLE ELEMENT 'ip3..2 ' in block DUMP (fort.3) parsed line: ip3..2 1 1032 2 IP3_DUMP_2 411 4506 ++++++++++++++++++++++++ +++++ERROR DETECTED+++++ ++++++++++++++++++++++++ RUN TERMINATED ABNORMALLY !!! *** ERROR ***,PROBLEMS WRITING TO FILE 10 FROM ABEND ERROR CODE : 5001 SIXTRACR stop ******* Done writing tail of file 'fort.6 ' to stderr ******* </stderr_txt> ]]> |
Send message Joined: 29 Feb 16 Posts: 157 Credit: 2,659,975 RAC: 0 ![]() ![]() |
Hello, Apologies for the errors - one of our users sent out jobs with inconsistent input files, which generate the errors you got. He has stopped the original submission and proceed with the correct inputs. Please abort all the tasks named workspace1* that you have received till early this afternoon. Thanks for the quick feedback. Cheers, A. |
Send message Joined: 11 Dec 09 Posts: 27 Credit: 236,713,617 RAC: 0 |
Thank you for the info! Can you cancel theses tasks on the server side to prevent them from being re-sent ? Thanks! |
![]() ![]() Send message Joined: 29 Sep 04 Posts: 281 Credit: 11,835,327 RAC: 162 ![]() ![]() |
I had loads of errant workspace1_hl13..... tasks today that failed after only a few seconds but this one, that arrived at 19:35 UTC, seems to be running fine. 4 mins in, 5% progress, 52 mins estimated remaining. |
Send message Joined: 29 Feb 16 Posts: 157 Credit: 2,659,975 RAC: 0 ![]() ![]() |
Hi Ray, thanks for confirming that re-submission was successful. Concerning cancellation of tasks, the operation is a bit difficult, as the study name (which is part of the task names) was not changed, making cancellation more surgical. Making out best not to kill any proper task. Thanks! A. |
©2023 CERN