Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transport endpoint is not connected, Bus error #1125

Open
Narayana-Rao opened this issue Oct 21, 2024 · 3 comments
Open

Transport endpoint is not connected, Bus error #1125

Narayana-Rao opened this issue Oct 21, 2024 · 3 comments
Assignees

Comments

@Narayana-Rao
Copy link

Unable to download or process Sentinel-1 SLC .zip files (~ 4GB)

If I try to download/copy any Sentinel-1 SLC .zip file to the workspace, the processing is breaking and reconnecting the workspace buckets.


> wget https://datapool.asf.alaska.edu/SLC/SA/S1A_IW_SLC__1SDV_20190126T002213_20190126T002240_025641_02D8E5_6F5E.zip

Saving to: ‘S1A_IW_SLC__1SDV_20190126T002213_20190126T002240_025641_02D8E5_6F5E.zip’

S1A_IW_SLC__1SDV_20190126T002213_20190126T002240_0256  26%[===============================>                                                                                          ]   1.11G  38.7MB/s    in 34s     


Cannot write to ‘S1A_IW_SLC__1SDV_20190126T002213_20190126T002240_025641_02D8E5_6F5E.zip’ (Transport endpoint is not connected).

To Reproduce
Steps to reproduce the behavior:

  1. Try downloading any Sentinel-1 SLC granule into workspace buckets "wget https://datapool.asf.alaska.edu/SLC/SA/S1A_IW_SLC__1SDV_20190126T002213_20190126T002240_025641_02D8E5_6F5E.zip"

Workaround to download
We can download into the /projects directory but cannot copy/move the files for further processing.

Bus error while processing
While trying to process them directly from /projects directory using ISCE2 , I got Bus error as shown below
/projects/../projects/my-public-bucket/iscetest/s1stack/vv/run_files/run_01_unpack_topo_reference: line 1: 297 Bus error SentinelWrapper.py -c /projects/my-public-bucket/iscetest/s1stack/vv/configs/config_reference

@wildintellect wildintellect self-assigned this Oct 21, 2024
@wildintellect
Copy link
Collaborator

wildintellect commented Oct 21, 2024

@Narayana-Rao

  1. what directory in your ADE are you when you execute this command?
  2. what command in ISCE2 do you run on the s1 file to test processing?

@wildintellect
Copy link
Collaborator

Transport_endpoint sounds like you're trying to download directly to a path with the name bucket in it. This is an S3 location, downloading very large files directly to S3 with wget/maap-py is not advised. Best practices would be to download to a local folder first.

Using this S1 example, I tested copying from EarthDataCloud.

Modified search to get the granule of interest:

results = maap.searchGranule(cmr_host="cmr.earthdata.nasa.gov",
                                short_name='SENTINEL-1A_SLC',
                                producer_granule_id="S1A_IW_SLC__1SDV_20190126T002213_20190126T002240_025641_02D8E5_6F5E",
                                limit=10,
                                )

In an ISCE2 workspace you might also need to set the host on maap import (bug the current image points to dit)

maap = MAAP(maap_host="api.maap-project.org")

TODO: Test ISCE2 process, need more info from @Narayana-Rao on how to do that.

@Narayana-Rao
Copy link
Author

Thanks @wildintellect !

maap.downloadGranule() is working fine to download the granules now.

However, the bus error still persist while processing. As suggested, i have avoided using buckets either in input or output paths, by directly reading and writing to projects folder.

  1. I am using projects folder to store input data and processed data
  2. SentinelWrapper.py command from topsStack workflow

Here are the details of the error.

(isce2) root@workspace3xf7prc53yo79zll:~# ./run_files/run_01_unpack_topo_reference Completed Parsing the Configuration file Functions to be executed: ['Function-1', 'Function-2'] Running: Sentinel1_TOPS ['--dirname', '/projects/S1B_IW_SLC__1SDV_20180423T161524_20180423T161551_010613_0135DD_33F0.zip', '--swaths', '1 2 3', '--orbit', '/projects/orbits/20180423/S1B_OPER_AUX_POEORB_OPOD_20210312T225246_V20180422T225942_20180424T005942.EOF', '--outdir', '/projects/reference', '--auxdir', '/projects/aux', '--bbox', '19.4000 19.6000 -155.5000 -155.3000', '--pol', 'vv'] Using default ISCE Path: /opt/conda/envs/isce2/lib/python3.10/site-packages/isce Input XML files: ['/vsizip//projects/S1B_IW_SLC__1SDV_20180423T161524_20180423T161551_010613_0135DD_33F0.zip/S1B_IW_SLC__1SDV_20180423T161524_20180423T161551_010613_0135DD_33F0.SAFE/annotation/s1b-iw1-slc-vv-20180423t161526-20180423t161551-010613-0135dd-004.xml'] Input TIFF files: ['/vsizip//projects/S1B_IW_SLC__1SDV_20180423T161524_20180423T161551_010613_0135DD_33F0.zip/S1B_IW_SLC__1SDV_20180423T161524_20180423T161551_010613_0135DD_33F0.SAFE/measurement/s1b-iw1-slc-vv-20180423t161526-20180423t161551-010613-0135dd-004.tiff'] Manifest files: ['/vsizip//projects/S1B_IW_SLC__1SDV_20180423T161524_20180423T161551_010613_0135DD_33F0.zip/S1B_IW_SLC__1SDV_20180423T161524_20180423T161551_010613_0135DD_33F0.SAFE/manifest.safe'] MANS: /projects/S1B_IW_SLC__1SDV_20180423T161524_20180423T161551_010613_0135DD_33F0.zip S1B_IW_SLC__1SDV_20180423T161524_20180423T161551_010613_0135DD_33F0.SAFE/manifest.safe Setting IPF version to : 002.90 Extracting orbit from Orbit File: /projects/orbits/20180423/S1B_OPER_AUX_POEORB_OPOD_20210312T225246_V20180422T225942_20180424T005942.EOF Number of Bursts before cropping: 9 Number of Bursts after cropping: 3 /opt/conda/envs/isce2/lib/python3.10/site-packages/osgeo/gdal.py:287: FutureWarning: Neither gdal.UseExceptions() nor gdal.DontUseExceptions() has been explicitly called. In GDAL 4.0, exceptions will be enabled by default. warnings.warn( ./run_files/run_01_unpack_topo_reference: line 1: 1653 Bus error SentinelWrapper.py -c /projects/configs/config_reference

@Narayana-Rao Narayana-Rao changed the title Transport endpoint is not connected Transport endpoint is not connected, Bus error Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants