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.
Thanks, Steve. I have noaaport logging into it's own log file now. We'll see what turns up? Bruce On Wed, Jun 3, 2015 at 1:59 PM, Steve Emmerson <emmerson@xxxxxxxx> wrote: > Bruce, > > The `noaaportIngester` utility can be configured to use a different log > file than the LDM log file via the "-u" option. If that option is used, > then messages will be logged according to the entry for "local<n>", where > <n> is the argument of the "-u" option. For example, the following LDM > configuration-file entry > > EXEC "noaaportIngester -m 224.0.1.1 -n -u 3" > > will cause messages to be logged according to the "local3" entry in the > system logging daemon's configuration-file. > > Regards, > Steve Emmerson > > On Wed, Jun 3, 2015 at 12:36 PM, Bruce Haynie - NOAA Federal < > bruce.haynie@xxxxxxxx> wrote: > >> Steve, >> >> Assuming I'm looking in the correct log file, that string does not exist >> in ldmd.log on our NOAAPort ingester machine. I turned on ldm's debug mode >> to include more logging info. >> >> Bruce >> >> On Wed, Jun 3, 2015 at 11:11 AM, Steve Emmerson <emmerson@xxxxxxxx> >> wrote: >> >>> Bruce, >>> >>> Search for the string "Couldn't get parameter info:" in the log file for >>> your LDM NOAAPort ingester. This will identify the relevant fields of the >>> missing parameter. See if you can find that parameter in any of the GRIB2 >>> table files and copy it to the file identified in the log message. >>> >>> Regards, >>> Steve Emmerson >>> >>> On Wed, Jun 3, 2015 at 9:23 AM, Bruce Haynie - NOAA Federal < >>> bruce.haynie@xxxxxxxx> wrote: >>> >>>> Fellow LDMers: >>>> >>>> Sorry to bother the list with what is probably a tables problem. >>>> >>>> Our ldmd.log files are filling with errors like the following: >>>> >>>> Jun 3 09:24:45 noaaportIngester[26097] ERROR: [gb22gem.c:76] [GB 1] >>>> Couldn't get parameter values >>>> Jun 3 09:24:45 noaaportIngester[26097] ERROR: [grib2name.c:780] >>>> Couldn't decode GRIB2 message. WMO header="LGXP30 KNHC 030600" >>>> >>>> All error messages point to the NHC probabilistic storm >>>> surge/inundation products. I suspect this is a table issue, but I'm not >>>> sure which table to update and what info to use to update the table. >>>> >>>> Any suggestions? Maybe some updated tables exist somewhere? We are >>>> running ldm-6.12.13 >>>> >>>> Thanks! >>>> >>>> Bruce >>>> >>>> >>>> >>>> -- >>>> >>>> Bruce Haynie, NW5S >>>> Electronic Systems Analyst >>>> National Weather Service >>>> Lubbock, TX >>>> Bruce.Haynie@xxxxxxxx >>>> >>>> >>>> _______________________________________________ >>>> ldm-users mailing list >>>> ldm-users@xxxxxxxxxxxxxxxx >>>> For list information or to unsubscribe, visit: >>>> http://www.unidata.ucar.edu/mailing_lists/ >>>> >>> >>> >> >> >> -- >> >> Bruce Haynie, NW5S >> Electronic Systems Analyst >> National Weather Service >> Lubbock, TX >> Bruce.Haynie@xxxxxxxx >> >> > -- Bruce Haynie, NW5S Electronic Systems Analyst National Weather Service Lubbock, TX Bruce.Haynie@xxxxxxxx
ldm-users archives: