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.
Mark, > The pqact.conf file is as generic as I can get it: > > > NEXRD2 > > ^L2-BZIP2/((K...)/(........)(......)/(.|..|...)/([0-9]|[0-9][0-9]|[0-9][0-9][0-9])) > > FILE /home2/ldm/nexradII/tmp/\2/\3/\2\3_\4_\5_\6.bz2 Do your downstream servers use the same "pqact.conf" entry? Do your downstream servers get any NEXRAD2 data-products from any other LDM? > There are no messages in the logs about 'Processed oldest product in > queue'. > > And there's only one pqact process running. I can imagine forces outside the LDM causing this phenomena, but not the LDM. Regards, Steve Emmerson Ticket Details =================== Ticket ID: IRP-426248 Department: Support LDM Priority: High Status: On Hold