Differences

This shows you the differences between two versions of the page.

--- public:lta_faq [2023-02-17 10:48] – Hanno Holties
+++ public:lta_faq [2025-01-23 06:48] (current) – [Troubleshoot] Sander ter Veen
@@ Line 22: / Line 22: @@
   * **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**: [[: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:** [[:https:::www.astron.nl:lofarwiki:doku.php?id=public:lta_faq#i_get_a_time-out_when_searching_around_a_declination_of_zero|I get a time-out when searching around a declination of zero]]
   * **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**: [[:public:lta_faq#my_data_files_are_corrupted|My data files are corrupted / I cannot unpack my data]]
@@ Line 32: / Line 33: @@
   * **Q**: [[:public:lta_faq#srm_grid_commands_fail_with_error_ac_validation_failed_or_no_trusted_path_can_be_constructed|SRM/Grid commands fail with error 'AC validation failed!' or 'No trusted path can be constructed']]
   * **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 =====
@@ Line 117: / Line 120: @@
 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' notification for the same request id after the error notification. If you did, the problem was already resolved.
+**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' notification for the same request id after the error notification. If you did, the problem was already resolved.
 === I got an email that says my staging request was only partially successful! What's going on? ===
@@ Line 125: / Line 127: @@
 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' notification for the same request id after the error notification. If you did, the problem was already resolved.
+**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' notification for the same request id after the error notification. If you did, the problem was already resolved.
 === Oops! I made a mistake! How can I stop a request? ===
 Unfortunately, this is currently not possible for you as a user. Stay calm and ask [[https://support.astron.nl/rohelpdesk|ASTRON helpdesk]] to stop the request for you.
+=== I get a time-out when searching around a declination of zero ===
+The system has trouble finding data around a declination of zero. This can take a long time (minutes). If it still not succeeds you will get an nginx time-out error. To limit the search so it will still succeed you can either lower the search radius or limit the **Observing date** start and stop time. With that we have been able to find date with a radius of 1.2 in a two-year window for example. LOFAR observations start around 2011.
 === 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://support.astron.nl/rohelpdesk|ASTRON helpdesk]] or retry after a few hours.
-**Important:**  If you use wget with option '-c', please note the following: wget does not check the contents of an existing file, so when restarting wget with option '-c' (continue) to retrieve the failed files, it will append the later data chunk to the existing file that contains the error message (and not the first section of you data). Make sure to delete the existing error files (should be obvious by the small file size) before calling 'wget -ci' again, to avoid corrupted data. If you already ended up with a corrupted file, you have to delete that and re-retrieve the whole file.
+**Important:** If you use wget with option '-c', please note the following: wget does not check the contents of an existing file, so when restarting wget with option '-c' (continue) to retrieve the failed files, it will append the later data chunk to the existing file that contains the error message (and not the first section of you data). Make sure to delete the existing error files (should be obvious by the small file size) before calling 'wget -ci' again, to avoid corrupted data. If you already ended up with a corrupted file, you have to delete that and re-retrieve the whole file.
 === My data files are corrupted ===
@@ Line 169: / Line 172: @@
 Ensure you have run 'voms-proxy-init'' to generate an up-to-date proxy file. In case the error persists: The SRM tools apparently do not always use the default proxy file location $HOME/.proxy or you used a non-standard proxy location in ''voms-proxy-init''.
-  * 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.
 <code>