TaskController Error Codes (MRv1)
This table shows some of the error codes and messages generated by TaskController in MapReduce (MRv1).
| Numeric Code | Name | Description | 
|---|---|---|
| 1 | INVALID_ARGUMENT_NUMBER | 
 | 
| 2 | INVALID_USER_NAME | The user passed to the task-controller does not exist. | 
| 3 | INVALID_COMMAND_PROVIDED | The task-controller does not recognize the command it was asked to execute. | 
| 4 | SUPER_USER_NOT_ALLOWED_TO_RUN_TASKS | The user passed to the task-controller was the super user. | 
| 5 | INVALID_TT_ROOT | The passed TaskTracker root does not match the configured TaskTracker root (mapred.local.dir), or does not exist. | 
| 6 | SETUID_OPER_FAILED | Either could not read the local groups database, or could not set UID or GID | 
| 7 | UNABLE_TO_EXECUTE_TASK_SCRIPT | The task-controller could not execute the task launcher script. | 
| 8 | UNABLE_TO_KILL_TASK | The task-controller could not kill the task it was passed. | 
| 9 | INVALID_TASK_PID | The PID passed to the task-controller was negative or 0. | 
| 10 | ERROR_RESOLVING_FILE_PATH | The task-controller could not resolve the path of the task launcher script file. | 
| 11 | RELATIVE_PATH_COMPONENTS_IN_FILE_PATH | The path to the task launcher script file contains relative components (for example, ".."). | 
| 12 | UNABLE_TO_STAT_FILE | The task-controller did not have permission to stat a file it needed to check the ownership of. | 
| 13 | FILE_NOT_OWNED_BY_TASKTRACKER | A file which the task-controller must change the ownership of has the wrong the ownership. | 
| 14 | PREPARE_ATTEMPT_DIRECTORIES_FAILED | The mapred.local.dir is not configured, could not be read by the task-controller, or could not have its ownership secured. | 
| 15 | INITIALIZE_JOB_FAILED | The task-controller could not get, stat, or secure the job directory or job working working directory. | 
| 16 | PREPARE_TASK_LOGS_FAILED | The task-controller could not find or could not change the ownership of the task log directory to the passed user. | 
| 17 | INVALID_TT_LOG_DIR | The hadoop.log.dir is not configured. | 
| 18 | OUT_OF_MEMORY | The task-controller could not determine the job directory path or the task launcher script path. | 
| 19 | INITIALIZE_DISTCACHEFILE_FAILED | Could not get a unique value for, stat, or the local distributed cache directory. | 
| 20 | INITIALIZE_USER_FAILED | Could not get, stat, or secure the per-user task tracker directory. | 
| 21 | UNABLE_TO_BUILD_PATH | The task-controller could not concatenate two paths, most likely because it ran out of memory. | 
| 22 | INVALID_TASKCONTROLLER_PERMISSIONS | The task-controller binary does not have the correct permissions set. See Information about Other Hadoop Security Programs. | 
| 23 | PREPARE_JOB_LOGS_FAILED | The task-controller could not find or could not change the ownership of the job log directory to the passed user. | 
| 24 | INVALID_CONFIG_FILE | The taskcontroller.cfg file is missing, malformed, or has incorrect permissions. | 
| 255 | Unknown Error | Several possible causes for this error, including: 
 | 
| << YARN, MRv1, and Linux OS Security | ©2016 Cloudera, Inc. All rights reserved | ContainerExecutor Error Codes (YARN) >> | 
| Terms and Conditions Privacy Policy |