...
Authorization issue:
- Problem:
- user tried to use CLI client (fts-rest-transfer-submit) to trigger FTS transfer but the CLI client returns errors indicating that the request is not authorized
- RemedySteps to solve the problem:
- (1) check the status of the grid proxy (grid/voms-proxy-info command output);
- (2) examine the output of the command; it should contain the proxy expiration time; examine if the proxy is still valid;
- (a3) If the proxy is not valid, initialise the proxy (grid-proxy-init or voms-proxy-init) and re-run the FTS client command;
- (b) if the proxy is valid check if you're specifying the transfer endpoints properly (see next help topic);(3) 4) refer the FTS CLI tool documentation;
- (45) refer the grid/voms-proxy* CLI commands documentation;
...
- Problem:
- tried to use CLI client to trigger FTS transfer but the CLI client returns errors indicating that the transfer did not start or the transfer status checking tool returns no output or transfer errors:
- Steps to solve the problemRemedy:
- (0) check if the request is authorized properly - see the previous help topic
- (1) Examine your input to the FTS client command (CLI): it should include 2 parts: (a) GridFTP source endpoint with URL; (b) GridFTP target endpoint with URL;
- (2) if the list of endpoint is incomplete, use the use the correct syntax to issue the command; refer to relevant documentation;rerun the command;
- (3) if the input is complete, , but the transfer jobs do not start,, compare the endpoints with the list of the EOSC EU Node endpoints (see table above); at least one of the endpoints should be within EOSC EU Node - specified as target or source of the data transfer); if it is not the case, correct your command's input so that that the transfer will be initiated among proper GridFTP transfer endpoints including FTS server within EOSC EU node;
- (4) refer the FTS CLI tool documentation;
...