There might be some global setting the TDS uses
On Saturday, March 8, 2014, Brian Mapes <address@hidden <mailto:address@hidden>> wrote:
I think Sean set up our TDS, Sean does this ring any bells? I didn't realize RAMADDA drew on that somehow.
Yuan - If you looked at the actual error you would see that it is a server side error - not an IDV error. If you go to the opendap link page: http://weather.rsmas.miami.edu/repository/opendap/synth:601aa404-ac59-4abb-8c4f-11c08474a214:LzIwMTEtMTAuZ3Ji/entry.das
This is the error:
/opt/tds-live/.unidata/cache/data2-brian-DYNAMO-ECMWF-analysis-2011-10.grb.gbx9 (No such file or directory)
The question is is why is RAMADDA pointing to /opt/tds-live/... as the place to write GRIB caches to? In RAMADDA we write out the threddsConfig.xml to define the subset service directory but we don't do anything with the GRIB settings: <!-- Writing GRIB indexes. <GribIndexing> <setExtendIndex>false</setExtendIndex> <alwaysUseCache>false</alwaysUseCache> </GribIndexing> -->
I am assume there is also a TDS running under the same TOMCAT? I would guess that it has set some configuration options.
Yuan - this should be looked at by the TDS folks
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.