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.
Jennifer, >> What are the pqact(1) configuration-file entries for the "data/dds/sa/*.sa" >> files? > > AHA! The pqact.conf file was not updated — oops, my mistake Been there. Done that. Bought the T-shirt. > — the following entries are (were) missing in the new LDM’s pqact.conf: > > # All metars in files by day and hour. > IDS|DDPLUS > ^SA.... .... (..)(..).* > FILE data/dds/sa/(\1:yyyy)(\1:mm)\1\2.sa > > # All warnings watches etc in files by day and hour. > IDS|DDPLUS ^W..... .... (..)(..).* > FILE data/dds/w/(\1:yyyy)(\1:mm)\1\2.w > > # All Synoptic reports in files by day > IDS|DDPLUS > ^S[IMN].... .... (..).* > FILE data/dds/sn/(\1:yyyy)(\1:mm)\1.sn > > # All upper air reports in files by day > IDS|DDPLUS > ^U..... .... (..).* > FILE data/dds/u/(\1:yyyy)(\1:mm)\1.u > # All FNEXRAD > FNEXRAD > ^radar_mosaic > STDIOFILE data/fnexrad/%y%m%d%H%M.mosaic > # All NIMAGE > NIMAGE > (TIG[NE]..) KNES (..)(....) > STDIOFILE data/nimage/(\2:yyyy)(\2:mm)\2\3.\1 > > Without these entries, I am surprised LDM was doing anything right, but the > files in /data/fnexrad and data/nimage and the others were updating properly. > After editing pqact.conf, I ran the following commands: > > colaweb.gmu.edu<http://colaweb.gmu.edu>[ldm]:~ # ldmadmin stop > colaweb.gmu.edu<http://colaweb.gmu.edu>[ldm]:~ # ldmadmin clean > colaweb.gmu.edu<http://colaweb.gmu.edu>[ldm]:~ # ldmadmin delqueue > colaweb.gmu.edu<http://colaweb.gmu.edu>[ldm]:~ # ldmadmin mkqueue > colaweb.gmu.edu<http://colaweb.gmu.edu>[ldm]:~ # ldmadmin start > > I will see how things go from here. I will respond again if that hasn’t fixed > it in a few hours. > > >> What is the output of the command "ulimit -a" on the two systems? > > ulimit: Command not found. You must be using a user-shell like csh(1) -- in which case try the command "limit" on both systems. Regards, Steve Emmerson Ticket Details =================== Ticket ID: MIY-170840 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.