Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
titleMain steps:
  • We strongly recommend users to read our ECMWF Service Status and the WebAPI FAQ before reporting the problem
  • If the problem you are experiencing is included in the troubleshooting list below, please follow the corresponding instructions.
  • If you are still experiencing problems, or if the problem is NOT included in the troubleshooting list below, please feel free to report the problem

Info

(lightbulb) (lightbulb) Before you report any problem please note that usually on Wednesdays, we carry out service maintenance sessions, which may affect the availability of the Web-API service.

  • For real time information please visit the ECMWF Service Status area.     
  • Please note that Web API availability, depends on the availability of other services like MARS, INTERNET and WEB-SERVICES.


...

Your job list

Info
titleYour job list

(lightbulb) (lightbulb) Your job list is important for tracing back and debugging your requests. It includes plenty of useful information, like the following:

  • job id,
  • user login,
  • status of your request,
  • duration of your request,
  • details of your request (ie what you have requested),
  • log messages of your request (ie the feedback from our servers).  
  • an option to cancel a request (sad) (sad)

 

Info
titlekilling or cancelling a request?

(warning) (warning) If you kill a Web-API request on your local environment (e.g. by CTRL+C), the corresponding job, on the web-API service level, is NOT cancelled but still running. In that case please keep in mind the following:

  • Your request will continue to be visible in your job list
  • If you wish to cancel it please use the corresponding option on your job list
  • Once you have cancelled it, the request status will become aborted.
  • Due to the "max active requests per user" limitation, killing or cancelling requests may affect the performance of your other submitted requests.


...

Info
  • Check the status of your request in your job list
  • If your request is not in your job list please report the problem
  • If your request is in your job list and the status has been "queued", for a long time, we recommend you the following:
    • Check the Nr of your "active" and "queued" requests. Please keep in mind that a limitation of  3  "active" requests/per user has been set to improve the service
    • Have a look on the Web-API activity to check the current status of our service.(ie if the service is busy you will see plenty of "queued"  requests). You may also wish to check our  MARS activity
  • If your long running request is in your job list and the  status  is "active"it means that your request is currently handled by MARS but for some reasons it is slow.
    In this case we recommend you the following:

 

Info

(lightbulb) (lightbulb) Please keep in mind the following:

  • Many requests submitted by other users may be running in parallel consuming the services resources (MARS slots, Web-API slots, Tapes etc)
  • A limitation of  3 "active" requests  and 20 "queued" requests per user has been set to improve the service
  • Read carefully our retrieval efficiency pages and check if you can split your big requests
  • Read the efficiency tips below:

Info
titleEfficiency tips
  • Smaller Nr of tapes (a request accesses) means better request efficiency.
  • Ideally requests should not access more than 1 tape.
  • Requests for data which is online in general go faster
  • All this information above, can be found in MARS activity



...

Invalid or missing key or token

 

...

Make

...

sure

...

you

...

get

...

a

...

valid key

...

from

...

https://api.ecmwf.int/v1/key/.

...

The

...

file

...

in

...

$HOME/.ecmwfapirc

...

 should contain

...

something

...

like:

...

No Format
{
    "url"   : "https://api.ecmwf.int/v1",
    "key"   : "XXXXXXXXXXXXXXXXXXXXXX",
    "email" : "john.smith@example.com"
}

Including

...

the

...

curly

...

brackets.

Python issues

ECMWF API at None

...

Info
This means that the Web API client script failed to transfer the data from the ECMWF servers to your local machine. The reasons can be:
  • Connectivity network issues.
  • Local disk space or file systems issues

(lightbulb) (lightbulb) Check if the results are still available in your job list

(smile)(smile) If not, you may wish to rerun the request

(warning) (warning) Check if you have installed the latest api client from our Web-API Downloads

...

Info

MARS messages

Info

(lightbulb) (lightbulb) It is very important users to be aware of the MARS messages:

INFOrequest being processed and a report on the execution at the end
DEBUGadditional information if debugging is switched on
WARNINGany unusual aspect of the execution
ERRORsystem or data errors which do not stop MARS execution
FATALterminates the execution of MARS


...