Re: [IDV #RJZ-602723]: error with grib file on RAMADDA

Note that accessing a file for the first time will take quite a bit of 
time, as the index file has to be created (the entire ~50 GB file has to 
read through to create the index). The 2012-01 and 2013-03 files have 
been indexed, so they should be speedy now.

Sean


On 3/9/14, 4:38 AM, Jeff McWhirter wrote:
> The TDS and RAMADDA are in the same JVM so there may be some shared
> global state.
>
> Is the path "/opt/tds-live/.unidata/cache" being set in the TDS config
> or is that the default GRIB index path and it doesn't exist.
>
> As I said - RAMADDA does not set any GRIB config in its
> threddsConfig.xml. What needs to be set in the config?
>
> -Jeff
>
>
>
> On Sat, Mar 8, 2014 at 7:41 PM, Sean Arms <address@hidden
> <mailto:address@hidden>> wrote:
>
>     No sure what's going on here. The TDS will only index files that it
>     has cataloged, and the ECMWF files are not cataloged.
>
>     TDS and RAMADDA are running in different tomcat installs.
>     /opt/tds-live is the apache tomcat directory for TDS; RAMADDA is in
>     /opt/repos. I cannot think of any reason as to why an index file
>     would be in the .unidata folder.
>
>     Brian, are you by any chance trying to run the IDV on the machine to
>     generate images on RAMADDA? Is that something Tom setup for you?
>
>     Sean
>
>
>     On 3/8/14, 12:29 PM, Jeff McWhirter wrote:
>
>         There might be some global setting the TDS uses
>
>         On Saturday, March 8, 2014, Brian Mapes <address@hidden
>         <mailto:address@hidden>
>         <mailto:address@hidden
>         <mailto:address@hidden>__>> wrote:
>
>              Thanks Jeff.
>
>              I think Sean set up our TDS, Sean does this ring any bells?
>              I didn't realize RAMADDA drew on that somehow.
>
>              Brian
>
>
>
>
>              On Mar 8, 2014, at 6:34 AM, Jeff McWhirter
>         <address@hidden <mailto:address@hidden>
>              <javascript:_e(%7B%7D,'cvml','address@hidden
>         <mailto:address@hidden>');>> wrote:
>
>
>                  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
>             
> <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
>
>                  -Jeff
>
>
>
>              Brian Mapes
>         address@hidden <mailto:address@hidden>
>              <javascript:_e(%7B%7D,'cvml','address@hidden
>         <mailto:address@hidden>');>