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.
Milas, > I received this file from UTA this afternoon. It contains the ldmd.conf, > pqact.conf in effect > for at least the past day; and all of the log files. The most-recent LDM log file contained this Nov 03 19:37:47 Waterdrop rpc.ldmd[3319] NOTE: Starting Up (version: 6.8.1; built: Oct 22 2010 12:25:42) Nov 03 19:37:47 Waterdrop rpc.ldmd[3319] NOTE: Using local address 0.0.0.0:388 Nov 03 19:37:47 Waterdrop pqact[3321] NOTE: Starting Up Nov 03 19:37:47 Waterdrop pqact[3321] INFO: Successfully read configuration-file "/usr/local/ldm/etc/pqact.conf" Nov 03 19:37:47 Waterdrop pqact[3321] WARN: No such file or directory Nov 03 19:37:47 Waterdrop pqact[3321] WARN: stateRead(): Couldn't open "/usr/local/ldm/etc/pqact.conf.state" Nov 03 19:37:47 Waterdrop pqact[3321] WARN: Previous-state information doesn't exist. Continuing... Nov 03 19:37:47 Waterdrop pqact[3321] INFO: TS_ZERO TS_ENDT {{ANY, ".*"}} Nov 03 19:37:47 Waterdrop pqact[3321] INFO: 0 20101103193747.111 ANY 000 _BEGIN_ Nov 03 19:37:47 Waterdrop srh-ls-cpnrs1.srh.noaa.gov[3322] NOTE: Starting Up(6.8.1): srh-ls-cpnrs1.srh.noaa.gov:388 20101103183747.111 TS_ENDT {{EXP, "/data/ldad/ftp/ups2ldm/MPE/gis_text/.*"}} Nov 03 19:37:47 Waterdrop srh-ls-cpnrs1.srh.noaa.gov[3322] NOTE: Previous product-information file ".ce9740b37b2dfdfc0ad0274046161d97.info" doesn't exist Nov 03 19:37:47 Waterdrop srh-ls-cpnrs1.srh.noaa.gov[3322] NOTE: LDM-6 desired product-class: 20101103183747.112 TS_ENDT {{EXP, "/data/ldad/ftp/ups2ldm/MPE/gis_text/.*"}} Nov 03 19:37:47 Waterdrop srh-ls-cpnrs1.srh.noaa.gov[3322] NOTE: Upstream LDM-6 on srh-ls-cpnrs1.srh.noaa.gov is willing to be a primary feeder I don't see anything untoward in the above. In particular, the last entry indicates that the downstream LDM should be able to receive data-products that match the given selection criteria providing 1) the upstream LDM receives those data-products; and 2) the upstream LDM allows the downstream LDM to receive such data-products. You indicated that you verified the first condition. I'll need to see the LDM configuration-file (etc/ldmd.conf) of the upstream LDM to verify the second condition. Regards, Steve Emmerson Ticket Details =================== Ticket ID: FOR-229341 Department: Support LDM Priority: Normal Status: Open