[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #IRP-426248]: More problems with dropping files.

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.

  • Subject: [LDM #IRP-426248]: More problems with dropping files.
  • Date: Fri, 07 Sep 2007 12:41:13 -0600
Mark,

> Hi Steve, I wanted to bring you up to speed on some weirdness I'm seeing
> on our LDM servers.  LDM1 is still dropping files, however, I've
> verified that while LDM1 is dropping files, it's also able to relay some
> of those files onto my test servers.  IE. I had 56 missing files on LDM1
> yesterday, but 52 missing on the 2 test servers.  I verified the files
> WERE missing on lDM1 and NOT missing on the 2 test servers.
> 
> This means LDM1 is actually receiving some files, but pqact isn't
> storing them locally.  Any ideas?

Some possibilities:

The "pqact" configuration-file entries don't catch
all possible products.

The "pqact" process can't keep up with the rate at which products
arrive.  In this case I would expect to see log messages from "pqact"
that contain the string "Processed oldest product in queue".

A "pqact" configuration-file is shared by more than one "pqact"
process.  See 
<http://www.unidata.ucar.edu/software/ldm/ldm-6.6.5/basics/programs.html#pqact>.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: IRP-426248
Department: Support LDM
Priority: High
Status: On Hold