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.
Niles, > I have an LDM for which the network packets seem to be turning up just fine : > > rttc-ingest:ldm> ldmadmin watch -f NEXRAD > (Type ^D when finished) > Aug 31 16:34:42 pqutil INFO: 17356 20070831163442.538 NNEXRAD 186882371 > SDUS53 KPAH 311633 /pN0RVWX /NWSTG/0186882371 > Aug 31 16:34:42 pqutil INFO: 10416 20070831163442.553 NNEXRAD 186882372 > SDUS73 KPAH 311633 /pN0ZVWX /NWSTG/0186882372 > Aug 31 16:34:42 pqutil INFO: 11218 20070831163442.562 NNEXRAD 186882373 > SDUS22 KTAE 311633 /pN1RTLH /NWSTG/0186882373 > ^C > rttc-ingest:ldm> date -u > Fri Aug 31 16:34:46 UTC 2007 > > But files on disk are appearing late : > > ls -l /home/ldm/data/ldm/nids/uc/nids/BMX/BREF1/20070831 > total 96 > -rw-rw-r-- 1 ldm ldm 31946 Aug 31 16:15 20070831.1507.BREF1 > -rw-rw-r-- 1 ldm ldm 32282 Aug 31 16:26 20070831.1517.BREF1 > -rw-rw-r-- 1 ldm ldm 32520 Aug 31 16:34 20070831.1526.BREF1 It's impossible to tell from the above the delay between arrival and writing to disk. I suggest that you send a USR signal to the relevant "pqact" process so that you can see the delay from product-creation to product-processing. > This development co-incided with a network reconfiguration that changed some > IP numbers, > if that is relevant. That shouldn't be relevant. Regards, Steve Emmerson Ticket Details =================== Ticket ID: UUC-234187 Department: Support LDM Priority: Normal Status: Closed