next up previous contents index
Next: 8.2.3 Strategy for Coping Up: 8.2 Error Checking Previous: 8.2.1 Errors at the   Contents   Index

8.2.2 Errors at the 'Get' Step

At the 'Get' step, if you get 'Status=WAITING' it means that either the search request is waiting to be processed or the result is not yet ready. Do not resubmit this search again.

If the query is lost for some unknown reason, you will get 'Status=UNKNOWN', 'Status=ERROR', or other errors/warnings outside the QBlastInfo section. In these cases, stop your script and contact [blast-help@ncbi.nlm.nih.gov] as soon as possible. Please include the RIDs in question. If you are receiving no results from the BLAST server, do not rerun your scripts; contact blast-help and provide the details. Our staff will look into the problem. Representative error messages are given below.

Table 8.2.2 Selective Error/Warning Messages for Get Step
Error/Warning Messages Meaning
Error: 500, Error: 502, Error: 803 From Web front end
ERROR: Invalid RID: ... RID provided is incorrect
INFO: [blastsrv4.REAL]: Error: CPU usage limit was exceeded, resulting in SIGXCPU (24). CPU limit exceeded *
ERROR: An error has occurred on the server, Too many HSPs to save all Too many HSPs to process due to loose search settings
INFO: Failure to set-up BLAST search with database '...' The specified database may be missing or corrupted
INFO: No sequences corresponding to the entrez query ... were found in the ... database The Entrez Limit applied did not work properly for various reasons
ERROR: INFO: an error has occurred on the server, search failed. Search against a portion of the database did not return results properly causing the whole search to fail
ERROR: Results for RID AJ0193G101T not found RID has expired or is incorrect

Note: Currently, the CPU limit is set at 60 minutes per search request.


next up previous contents index
Next: 8.2.3 Strategy for Coping Up: 8.2 Error Checking Previous: 8.2.1 Errors at the   Contents   Index
Tao Tao 2007-08-03