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

Re: Thredds Aggregations: RTOFS Grib data



Hi Tim:

Shutdown, remove all the *.ncx, *.ncx2 and *.gbx9 files for the problem files, then start up again.

John

On Mon, Sep 22, 2014 at 8:24 AM, Timothy Lewis - NOAA Affiliate <address@hidden> wrote:
John, 

Thank you for your help.  Upon further inspection, the new aggregation with Polar Stereographic Projection has only one timestamp - Sep 17, 2014 at 0300.  I've removed all files with this date and restarted TDS, but the split aggregation continues to appear.  I understand the TDS write index files for GRIB aggregations.  Might the server be reading stale index files that still have references to files with this date/projection?  If so, where are they written and how do we clear/renew these index files?

Thank you,

Tim Lewis

On Fri, Sep 19, 2014 at 5:08 PM, John Caron <address@hidden> wrote:
Hi Timothy:

It looks like some GRIB files using Polar Stereographic Projection has gotten into your collection of GRIB that uses Curvilinear Orthographic. THREDDS will automatically create seperate groups for different projections.

 If it just happened, then its likely in data that youve recently added to the collection. You can open up files in ToolsUI to see whats in there. You'll need to track down the offending files and remove them.

John

On Fri, Sep 19, 2014 at 3:24 PM, Timothy Lewis - NOAA Affiliate <address@hidden> wrote:
John,

I maintain the Thredds server for OceanNOMADS at NCDDC.  We are having an issue with our aggregation of RTOFS surface Grib data.  The server is configured to serve one aggregation, and this has worked fine before.  Now, however, the server is producing two aggregations, each with its own name based on its projection.  You can see this here:


I have not configured the aggregation to split into two, and I do not understand where the names for these are coming from.  The aggregation works as expected on staging, and the configurations are the same for both.  Both servers have been restarted numerous times since this issue began, and they are both looking at the same data(minus about one week for staging).  I have attached the configuration files for staging and production as well as a screenshot of the staging Thredds server.  Both are at version 4.3.18.  

Can you please provide some insight as to why this aggregation is suddenly giving these unexpected results?  Thank you, and have a good weekend.

Sincerely,

Tim Lewis
--
Tim Lewis, Associate Software Engineer
General Dynamics Information Technology
NOAA Coastal Data Development Center
1021 Balch Boulevard, Suite 1003
Stennis Space Center, Mississippi 39529 USA





--
Tim Lewis, Associate Software Engineer
General Dynamics Information Technology
NOAA Coastal Data Development Center
1021 Balch Boulevard, Suite 1003
Stennis Space Center, Mississippi 39529 USA