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.
Steve, > We're having some weirdness with our ldm (version 6.13.5) over the last > couple of days. No config changes, so I'm at a loss about what is going on. > Specifically, we write metar data to 2 locations, one on the local disk, > the other in a networked directory. Here are the pqact.conf entries: > > IDS|DDPLUS ^SA.... .... ([0-3][0-9])([0-2][0-9]).. > STDIOFILE -close data/surface/sao/(\1:yy)(\1:mm)\1\2.sao > > and > > IDS|DDPLUS ^SA.... .... ([0-3][0-9])([0-2][0-9]).. > STDIOFILE -close /loc/local/surface/sao/(\1:yy)(\1:mm)\1\2.sao NB: The pathname of the local file is relative and the pathname of the network file is absolute. > Sorry for the wrapping. The /loc/local version (network) is working fine. > However, the first entry works for a while (few hours) then stops writing. > The log file shows this: > > 20170424T200229.188258Z pqact[18085] INFO palt.c:1222:prodAction() > stdiofile: -close data/surface/sao/17042420.sao and the ident is > SAUS41 KPHI 242002 /pMTRNEL > > 20170424T200229.188327Z pqact[18085] INFO palt.c:1222:prodAction() > stdiofile: -close /loc/local/surface/sao/17042420.sao and the ident > is SAUS41 KPHI 242002 /pMTRNEL > > 20170424T200229.189456Z pqact[18085] INFO filel.c:429:fl_removeAndFree() > Deleting closed STDIOFILE entry "/loc/local/surface/sao/17042420.sao" The above are just informational messages and have no bearing on your problem. > The product is in /loc/local/surface/sao/17042420.sao , but the > file data/surface/sao/17042420.sao does not exist. A stop, then restart of > the ldm results in the local file writes resuming. I've played with a > "-flush" instead of a "-close", but the behavior is the same. We have a > small queue (2GB) where product age can get down to 6 minutes. Have any > ideas why our local disk writes fail after a while but our networked writes > remain solid? Anything you can suggest? The current working directory of the pqact(1) process will be used to convert the relative output pathnames of the STDIOFILE action into absolute pathnames. The current working directory of the pqact(1) process will be the value of the "/pqact/datadir-path" registry parameter (or the home-directory of the LDM user if not specified). What is the output of the following command? regutil /pqact/datadir-path Regards, Steve Emmerson Ticket Details =================== Ticket ID: FLA-146766 Department: Support LDM 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.