Common Job Errors
This is a list of common job error messages found within the Job Log for all KBase Apps, what they mean and how to go about fixing them or if a job ticket needs to be submitted.
You can always submit a ticket for help, questions, or follow-up to the KBase Help Board.

Types of Errors

    UE=User fixable or possible user error
    KE=KBase error
    UK=Unknown or multiple possibles causes
    TE=Temporary system problem
Use your Browser's search tool to paste in your error message to locate your error message and next steps.

Common Job Error Messages

(2, No such file or directory)

UK: The app did not produce any output or it produced output but none passed the filters. There may also be app-specific reasons described below.
Check the logs for more information and adjust filters as needed.

Unable to build output viewer

UK: The job ran for more than 7 days and crashed. There is no output. Dependent on the reason for the crash, rerunning the job may work.
Resubmit job.

Output file is not found, exit code 123

UK: No space left on device. The job may be too big for KBase in the current configuration.
Resubmit job to make certain the issue isn’t a conflict with other jobs. If this doesn’t work, submit a ticket to the Help Board.

Output file is not found, exit code is 137

UK: Cause unknown. Job probably cancelled by another process but not the user.
Resubmit job.

Job was cancelled as it ran overMax allotted time (604800000) milliseconds (10080) minutes

UE: Job ran for more than 7 days and finished cleanly. Likely the job is too big.
Resubmit job, dependent on the reason it took so long.

'listener timeout after waiting for [600000] ms'

TE: The utility ElasticSearch went down. The fix is a manual process and may not get fixed during nights, weekends, and holidays.
Submit a ticket the the Help Board. Resubmitting the job every couple of hours until it runs may also work.

kafka

TE: Any messages with the word kafka in the error. Something went wrong with the system.
Resubmit job. Report the issue to the Help Board if resubmitting doesn’t fix the problem.

ProtocolError, Connection aborted., BadStatusLine

UK: Something went wrong with the reporting and cleanup at the end of the job. Intermittent error. The data is fine, but there will be no report at the end. If an object was created, clicking on it in the data panel will create a viewer for the object, which is likely missing.
Resubmit job if you need the end report.

User XXXX may not read workspace nnnnn

UE: The app requires data owned by another user and you do not have access. In another scenario, either you or the user have deleted the original file.
Ask the user for access to the needed file or re-import file if deleted.
TE: A component in KBase needed to be rebooted and will recover in a few minutes.
Try resubmitting the job in 10-15 minutes.

No such container:...

TE: A known temporary error.
Resubmit job.

Token validation failed: Too many open files'

TE: A known temporary error .
Try resubmitting the job in 10-15 minutes.

502 Server Error: Bad Gateway….

TE: A known temporary error.
Resubmit job.

Gee whiz, I sure am sorry, but an error occurred. Gosh!...... Object 19 cannot be accessed

UE: User’s browser cache is retaining old information. In this case, it is 'Object 19'. One symptom is that the user gets the error but the narrative looks fine to others.
Try the following:
    Reload the page
    Close and reopen your narrative
    Log out and log back in again
    Clear your cache
If you find something that works, no need to try the others.

Details: 500 globus_xio: ICE negotiation failed.

UE: The error generally indicate a firewall issue.
Please refer to this question on the Globus forum for a similar question with its solution. If you are working from home, you can view the Globus documentation for configuring the firewall. If you are on an institution network, you'll probably have to request an exception from IT.
Last modified 10mo ago