This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi, re: > I recently configured my LDM to start receiving a small set of radar > products from Unidata for ingest into AWIPS, however I'm getting errors in > my "ldmd.log". I was hoping you could help me interpret those errors? We will certainly try :-) re: > This is one of my entries in "ldmd.conf" for a specific NEXRAD Level III > product and a specific station: > > REQUEST NEXRAD "SDUS[23578]. .... > ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(DAA)(AIH)" idd.unidata.ucar.edu Quick comment: The extended regular expression (ERE) you are using seems overly complicated for what you seem to want. A much simpler REQUEST could look like: REQUEST NEXRAD3 "/pDAAAIH" idd.unidata.ucar.edu The LDM utility 'notifyme' is very handy since it can be used to test EREs to see if they specify what is, in fact, wanted. For instance: <as 'ldm'> notifyme -vl- -f NEXRAD3 -p "/pDAAAIH" -o 3600 -h idd.unidata.ucar.edu The output from this 'notifyme' invocation on your system should look like: ~: notifyme -vl- -f NEXRAD3 -p "/pDAAAIH" -o 3600 -h idd.unidata.ucar.edu 20200904T145843.294018Z notifyme[402111] notifyme.c:main:363 NOTE Starting Up: idd.unidata.ucar.edu: 20200904135843.293800 TS_ENDT {{NEXRAD3, "/pDAAAIH"}} 20200904T145843.294070Z notifyme[402111] ldm5_clnt.c:forn5:460 NOTE LDM-5 desired product-class: 20200904135843.293800 TS_ENDT {{NEXRAD3, "/pDAAAIH"}} 20200904T145843.294534Z notifyme[402111] error.c:err_log:236 INFO Resolving idd.unidata.ucar.edu to 128.117.135.3 took 0.000395 seconds 20200904T145843.305285Z notifyme[402111] ldm5_clnt.c:forn_signon:294 NOTE NOTIFYME(idd.unidata.ucar.edu): OK 20200904T145845.269047Z notifyme[402111] notifyme.c:notifymeprog_5:212 INFO 16300 20200904140239.462724 NEXRAD3 168654802 SDUS88 PAFC 041357 /pDAAAIH !nids/ 20200904T145845.945111Z notifyme[402111] notifyme.c:notifymeprog_5:212 INFO 16238 20200904140822.219223 NEXRAD3 168668542 SDUS88 PAFC 041402 /pDAAAIH !nids/ ... Aside: I use the canonical name for the NEXRAD Level 3 LDM/IDD feed, NEXRAD3 instead of the other names by which it is known, NEXRAD, NNEXRAD. re: > and this is my entry in "pqact.conf" > > NEXRAD ^SDUS[23578].* > FILE -close /awips2/edex/data/manual/\1 First, the '\1' notation in the FILE action file name will be replaced with the Product ID clause that is contained in the first set of parentheses in your ERE. Your action contains no clauses surrounded by parentheses, so nothing will be matched, and '\1' will be blank. re: > The intent was that files received would be copied directly into the AWIPS > manual ingest directory "/awips2/edex/data/manual" but it's not working. It is not working because your ERE in your pattern-action file action does not indicate which portion of the Product IDs should be identified by the '\1' notation. re: > Here are some of the errors I'm getting. > > 0200904T013338.393990Z pqact[8298] > filel.c:unio_prodput:1285 ERROR Couldn't get entry for product > "SDUS88 PAFC 040128 /pDAAAIH !nids/" > 20200904T013338.394011Z pqact[8298] palt.c:prodAction:1237 > ERROR Couldn't process product: feedtype=NEXRAD3, > pattern="^SDUS[23578].*", action=file, args="-close > /awips2/edex/data/manual/\1" > 20200904T013356.548835Z pqact[8298] filel.c:unio_open:1001 > ERROR Is a directory > 20200904T013356.548887Z pqact[8298] filel.c:unio_open:1001 > ERROR Couldn't open file "/awips2/edex/data/manual/" > > It seems like LDM doesn't have permission to write to that directory Your action is trying to write the product into a file name that matches the directory name, and, presumably, that directory already exists, so it will fail. re: > however there are several other products we receive via LDM that do the > same thing successfully. I would guess that the EREs for those products do contain clauses within parentheses that will match part of the Product IDs that are being checked. re: > Thanks for any suggestions about what might be going wrong? I suspect that the action you want to use would look something like: NEXRAD3<tab>^SDUS[23578]. .... ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(DAA)(AIH) <tab>FILE<tab>-close /awips2/edex/data/manual/\5_\4_\1\2\3 For the first match from the 'notifyme' listing above, this would have created the file: /awips2/edex/data/manual/AIH_DAA_041357 This assumes, of course, that the directory '/awips2/edex/data/manual' is writable by the user running your LDM. 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: OWZ-603499 Department: Support IDD Priority: Normal Status: Closed =================== 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.