Error codes#

This pages gives an overview of the error codes in auto-icon.

Note

auto-icon error codes are always 3-digit.
4-digit error codes are Autosubmit error codes.

Errors with user input [4xx]#

Most of these errors are due to an invalid user input or configuration. The error message and/or the description below shall give you a hint how to correct the input. If the issue cannot be solve, you can get in contact.

Error codes are in the ranges:

  • 40x: Init script

  • 41x - 44x: Core functionality and general error codes

  • 45x - 46x: specific to pre-processing jobs

  • 47x - 48x: specific to post-processing jobs

  • 49x: others

Code

Error and solution

400

Invalid user input. Check out the detailed error message or the help text for correct input.

401

Init script not started from the root of an Autosubmit experiment. Start from the root, i.e. your <expid>/ directory.

402

Configuration input file in the minimal configuration <expid>/conf/minimal.yml not found. The section DEFAULT.CUSTOM_CONFIG was not found.

410

Working directory (OUTDIR) is not empty, but the switch REQUIRE_CLEAN_OUTDIR (in conf/<icon_case>/simulation.yml) is set to True. Either set the switch to false (to overwrite content) or clear the working directory.

411

Invalid experiment configuration. Check the value of the indicated field(s) in your configuration.

412

(Internal) workflow data file not found or corrupt. Check your configuration and rerun the PRE_FIND_FILES job and try again. If the error persists, please report it to the developers.

413

Internal configuration invalid. Check the named configuration setting. If you did change this setting, you entered an illegal value. If you did not, this is probably a bug, please report in that case.

414

Runtime error closely related to user input. Check out the error message and revise your configuration accordingly.

415

(HPC software) module could not be loaded.

416

Branch cannot be checked out. Check the branch name and the detailed git error message. You can resolve the issue manually (checking out the correct branch) and rerun the job.

417

Error in preparing the installation directory. Check the error message and resolve the issue.

420

Validation of namelist failed. Please check the fields indicated by the error message.

421

File checking error. A file check was requested by some user configuration and failed.

470

File exists error: a simulation output file might be overwritten. Double-check configuration and potentially activate explicitly the overwriting.

471

File exists error: a post-processed or visualization file might be overwritten. Double-check configuration and potentially activate explicitly the overwriting.

472

File corrupt. Check the file. If the file is as expected, try rerunning the job. If the problem persists, please report.

Internal errors [5xx]#

Most of these errors point towards an issue in auto-icon and thus, should be reported to the developers at DKRZ Gitlab or Gitlab.com.

Error codes are in the ranges:

  • 50x: Init script

  • 51x - 54x: Core functionality and general error codes

  • 55x - 56x: specific to pre-processing jobs

  • 57x - 58x: specific to post-processing jobs

  • 59x: others

Code

Error

500

The init script was not able to successfully apply the configurations requested. You can continue but should check out the respective configuration file for correctness.

510

Internal validation error. This is a clear indication of a bug. Please report it.

511

Internally stored file handle invalid. If during preparation, try re-running the PRE_FIND_FILES job, if during post-processing, try to rerun the whole post-processing chain. If the error persists, it is a clear indication of a bug. Please report it.

512

Internal error related to experiment configuration, but not directly derived from it. Cross-check the related input. If it is correct, please report.

513

Unexpected file-related runtime error. Please try again. If the error persists, please report.

Other errors [9xx]#

Code

Error

900

Not implemented. This use case is not implemented. If the feature is key for you, please consider creating a feature request by filing an issue.

901

Feature pending implementation. You can check the status in the issues and possibly raise awareness and priority by contributing your use case.