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

[THREDDS #EFD-388660]: File Access Problems With TDS 4.18?



There we go, that unpacked as expected.

On 9/25/2013 3:28 PM, Kevin Manross wrote:
> New Client Reply: File Access Problems With TDS 4.18?
>
>
> Fascinating and frustrating.
>
> How about this one (attached)
>
> -kevin.
>
> On 9/25/13 3:23 PM, Unidata THREDDS Support wrote:
>> Kevin,
>>
>> I've never seen it before, but I don't seem to be able to successfully
>> unpack the tarball you sent.  I get a bunch of:
>>
>> catalog_ds629.3.xml
>> tar: Archive value 1202617992 is out of gid_t range 0..65535
>> tar: Extended header gid=1202617992 is out of range 0..65535
>> tar: Extended header uid=666758683 is out of range 0..65535
>> tar: Ignoring unknown extended header keyword `SCHILY.dev'
>> tar: Ignoring unknown extended header keyword `SCHILY.ino'
>> tar: Ignoring unknown extended header keyword `SCHILY.nlink'
>> catalog_ds629.4.xml
>> tar: Archive value 1202617992 is out of gid_t range 0..65535
>> tar: Extended header gid=1202617992 is out of range 0..65535
>> tar: Extended header uid=666758683 is out of range 0..65535
>> tar: Ignoring unknown extended header keyword `SCHILY.dev'
>> tar: Ignoring unknown extended header keyword `SCHILY.ino'
>> tar: Ignoring unknown extended header keyword `SCHILY.nlink'
>> catalog_ds629.5.xml
>> tar: Archive value 1202617992 is out of gid_t range 0..65535
>> tar: Extended header gid=1202617992 is out of range 0..65535
>> tar: Extended header uid=666758683 is out of range 0..65535
>> tar: Ignoring unknown extended header keyword `SCHILY.dev'
>> tar: Ignoring unknown extended header keyword `SCHILY.ino'
>> tar: Ignoring unknown extended header keyword `SCHILY.nlink'
>> catalog_ds629.6.xml
>> tar: Archive value 1202617992 is out of gid_t range 0..65535
>> tar: Extended header gid=1202617992 is out of range 0..65535
>> tar: Extended header uid=666758683 is out of range 0..65535
>> tar: Ignoring unknown extended header keyword `SCHILY.dev'
>> tar: Ignoring unknown extended header keyword `SCHILY.ino'
>> tar: Ignoring unknown extended header keyword `SCHILY.nlink'
>> catalog_ds631.0.xml
>> tar: Exiting with failure status due to previous errors
>>
>> Can you try packing and sending again?  Sorry to be having trouble.
>>
>> -Lansing
>>
>> On 9/25/2013 11:13 AM, Kevin Manross wrote:
>>> New Client Reply: File Access Problems With TDS 4.18?
>>>
>>>
>>> I'm glad the error is reproducible Lansing.
>>>
>>> Attached is a tarball of my catalog files.  Please let me know if you
>>> need anything else and I'll be happy to provide it.  many thanks for the
>>> attention on this!
>>>
>>> -kevin.
>>>
>>> On 9/25/13 11:07 AM, Unidata THREDDS Support wrote:
>>>> Kevin,
>>>>
>>>> Okay, I see the 500 error coming up on variable map requests.  I didn't
>>>> check every dataset, but I'll take your word for it.  I have a bunch of
>>>> your grib1 files, so I'll try to reproduce what's happening on your
>>>> server locally in my debugger.  I would appreciate it if you would send
>>>> me your catalogs, since that makes it a little easier to recreate your
>>>> environment.  If I can't reproduce the issue, I may need to get some of
>>>> the specific files that are giving you the 500 error on variable map.
>>>>
>>>> -Lansing
>>>>
>>>> On 9/25/2013 9:16 AM, Kevin Manross wrote:
>>>>> New Client Reply: File Access Problems With TDS 4.18?
>>>>>
>>>>>
>>>>> Hmmm, that's a bit odd.  I restarted the server at 2:30 yesterday
>>>>> afternoon.  I have not seen the 503 error after that, nor this morning.
>>>>>
>>>>> I know that when hitting the files link for ds083.2, it takes a while
>>>>> since I do not currently have them partitioned.
>>>>>
>>>>> Could you try again this morning and let me know if you are still
>>>>> getting the 503 error?
>>>>>
>>>>> Thanks!
>>>>>
>>>>> -kevin.
>>>>>
>>>>> On 9/24/13 5:26 PM, Unidata THREDDS Support wrote:
>>>>>> Kevin,
>>>>>>
>>>>>> I've been hitting castle this afternoon, but I'm getting a service
>>>>>> unavailable 503 message when I hit the files.  Is this what you're
>>>>>> seeing, or something new and different?
>>>>>>
>>>>>> -Lansing
>>>>>>
>>>>>> On 9/10/2013 12:08 PM, Kevin Manross wrote:
>>>>>>> New Client Reply: File Access Problems With TDS 4.18?
>>>>>>>
>>>>>>>
>>>>>>> Hello Lansing,
>>>>>>>
>>>>>>> I finally updated my TDS yesterday to the war file you offered below.
>>>>>>> It appears to have fixed some of the issues, but not all of them.  You
>>>>>>> are welcome to check my server at
>>>>>>>
>>>>>>> http://castle.ucar.edu/thredds
>>>>>>>
>>>>>>> There you will see the following datasets.  I have added comments
>>>>>>> regarding which are GRIB/GRIB2 and which ones are now successful in
>>>>>>> allowing OPeNDAP/NCSS/Variable Map access and which are not.  Note, you
>>>>>>> will need an RDA user account to access the OPeNDAP/NCSS links, but the
>>>>>>> Variable Map links do not require a login.
>>>>>>>
>>>>>>>           Folder  RDA Datasets
>>>>>>>                  Folder  ds083.2/           GRIB1  :: suffix _00_c or 
>>>>>>> _00 ::
>>>>>>> Access fails at file level but works for aggregation
>>>>>>>                  Folder  ds093.1/           GRIB2  :: suffix .grb2  :: 
>>>>>>> Access
>>>>>>> fails at file level but works for aggregation
>>>>>>>                  Folder  ds094.1/           GRIB2  :: suffix .grb2  :: 
>>>>>>> Access
>>>>>>> fails at file level but works for aggregation
>>>>>>>                  Folder  ds277.6/           GRIB1  :: .grb  :: All is 
>>>>>>> good!
>>>>>>>                  Folder  ds285.3/           GRIB1  :: .grb  :: All is 
>>>>>>> good!
>>>>>>>                  Folder  ds316.0/           NetCDF
>>>>>>>                  Folder  ds502.0/           NetCDF
>>>>>>>                  Folder  ds629.1/           GRIB1  :: .YYYYMMDD :: 
>>>>>>> Access fails
>>>>>>> at file level but works for aggregation
>>>>>>>                  Folder  ds629.2/           GRIB1  :: .YYYYMMDD :: 
>>>>>>> Access fails
>>>>>>> at file level but works for aggregation
>>>>>>>                  Folder  ds629.3/           (Same as others in this 
>>>>>>> series, but
>>>>>>> still updating and may not be immediately available)
>>>>>>>                  Folder  ds629.5/           GRIB1  :: .YYYYMMDD :: 
>>>>>>> Access fails
>>>>>>> at file level but works for aggregation
>>>>>>>                  Folder  ds629.6/           GRIB1  :: .YYYYMMDD :: 
>>>>>>> Access fails
>>>>>>> at file level but works for aggregation
>>>>>>>                  Folder  ds631.0/           NetCDF
>>>>>>>
>>>>>>> I would be happy to send you the respective catalogs id that would be
>>>>>>> useful.
>>>>>>>
>>>>>>> For all the GRIB2 data, I have the following:
>>>>>>>
>>>>>>> <gribConfig datasetTypes="Best Files">
>>>>>>>                  <bestNamer name="Timeseries Aggregation"/>
>>>>>>>                  <pdsHash>
>>>>>>>                    <useGenType>true</useGenType>
>>>>>>>                  </pdsHash>
>>>>>>> </gribConfig>
>>>>>>>
>>>>>>> For all the GRIB1 data it is:
>>>>>>>
>>>>>>> <gribConfig datasetTypes="Best Files">
>>>>>>>                      <bestNamer name="Timeseries Aggregation"/>
>>>>>>>                      <pdsHash>
>>>>>>>                        <useTableVersion>false</useTableVersion>
>>>>>>>                      </pdsHash>
>>>>>>> </gribConfig>
>>>>>>>
>>>>>>> Please let me know if I can provide any additional info to help.
>>>>>>>
>>>>>>> -kevin.
>>>>>>>
>>>>>>>
>>>>>>> On 8/27/13 1:40 PM, Unidata THREDDS Support wrote:
>>>>>>>> Hi Kevin,
>>>>>>>>
>>>>>>>> I have a bug fix for you.  The initial stack trace that I saw was a 
>>>>>>>> red herring, and was a function of me hitting the server before 
>>>>>>>> indexing was complete on start up.  You can download the new warfile 
>>>>>>>> (a snapshot of 4.3.19) here:
>>>>>>>>
>>>>>>>> https://docs.google.com/file/d/0B7jP7ooGP2ZzYng3R3NUVlVsVkE/edit?usp=sharing
>>>>>>>>
>>>>>>>> Thank you for reporting this bug!
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>>           Lansing Madry
>>>>>>>>           Unidata
>>>>>>>>           Boulder, Colorado
>>>>>>>>
>>>>>>>> Ticket Details
>>>>>>>> ===================
>>>>>>>> Ticket ID: EFD-388660
>>>>>>>> Department: Support THREDDS
>>>>>>>> Priority: Low
>>>>>>>> Status: Open
>>>>>>>>
>>>>>> Ticket Details
>>>>>> ===================
>>>>>> Ticket ID: EFD-388660
>>>>>> Department: Support THREDDS
>>>>>> Priority: Low
>>>>>> Status: Open
>>>>>>
>>>> Ticket Details
>>>> ===================
>>>> Ticket ID: EFD-388660
>>>> Department: Support THREDDS
>>>> Priority: Low
>>>> Status: Open
>>>>
>>
>> Ticket Details
>> ===================
>> Ticket ID: EFD-388660
>> Department: Support THREDDS
>> Priority: Low
>> Status: Open
>>



Ticket Details
===================
Ticket ID: EFD-388660
Department: Support THREDDS
Priority: Low
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.