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 [2018-07-10 09:50] – Marco Iacobelli | public:lta_faq [2023-02-17 10:48] (current) – Hanno Holties | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | =====Long Term Archive Frequently Asked Questions===== | + | ===== Long Term Archive Frequently Asked Questions ===== |
- | This page is targeted at users who want to learn more on the LOFAR LTA (Long Term Archive). | + | This page is targeted at users who want to learn more on the LOFAR LTA (Long Term Archive). It should answer the most common questions and provide help in case of difficulties in data retrieval. If the information on this page did not succeed to solve any issues you may encounter, please submit a support request to the [[https:// |
- | It should answer the most common questions and provide help in case of difficulties in data retrieval. | + | |
- | If the information on this page did not succeed to solve any issues you may encounter, please submit a support request to the [[https:// | + | |
- | =====Questions===== | + | ===== Questions ===== |
==== General ==== | ==== General ==== | ||
- | * **Q**: [[lta_faq#I never worked with the LTA before. Where is a good starting point?|I never worked with the LTA before. Where is a good starting point?]] | + | * **Q**: [[:public:lta_faq#i_never_worked_with_the_lta_before_where_is_a_good_starting_point|I never worked with the LTA before. Where is a good starting point]] |
- | * **Q**: [[lta_faq#Why is data retrieval so difficult?|Why is data retrieval so difficult?]] | + | * **Q**: [[:public:lta_faq#why_is_data_retrieval_so_difficult|Why is data retrieval so difficult]] |
- | * **Q**: [[lta_faq#What is an appropriate amount of data to retrieve?|What is an appropriate amount of data to retrieve?]] | + | * **Q**: [[:public:lta_faq#what_is_an_appropriate_amount_of_data_to_retrieve|What is an appropriate amount of data to retrieve]] |
- | * **Q**: [[lta_faq#What is all this SRM/staging stuff about?|What is all this SRM/staging stuff about?]] | + | * **Q**: [[:public:lta_faq#what_is_all_this_srm_staging_stuff_about|What is all this SRM/staging stuff about]] |
- | * **Q**: [[lta_faq#Do I have to make new requests via the web catalog?|Do I have to make new requests via the web catalog?]] | + | * **Q**: [[:public:lta_faq#do_i_have_to_make_new_requests_via_the_web_catalog|Do I have to make new requests via the web catalog]] |
- | * **Q**: [[lta_faq#There are different ways to download. Which one is the best?|There are different ways to download. Which one is the best?]] | + | * **Q**: [[:public:lta_faq#there_are_different_ways_to_download_which_one_is_the_best|There are different ways to download. Which one is the best]] |
- | * **Q**: [[lta_faq#My downloads are too slow. What can I do?|My download speeds are too slow. What can I do?]] | + | * **Q**: [[:public:lta_faq#my_downloads_are_too_slow_what_can_i_do|My download speeds are too slow. What can I do]] |
- | * **Q**: [[lta_faq# | + | * **Q**: [[:public:lta_faq# |
==== Troubleshoot ==== | ==== Troubleshoot ==== | ||
- | * **Q**: [[lta_faq#I did not receive a mail notification that my request was scheduled!|I did not receive a mail notification that my request was scheduled!]] | + | * **Q**: [[:public:lta_faq#i_did_not_receive_a_mail_notification_that_my_request_was_scheduled|I did not receive a mail notification that my request was scheduled!]] |
- | * **Q**: [[lta_faq#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?]] | + | * **Q**: [[:public:lta_faq#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]] |
- | * **Q**: [[lta_faq#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?]] | + | * **Q**: [[:public:lta_faq#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]] |
- | * **Q**: [[lta_faq#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?]] | + | * **Q**: [[:public:lta_faq#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]] |
- | * **Q**: [[lta_faq#Oops! I made a mistake! How can I stop a request?|Oops! I made a mistake! How can I stop a request?]] | + | * **Q**: [[:public:lta_faq#oops_i_made_a_mistake_how_can_i_stop_a_request|Oops! I made a mistake! How can I stop a request]] |
- | * **Q**: [[lta_faq#My files only contain some error message instead of data|My files only contain some error message instead of data]] | + | * **Q**: [[:public:lta_faq#my_files_only_contain_some_error_message_instead_of_data|My files only contain some error message instead of data]] |
- | * **Q**: [[lta_faq#My data files are corrupted|My data files are corrupted / I cannot unpack my data]] | + | * **Q**: [[:public:lta_faq#my_data_files_are_corrupted|My data files are corrupted / I cannot unpack my data]] |
- | * **Q**: [[lta_faq#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" | + | * **Q**: [[:public:lta_faq#my_downloads_fail_with_error_ckgedit_quot_all_ready_slots_are_taken_and_ready_thread_queue_is_full_ckgedit_quot|My downloads fail with error "All Ready slots are taken and Ready Thread Queue is full" |
- | * **Q**: [[lta_faq#My downloads don't start / time out|My downloads don't start / time out]] | + | * **Q**: [[:public:lta_faq#my_downloads_don_t_start_time_out|My downloads don't start / time out]] |
- | * **Q**: [[lta_faq#Http downloads randomly fail with "503 Service Temporarily Unavailable" | + | * **Q**: [[:public:lta_faq#http_downloads_randomly_fail_with_ckgedit_quot_503_service_temporarily_unavailable_ckgedit_quot|Http downloads randomly fail with "503 Service Temporarily Unavailable" |
- | * **Q**: [[lta_faq#When selecting a project it fails with " | + | * **Q**: [[:public:lta_faq#when_selecting_a_project_it_fails_with_ckgedit_quot_401_-_no_permission_--_see_authorization_schemes_ckgedit_quot|When selecting a project it fails with "401 - No permission -- see authorization schemes" |
- | * **Q**: [[lta_faq#SRM commands fail with error containing "Java heap space"|SRM commands fail with error containing "Java heap space" | + | * **Q**: [[:public:lta_faq#srm_commands_fail_with_error_containing_ckgedit_quot_java_heap_space_ckgedit_quot|SRM commands fail with error containing "Java heap space" |
- | * **Q**: [[lta_faq#SRM commands fail with error '426 Connection refused' | + | * **Q**: [[:public:lta_faq#srm_commands_fail_with_error_426_connection_refused|SRM commands fail with error '426 Connection refused' |
- | * **Q**: [[lta_faq# | + | * **Q**: [[:public:lta_faq# |
- | * **Q**: [[lta_faq#SRM/Grid commands fail and I cannot figure out why!|SRM/Grid commands fail and I cannot figure out why!]] | + | * **Q**: [[:public:lta_faq#srm_grid_commands_fail_and_i_cannot_figure_out_why|SRM/Grid commands fail and I cannot figure out why!]] |
- | + | ===== Answers ===== | |
- | =====Answers===== | + | |
==== General ==== | ==== General ==== | ||
=== I never worked with the LTA before. Where is a good starting point? === | === I never worked with the LTA before. Where is a good starting point? === | ||
- | New users are advised to read through our tutorial page, the [[public: | + | |
+ | New users are advised to read through our tutorial page, the [[:public: | ||
=== Why is data retrieval so difficult? === | === Why is data retrieval so difficult? === | ||
- | It is important to understand the the data volumes of LOFAR are pretty huge and handling them requires different technologies than what we all know and use in our everyday life. For instance, LTA data is [[lta_faq#What is all this SRM/staging stuff about?|stored on magnetic tape and has to be copied to a hard drive (getting ' | + | |
- | We try to make the LTA as convenient to use as possible, e.g. by providing http downloads for users without Grid certificate and portable Grid tools for those who want or need the extra performance. We are aware of the fact that data retrieval is quite close to the backend technology and we hope to be able to provide solutions with higher abstraction in the future. But it will always be necessary to prepare data for the download, so will always have plan a bit ahead, sorry. | + | It is important to understand the the data volumes of LOFAR are pretty huge and handling them requires different technologies than what we all know and use in our everyday life. For instance, LTA data is [[:public:lta_faq#what_is_all_this_srm_staging_stuff_about|stored on magnetic tape and has to be copied to a hard drive (getting ' |
=== What is an appropriate amount of data to retrieve? === | === What is an appropriate amount of data to retrieve? === | ||
- | This depends. | ||
- | As a rule of thumb, we ask you to keep your requests below 5 TB in volume and smaller than 1'000 files. | ||
- | Also, the total file count in all your //running// requests should not exceed 5'000 files at any point in time. | ||
- | In more detail, there are essentially two things | + | This depends. As a rule of thumb, we ask you to keep your requests below 5 TB in volume |
- | The most important thing to know about LTA capabilities, | + | In more detail, there are essentially two things to consider: The capabilities of your own system and the capabilities of the LTA services. |
+ | |||
+ | The most important thing to know about LTA capabilities, | ||
The second most important LTA limit is the number of files that can be processed at the same time. Some projects have not very much data volume, but the data is distributed over very many files. With large file counts, the management of the request itself puts a lot of load on the system. There is a maximum queue size of 10'000 files for all user requests together. So make sure to only occupy a fraction of that and wait until earlier submitted requests have finished (you got notified) before you submit new requests. | The second most important LTA limit is the number of files that can be processed at the same time. Some projects have not very much data volume, but the data is distributed over very many files. With large file counts, the management of the request itself puts a lot of load on the system. There is a maximum queue size of 10'000 files for all user requests together. So make sure to only occupy a fraction of that and wait until earlier submitted requests have finished (you got notified) before you submit new requests. | ||
Line 60: | 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 (' |
- | === 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? === | ||
- | That depends. In short terms: Http downloads are the easiest (e.g. via wget), downloads via SRM tools can be faster and are encouraged for large amounts. | + | That depends. In short terms: Http downloads are the easiest (e.g. via wget), downloads via SRM tools can be faster and are encouraged for large amounts. |
- | The SRM systems which the LTA sites operate are integrated in the Grid. To work with them directly, you need a Grid certificate. To allow users without a Grid certificate to download LTA data, we operate webservers as a frontend to the SRM backend. These webservers provide the requested data via http downloads. The webservers are not excessively capable machines and meant for occasional users. If you retrieve huge amounts of data on a regular timescale, please [[public: | + | The SRM systems which the LTA sites operate are integrated in the Grid. To work with them directly, you need a Grid certificate. To allow users without a Grid certificate to download LTA data, we operate webservers as a frontend to the SRM backend. These webservers provide the requested data via http downloads. The webservers are not excessively capable machines and meant for occasional users. If you retrieve huge amounts of data on a regular timescale, please [[:public: |
- | You may want to read this FAQ Answer as well to make a decision: [[lta_faq# | + | You may want to read this FAQ Answer as well to make a decision: [[:public:lta_faq# |
- | + | ||
- | For user instructions, | + | |
+ | For user instructions, | ||
=== My downloads are too slow. What can I do? === | === My downloads are too slow. What can I do? === | ||
- | First of all, you have to check how slow your download really is. If wget shows an estimated time of arrival of several hours, this does not necessarily mean that the download is ' | + | First of all, you have to check how slow your download really is. If wget shows an estimated time of arrival of several hours, this does not necessarily mean that the download is ' |
- | In case you can rule out your network connection as the bottleneck: there are different ways to download your data and not all provide the same performance. By our experience, this is the order of performance: | + | |
- | * [[public: | + | * [[:public: |
- | * [[public: | + | * [[:public: |
- | * [[public: | + | * [[:public: |
- | You may also want to read this FAQ Answer for further explanation: | + | You may also want to read this FAQ Answer for further explanation: |
- | === I want to contact Science Operations | + | === I want to contact Science |
+ | |||
+ | You are welcome to contact Science Data Centre Operations in case of problems that you could not solve yourself. However, we kindly ask you to include all important information in your inquiry, so that we can quickly help you with your problem without too much back and forth: | ||
- | You are welcome to contact Science Operations and Support in case of problems that you could not solve yourself. However, we kindly ask you to include all important information in your inquiry, so that we can quickly help you with your problem without too much back and forth: | ||
* It is absolutely essential, that you include a clear answer to the following: | * It is absolutely essential, that you include a clear answer to the following: | ||
- | | + | |
- | - What went wrong? | + | - What went wrong? |
- | - When exactly did it fail (so that we can check the logs)? | + | - When exactly did it fail (so that we can check the logs)? |
* If you are asking about a command that failed, please copy-paste the exact command that you executed together with the full terminal output. (Some tools (like the srm commands) have a ' | * If you are asking about a command that failed, please copy-paste the exact command that you executed together with the full terminal output. (Some tools (like the srm commands) have a ' | ||
- | * If you are using some script somebody gave you, please note that we are no clairvoyants and have no idea what the script you're using actually does. We can very likely not understand what went wrong from the output of some random script. Please check the [[public: | + | * If you are using some script somebody gave you, please note that we are no clairvoyants and have no idea what the script you're using actually does. We can very likely not understand what went wrong from the output of some random script. Please check the [[:public: |
==== Troubleshoot ==== | ==== Troubleshoot ==== | ||
Line 109: | 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. | ||
- | **Note:** We get notified of these issues as well and will usually re-schedule failed requests due to server issues after the problem was solved. So please first check whether you got a 'Data ready for retrieval' | + | **Note: |
=== 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 [[lta_faq#What is all this SRM/staging stuff about?|staged]], some could not. Your mail notification should include a list of which files could not be prepared for download successfully and also include an error message to indicate the cause. If the error message says ' | + | 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 [[:public:lta_faq#what_is_all_this_srm_staging_stuff_about|staged]], some could not. Your mail notification should include a list of which files could not be prepared for download successfully and also include an error message to indicate the cause. If the error message says ' |
- | Other messages should be self-explanatory, | + | |
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. | ||
- | **Note:** We get notified of these issues as well and will usually re-schedule failed requests due to server issues after the problem was solved. So please first check whether you got a 'Data ready for retrieval' | + | **Note: |
=== 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: | ||
=== 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 156: | Line 145: | ||
This usually means the SRM server system is overloaded and you should try again in a few hours. | This usually means the SRM server system is overloaded and you should try again in a few hours. | ||
+ | === 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, | + | |
- | If there is nothing going on, there is probably something wrong with the download service. Please try again a bit later and submit a support request to the [[https:// | + | |
=== Http downloads randomly fail with "503 Service Temporarily Unavailable" | === Http downloads randomly fail with "503 Service Temporarily Unavailable" | ||
Line 167: | Line 153: | ||
This can indicate too many users downloading at the same time. Please try again a bit later. There is also a limit of simultaneous downloads you are allowed to start yourself. Please limit yourself to four simultaneous downloads, the overall download rate will not improve with a larger number of connections. | This can indicate too many users downloading at the same time. Please try again a bit later. There is also a limit of simultaneous downloads you are allowed to start yourself. Please limit yourself to four simultaneous downloads, the overall download rate will not improve with a larger number of connections. | ||
- | === When selecting a project it fails with "401 - No permission | + | === When selecting a project it fails with "401 - No permission |
This happens when you first tried to select a project when you were not logged in. Please first select another tab, e.g. search, then try to select your project again. | This happens when you first tried to select a project when you were not logged in. Please first select another tab, e.g. search, then try to select your project again. | ||
=== SRM commands fail with error containing "Java heap space" === | === SRM commands fail with error containing "Java heap space" === | ||
- | The SRM tools ignore the system' | + | The SRM tools ignore the system' |
=== SRM commands fail with error '426 Connection refused' | === SRM commands fail with error '426 Connection refused' | ||
Line 180: | Line 167: | ||
=== SRM commands fail with error 'srm client error: org.globus.gsi.CredentialException: | === SRM commands fail with error 'srm client error: org.globus.gsi.CredentialException: | ||
- | Ensure you have run ' | + | Ensure you have run ' |
- | In case the error persists: The SRM tools apparently do not always use the default proxy file location $HOME/ | + | |
* Either set the X509_USER_PROXY environment variable to your .proxy file, e.g. | * Either set the X509_USER_PROXY environment variable to your .proxy file, e.g. | ||
+ | < | ||
- | | + | export X509_USER_PROXY=$HOME/ |
+ | |||
+ | </ | ||
* or pass -x509_user_proxy=< | * or pass -x509_user_proxy=< | ||
- | | + | < |
+ | srmcp -x509_user_proxy=$HOME/ | ||
+ | |||
+ | </code> | ||
=== SRM/Grid commands fail with error 'AC validation failed!' | === SRM/Grid commands fail with error 'AC validation failed!' | ||
- | This indicates an issue with creating a secure connection to the server. There is either an issue with your personal certificate/ | + | This indicates an issue with creating a secure connection to the server. There is either an issue with your personal certificate/ |
- | * Have you registered at the Lofar VO? You can do that at [[https:// | + | * Have you registered at the Lofar VO? You can do that at [[https:// |
- | * Make sure your set of server certificates is up to date (see [[public: | + | * Make sure your set of server certificates is up to date (see [[:public: |
* There also is a known issue with OpenJDK 7, which seems not to be capable of dealing with the certificates. Make sure to run Java provided by Oracle. | * There also is a known issue with OpenJDK 7, which seems not to be capable of dealing with the certificates. Make sure to run Java provided by Oracle. | ||
* Maybe your private key uses an unsupported algorithm. You might want to try converting it with a command like this: ' | * Maybe your private key uses an unsupported algorithm. You might want to try converting it with a command like this: ' | ||
Line 201: | 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 ' |
+ |