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

[THREDDS #MRV-895858]: $%#^@!%^#



Hi Roy,

Earlier in our conversation, I was suspecting that our GRIB indexing code was 
tripping up on something in your GRIB files. But since removing and re-adding 
one set of GRIB files fixes things, that guess seems much less likely.

I think the best way forward is for us to try to reproduce the problem here and 
see what we can figure out. Are your data files available for download from 
your server? Or can you send us a few files from each of the monthly 
collections you are using?

Thanks,

Ethan

Roy Mendelssohn wrote:
> Hi Ethan:
> 
> Something has to be messed up somewhere.  Since I was
> worried about your caching, I installed a clean TDS 4.3.15
> 
> I did the following:
> 
> 1) I had one directory with all the grib  files for two months in it, for 
> 201212 and 201301 (a file for every six hours).  I started thredds, and on 
> trying to access the html page it gave me the error
> 
> > Error {
> >    code = 500;
> >    message = "Variable name (pres_msl) must be unique within Group ";
> > };
> >
> 
> 2).  I stopped TDS.  Removed the 2012 files from the directory, restarted 
> TDS, worked fine.
> 
> 3).  Stopped TDS, put back in the 2012 files that I had removed, restarted 
> TDS, worked fine  (this was now at the same file configuration as step 1 
> where it failed).
> 
> 4).  I have a second directory where I have the files in subdirectories by 
> month.  I have 2 months 201212, 201301. Stopped TDS, adding these to 
> catalog.xml as a new dataset with new name, path etc , restarted TDS, when 
> trying to access the html page for these I got the error above.
> 
> 5).  Stopped TDS, removed the directory 201212, restarted TDS and now 
> everything worked.
> 
> 6) Stopped TDS, added back in the 201212 directory, restarted TDS and now 
> everything worked, even though this is exactly as I had it in step 4 where it 
> failed.  Note between 4 and 6 the catalog.xml file did not change.
> 
> The catalog.xml looks like:
> 
> 
> >      <featureCollection name="FNMOC 6-hour Pressure" featureType="GRIB" 
> > harvest="true" path="FNMOC/pressure/6hr">
> >        <dataFormat>GRIB-1</dataFormat>
> >        <metadata inherited="true">
> >           <serviceName>all</serviceName>
> >           <documentation type="summary">
> >               FNMOC 1-degree pressure fields from the NOGAPS model
> >            </documentation>
> >        </metadata>
> >
> >        <collection spec="/u00/FNMOC/A018000GRB#yyyyMMddHH#*"
> >                    olderThan="5 min"/>
> >        <tdm startup="false" rescan="0 0/15 * * * ? *" trigger="allow"/>
> >        <gribConfig datasetTypes="Best LatestFile" />
> >      </featureCollection>
> >
> >      <featureCollection name="FNMOC Pressure Months" featureType="GRIB" 
> > harvest="true" path="FNMOC/pressure/6hr2">
> >        <dataFormat>GRIB-1</dataFormat>
> >        <metadata inherited="true">
> >           <serviceName>all</serviceName>
> >           <documentation type="summary">
> >               FNMOC 1-degree pressure fields from the NOGAPS model
> >            </documentation>
> >        </metadata>
> >
> >        <collection spec="/u00/FNMOC2/**/A018000GRB#yyyyMMddHH#*"
> >                    olderThan="5 min"/>
> >        <tdm startup="true" rescan="0 0/15 * * * ? *" trigger="allow"/>
> >        <gribConfig datasetTypes="Best LatestFile" />
> >      </featureCollection>
> >
> 
> Either I have something very stupid in my catalog.xml that I ma not seeing, 
> or there are some problems, because removing data and then adding it back in 
> should not make such a difference to the server.
> 
> Thanks,
> 
> -Roy
> 
> Roy Mendelssohn
> Supervisory Operations Research Analyst
> NOAA/NMFS
> Environmental Research Division
> Southwest Fisheries Science Center


Ticket Details
===================
Ticket ID: MRV-895858
Department: Support THREDDS
Priority: Normal
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.