[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[THREDDS #UDT-134933]: TDS AWS S3 object services problems

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [THREDDS #UDT-134933]: TDS AWS S3 object services problems
  • Date: Tue, 22 Mar 2022 11:22:19 -0600
Greetings!

Thanks for pointing out this HTTPServer S3 bug. We are currently working on a 
fix and will let you know when it's merged.

The experimental CdmrFeature was removed. What were you using it for? I believe 
a lot of the functionality from that service is covered by other services, like 
ncss.

Best,
Tara

================================================================


I am doing some TDS (version 5.3 docker image) S3 tests, and found that
HTTPServer service is not working on a single S3 object/file, and
CdmrFeature is not working on any dataset. Both gave 404 Error:

HTTP Status 404 – Not Found
------------------------------

*Type* Status Report

*Description* The origin server did not find a current representation for
the target resource or is not willing to disclose that one exists.

Here is part of my Tomcat access_log:

127.0.0.1 - - [08/Mar/2022:18:40:48 +0000] "GET
/thredds/dodsC/s3-cw/viirs/npp/science/L3/global/chlora
/daily/WW00/V2022003_D1_WW00_chlora.nc.html HTTP/1.1" 200 26317
127.0.0.1 - - [08/Mar/2022:18:40:49 +0000] "GET /thredds/catalog.html
HTTP/1.1" 302 -
127.0.0.1 - - [08/Mar/2022:18:40:59 +0000] "GET /thredds/catalog.html
HTTP/1.1" 302 -
127.0.0.1 - - [08/Mar/2022:18:41:09 +0000] "GET /thredds/catalog.html
HTTP/1.1" 302 -
127.0.0.1 - - [08/Mar/2022:18:41:14 +0000] "GET
*/thredds/fileServer/s3-cw/viirs/npp/science/L3/global/chlora/daily/WW00/V2022003_D1_WW00_chlora.nc*
HTTP/1.1" 404 675
127.0.0.1 - - [08/Mar/2022:18:41:19 +0000] "GET
*/thredds/cdmrfeature/grid/s3-cw/viirs/npp/science/L3/global/chlora/daily/WW00/V2022003_D1_WW00_chlora.nc*
HTTP/1.1" 404 675

And here is part of my catalog file:

  <service name="all" base="" serviceType="compound">    <service
name="odap" serviceType="OpenDAP" base="/thredds/dodsC/"/>
*<service name="fileServer" serviceType="HTTPServer"
base="/thredds/fileServer/" />*    <service name="wcs"
serviceType="WCS" base="/thredds/wcs/"/>    <service name="wms"
serviceType="WMS" base="/thredds/wms/"/>    <service name="ncssGrid"
serviceType="NetcdfSubset" base="/thredds/ncss/grid/"/>    <service
name="cdmremote" serviceType="CdmRemote" base="/thredds/cdmremote/"/>
  *<service name="cdmrFeature" serviceType="CdmrFeature"
base="/thredds/cdmrfeature/grid/"/>*    <service name="iso"
serviceType="ISO" base="/thredds/iso/"/>    <service name="ncml"
serviceType="NCML" base="/thredds/ncml/"/>    <service name="uddc"
serviceType="UDDC" base="/thredds/uddc/"/>  </service>    <datasetRoot
path="s3-cw" location="cdms3:ncis-coastwatch" />  <dataset name="Test
Single VIIRS 4km global S3 (Aug 7th, 2020) "
ID="V2022003_D1_WW00_chlora"
urlPath="s3-cw/viirs/npp/science/L3/global/chlora/daily/WW00/V2020220_D1_WW00_chlora.nc"
   dataType="Grid"    serviceName="all"/>

Any advice on how to fix the problems?

Thanks,








Ticket Details
===================
Ticket ID: UDT-134933
Department: Support THREDDS
Priority: Urgent
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.