NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
>From Roy: Okay I may have made a little headway on featureCollections in thredds4.5, though I think it is due to some random changes rather than any understanding. Since on the real server the featureCollection will be changing, I am trying to see if I can make it dynamic. So I have installed the TDM, and now don’t understand what it is doing. I have modified the /tomcat-user.xml just as in the instructions, to be: > <tomcat-users> > <role ... /> > <role rolename="tdsTrigger"/> > <user ... /> > <user username="tdm" password="secret" roles="tdsTrigger"/> > </tomcat-users> and I have created a shell script with the line: > /usr/local/jre1.7.0_25/bin/java -Xmx800m > -Dtds.content.root.path=/usr/local/tomcat/content -jar tdm-4.5.jar -tds > "http:/localhost:8080" -showOnly Now according to the web page, the -showOnly does: > -showOnly: (optional) if this is present, just show the featureCollections > that will be indexed and exit. When I run it I get: > Server added http://localhost:8080/ > contentDir=/usr/local/tomcat/content > catalog=/usr/local/tomcat/content/thredds/catalog.xml > Server added http:/localhost:8080 > > Enter password for tds trigger: secret > > Password = 'secret' OK (Y/N)?y > Tdm startup at Thu Oct 30 17:43:35 PDT 2014 > Feature Collection names: > FNMOC NAVGEM 0.5-degree 6-hourly Pressure > > Triggers: > thredds/admin/collection/trigger?trigger=never&collection=FNMOC NAVGEM > 0.5-degree 6-hourly Pressure and then it hangs there and doesn’t exit - the test file set is only like 10 files and has already been scanned. Should not TDM have exited? Even more, can I exit it and then will it be called, or do I just leave it running or what. Thanks for any help. -Roy Hi Roy: 1) not sure if -showOnly works as advertised, i will check. 2) what does your <tdm> emelent say about that dataset? if it has a rescan, it will never exit, so you just kill it. 3) best to give your colelction a name with no blanks in it, eg: <collection name="FNMOC-NAVGEM" spec="/u00/FNMOC/NAVGEM/pressure/**/US058GMET-GR1mdl.0018_0056_00000F0..#yyyyMMddHH#_0102_000000-000000pres$" olderThan="5 min"/> 3) check your logs files, in the tdm working directory (by convention, "content/tdm") <collection_name>.log. It should say whats going on. Send it along if not clear what its doing. John On Sun, Nov 2, 2014 at 4:25 PM, John Caron <caron@xxxxxxxx> wrote: > > - *To*: thredds@xxxxxxxxxxxxxxxx <thredds@DOMAIN.HIDDEN> > - *Subject*: [thredds] thredds4.5 and Feature Collections > - *From*: Roy Mendelssohn - NOAA Federal <roy.mendelssohn@xxxxxxxx > <roy.mendelssohn@DOMAIN.HIDDEN>> > - *Date*: Thu, 30 Oct 2014 16:17:36 -0700 > > Hi All: > > Nothing like FeatureCollections to help one feel old and slow - and boy do I > feel old and slow. I have been putting off upgrading to thredds 4.5 just > because of the changes (I had enough trouble getting featureCollections > working the first time around). > > I have a working thredds4.3 feature collection that is failing with thredds4.5 > on my test server on my laptop. So, though what is wrong is probably obvious, > it hasn’t been obvious to me, nor to my bum knee. So here goes. > > 1. Do I understand correctly that a featureCollection will only work in > thredds4.5 with TDM running, or is that only if the dataset is being updated? > > -> only if the dataset is changing. > > 2. If I look at: > http://www.unidata.ucar.edu/software/thredds/current/tds/UpgradingTo4.5.html > > I see: > > <update startup="nocheck" trigger="allow"/> > <tdm startup="true" rescan="0 8,23,38,53 * * * ? *" trigger="allow"/> > replaced with: > > <update startup="never" trigger="allow"/> > <tdm rewrite="test" rescan="0 8,23,38,53 * * * ? *" trigger="allow"/> > I had update on startup before (more below) does it need to be “never” always > (or basically I am unclear in what sense one replaces the other). I didn’t > have an update command, just > > <tdm startup="true" rescan="0 0/15 * * * ? *" trigger="allow"/> > > > -> > > 1) > > <tdm startup ..> > > is now > > <tdm rewrite ..> > > although it still accepts "startup". just thought it was clearer. > > 2) > > <update startup="nocheck" ... > > means, on TDS startup, use indices if they are already there (dont check if > they are up to date), and create them if not > > <update startup="never" ... > > means, on TDS startup, indices must be already there, never create them. > > I have looked at the logs and it is unclear to me what is causing the > error. Below I have put what I hope are the relevant parts of the the > catalogs. If someone can point out the problem, I would be most grateful. > > -Roy > > thredds4.3: > > <featureCollection name="FNMOC NAVGEM 0.5-degree 6-hourly Pressure" > featureType="GRIB" harvest="true" path="FNMOC/navgem/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/NAVGEM/pressure/**/US058GMET-GR1mdl.0018_0056_00000F0..#yyyyMMddHH#_0102_000000-000000pres$" > olderThan="5 min"/> > <tdm startup="true" rescan="0 0/15 * * * ? *" trigger="allow"/> > <gribConfig datasetTypes="Best LatestFile" /> > </featureCollection> > > thredds4.5: > > <featureCollection name="FNMOC NAVGEM 0.5-degree 6-hourly Pressure" > featureType="GRIB1" harvest="true" path="FNMOC/navgem/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/NAVGEM/pressure/**/US058GMET-GR1mdl.0018_0056_00000F0..#yyyyMMddHH#_0102_000000-000000pres$" > olderThan="5 min"/> > <update startup="never" trigger="allow"/> > <tdm rewrite="test" rescan="0 0/15 * * * ? *" trigger="allow"/> > <gribConfig datasetTypes="TwoD Best LatestFile" /> > </featureCollection> > > > > -> dont see anything obvious, whats the error message? what does > catalogInit.log look like? > >
thredds archives: