Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
public:lta_faq [2020-11-04 15:05] – Bernard Asabere | public:lta_faq [2023-02-17 10:48] (current) – Hanno Holties | ||
---|---|---|---|
Line 14: | Line 14: | ||
* **Q**: [[: | * **Q**: [[: | ||
* **Q**: [[: | * **Q**: [[: | ||
- | * **Q**: [[: | + | * **Q**: [[: |
==== Troubleshoot ==== | ==== Troubleshoot ==== | ||
Line 56: | Line 56: | ||
Note that the larger your request, the longer it takes until you can retrieve the first file. Also, please limit the number of requests running in parallel to a few, especially when they contain many files. In principle, we avoid introducing hard limits, but rely on reasonable user behavior. This also means that you can block the system for a long time or, in the worst case, even bring it down. So please act responsibly or we might have to enforce some limits in the future to keep the system available for other users. Be aware, that we may cancel your request(s) in excessive cases to maintain LTA operation. | Note that the larger your request, the longer it takes until you can retrieve the first file. Also, please limit the number of requests running in parallel to a few, especially when they contain many files. In principle, we avoid introducing hard limits, but rely on reasonable user behavior. This also means that you can block the system for a long time or, in the worst case, even bring it down. So please act responsibly or we might have to enforce some limits in the future to keep the system available for other users. Be aware, that we may cancel your request(s) in excessive cases to maintain LTA operation. | ||
- | If you, by accident, staged some 100' | + | If you, by accident, staged some 100' |
=== What is all this SRM / ' | === What is all this SRM / ' | ||
- | These are technical terms that refer to the storage backend of the LTA. Each of the three LTA sites (in Amsterdam, Juelich and Groningen) operates an SRM (Storage Resource Management) system. Each SRM system consists of magnetic tape storage and hard disk storage. Both are addressed by a common file system, where each file has a specific locality: it can be either on disk (' | + | These are technical terms that refer to the storage backend of the LTA. Each of the three LTA sites (in Amsterdam, Juelich, and Poznan) operates an SRM (Storage Resource Management) system. Each SRM system consists of magnetic tape storage and hard disk storage. Both are addressed by a common file system, where each file has a specific locality: it can be either on disk (' |
Usually, you don't have to worry about the details. But be aware, that data retrieval is a two-step procedure: 1) preparation for download (' | Usually, you don't have to worry about the details. But be aware, that data retrieval is a two-step procedure: 1) preparation for download (' | ||
Line 66: | Line 66: | ||
=== Do I have to make new requests via the web catalog? === | === Do I have to make new requests via the web catalog? === | ||
- | In principle, yes, this is the only supported procedure, at the moment. There are development versions of programming interfaces, with which it is possible to query the catalog and talk to the staging service, e.g. from scripts. But these are not generally made available, unsupported and still in development. If you are an ' | + | In principle, yes, this is the only supported procedure, at the moment. There are development versions of programming interfaces, with which it is possible to query the catalog and talk to the staging service, e.g. from scripts. But these are not generally made available, unsupported and still in development. If you are an ' |
=== There are different ways to download. Which one is the best? === | === There are different ways to download. Which one is the best? === | ||
Line 103: | Line 103: | ||
=== I did not receive a mail notification that my request was scheduled! === | === I did not receive a mail notification that my request was scheduled! === | ||
- | If the LTA catalog did not show any error when you submitted your request, then it is safe to assume that your request was registered in our staging system. Usually, you should get a notification mail that this has happened within a few minutes. If you did not receive the notification within an hour, then our staging service may be down. Note that your request is not lost in this case and will be picked up after the service is back online. In urgent cases or if you are not sure that something went wrong while submitting your request, please contact the [[https:// | + | If the LTA catalog did not show any error when you submitted your request, then it is safe to assume that your request was registered in our staging system. Usually, you should get a notification mail that this has happened within a few minutes. If you did not receive the notification within an hour, then our staging service may be down. Note that your request is not lost in this case and will be picked up after the service is back online. In urgent cases or if you are not sure that something went wrong while submitting your request, please contact the [[https:// |
=== I did not receive a mail notification that my data is ready for retrieval! Has my request gone lost? === | === I did not receive a mail notification that my data is ready for retrieval! Has my request gone lost? === | ||
- | After you got a notification that your requests was scheduled, it is in our database and there' | + | After you got a notification that your requests was scheduled, it is in our database and there' |
- | It is not alarming when your request did not finish in 24 hours, even when your last request finished within 10 minutes. In urgent cases or if you did not receive a notification after 48 hours, please contact the [[https:// | + | It is not alarming when your request did not finish in 24 hours, even when your last request finished within 10 minutes. In urgent cases or if you did not receive a notification after 48 hours, please contact the [[https:// |
=== I got an email that says my staging request has failed! What happened? === | === I got an email that says my staging request has failed! What happened? === | ||
- | This means that the SRM server could not fulfill the request at all. This might mean that the system itself is fine, but none of the files from your request could be staged (e.g. missing files). Check the error message from your mail notification for details. The notification can also indicate that there is a general problem with the SRM system or with the staging service itself, i.e. something is broken or down for maintenance. We try to detect all temporary issues and only inform users in case that something is wrong with their request itself, but we cannot foresee all eventualities. If you cannot make sense out of the error message, or don't know how to deal with it, please contact the [[https:// | + | This means that the SRM server could not fulfill the request at all. This might mean that the system itself is fine, but none of the files from your request could be staged (e.g. missing files). Check the error message from your mail notification for details. The notification can also indicate that there is a general problem with the SRM system or with the staging service itself, i.e. something is broken or down for maintenance. We try to detect all temporary issues and only inform users in case that something is wrong with their request itself, but we cannot foresee all eventualities. If you cannot make sense out of the error message, or don't know how to deal with it, please contact the [[https:// |
If you used the xmlrpc interface to submit your request, please first check whether you made a mistake and e.g. entered the wrong SURLs. | If you used the xmlrpc interface to submit your request, please first check whether you made a mistake and e.g. entered the wrong SURLs. | ||
Line 121: | Line 121: | ||
=== I got an email that says my staging request was only partially successful! What's going on? === | === I got an email that says my staging request was only partially successful! What's going on? === | ||
- | In general, this means that the SRM system works fine, but there was a problem processing your request. As a result, some of your files could be [[: | + | In general, this means that the SRM system works fine, but there was a problem processing your request. As a result, some of your files could be [[: |
If you used the xmlrpc interface to submit your request, please first check whether you made a mistake and e.g. entered the wrong SURLs. | If you used the xmlrpc interface to submit your request, please first check whether you made a mistake and e.g. entered the wrong SURLs. | ||
Line 129: | Line 129: | ||
=== Oops! I made a mistake! How can I stop a request? === | === Oops! I made a mistake! How can I stop a request? === | ||
- | Unfortunately, | + | Unfortunately, |
=== My files only contain some error message instead of data === | === My files only contain some error message instead of data === | ||
- | Most errors should result in a 404/50x return code. However, some error messages are still returned as a message. Please read the error message carefully. In many cases, it should give you some indication of what went wrong. If this does not help you, please contact the [[https:// | + | Most errors should result in a 404/50x return code. However, some error messages are still returned as a message. Please read the error message carefully. In many cases, it should give you some indication of what went wrong. If this does not help you, please contact the [[https:// |
**Important: | **Important: | ||
Line 139: | Line 139: | ||
=== My data files are corrupted === | === My data files are corrupted === | ||
- | Check if the files are much smaller than you expect. Something might have gone wrong with the transfer. Please check the beginning of your files, e.g. with ' | + | Check if the files are much smaller than you expect. Something might have gone wrong with the transfer. Please check the beginning of your files, e.g. with ' |
=== My downloads fail with error "All Ready slots are taken and Ready Thread Queue is full" === | === My downloads fail with error "All Ready slots are taken and Ready Thread Queue is full" === | ||
Line 147: | Line 147: | ||
=== My downloads don't start / time out === | === My downloads don't start / time out === | ||
- | Maybe the SRM system is down for maintenance, | + | Maybe the SRM system is down for maintenance, |
=== Http downloads randomly fail with "503 Service Temporarily Unavailable" | === Http downloads randomly fail with "503 Service Temporarily Unavailable" | ||
Line 194: | Line 194: | ||
=== SRM/Grid commands fail and I cannot figure out why! === | === SRM/Grid commands fail and I cannot figure out why! === | ||
- | Retry with option ' | + | Retry with option ' |