Hi Carissa, re: > Boi needs a little more information to track down this product. Out of > your logs are you able to at all resolve the grib2 filename? Yes, this is very easy since there have been a lot of these products coming in since yesterday morning. Here is one example 'notifyme' line that shows 'gribinsert's failure to create a full LDM/IDD Product ID: Aug 03 19:01:14 notifyme[9864] INFO: 18522 20120803190106.526 CONDUIT 270 data/nccf/com/rap/prod/rap.20120803/rap.t18z.awp252pgrbf14.grib2 !grib2/ncep/RUC2/#000/FHRS//LVL! 000270 The name of the file piece of this log entry is: data/nccf/com/rap/prod/rap.20120803/rap.t18z.awp236pgrbf13.grib2 re: > Can you even narrow down which model it is? Anything at this point will help. I am attaching a file that contains 11 instances of the GRIB2 message in question and no other GRIB2 messages. I hope that this will help track down the information that is needed. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: NLP-275663 Department: Support CONDUIT Priority: Normal Status: Closed
Attachment:
noProductID.grib2
Description: Binary data