20040818: 20040818: Gempak decoder crashing problem

Tom,

The "message: table grib3.tbl" indicates the the modeling center
that the grid is being labeled is not in the  $GEMTBL/grid/cntrgrib1.tbl
file. 

I have scanned through the NOAAPORT ingest logs, and see that there are
a small number of proucts ^O[LMN]NC88 KWNB (Wave direction, height, period) that
are identifying themselves as center 161. For the time being, you might want to
duplicate the NCEP entry for #7 to 161 so that the ncepgrib3.tbl is located.


Steve Chiswell
Unidata User SUpport


>From: Tom McDermott <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200408181808.i7II8SaW025880

>
>On Wed, 18 Aug 2004, Unidata Support wrote:
>
>> I'll see if I can create a duplicate of your problem for the 5.7.3
>> release I'm working on.
>>
>> Steve Chiswell
>> Unidata User SUpport
>
>Steve,
>
>One other thing that I'm seeing now and only in the 'dcgrib2_ocean.log'
>are these messages:
>
>[3639] 040818/1124 [NA -1]  The table grib3.tbl cannot be opened.
>...
>
>[3640] 040818/1124 [NA -1]  The table grib3.tbl cannot be opened.
>
>BTW, even though the entries for children 3639 and 3640 in the log are not
>intermingled, it looks like they may have been running at the same time
>because of the timestamps and also this message from 'ldmd.log':
>
>Aug 18 15:25:00 vortex pqact[26768]: child 3640 terminated by signal 11
>Aug 18 15:25:00 vortex pqact[26768]: child 3639 terminated by signal 11
>
>So this may be the multiple file writers problem.
>
>Tom
>-----------------------------------------------------------------------------
>Tom McDermott                          Email: address@hidden
>Systems Administrator                  Phone: (585) 395-5718
>Earth Sciences Dept.                   Fax: (585) 395-2416
>SUNY College at Brockport
>
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically 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.