Dave, > Steve, > > I don't think the errors have always been there. The script that uses the > PIPEd metar data rewrites it into a NetCDF file. This has always worked. > When I try running the new LDM, nothing is written to the file - go back to > the old version and data is again successfully written. That script was > written by Jim Cowie - maybe you know him? The pqact entries were also setup > be him. > > The metar2nc script exists in /home/ldm/util. > > Here's the METAR entry from pqact.conf: > # METAR's > WMO ^S[AP].* .... ([0-3][0-9])([0-2][0-9][0-5][0-9]) PIPE > metar2nc -t 30 -l logs -d data/dec_data/obs/metar etc/metar.cdl > > There are no isolated minus signs. The '-d' does not have a space. there > isn't a space in the log entry either. It must have gotten garbled when I > cut and pasted the entry. > > Yes, the 'logs' dir exists. It is actually a link to var/logs and the same > directory the LDM log is written to. > > lrwxrwxrwx 1 ldm ldm 12 Apr 29 18:34 data -> /d1/ldm/data/ > lrwxrwxrwx 1 ldm ldm 8 Apr 29 15:24 logs -> var/logs/ > > <pqact> > <config-path>/home/ldm/etc/pqact.conf</config-path> > <datadir-path>/home/ldm</datadir-path> > </pqact> OK. That all looks good. > Not knowing what to try, I changed the pqact entry to see if it made a > difference: > WMO ^S[AP].* .... ([0-3][0-9])([0-2][0-9][0-5][0-9]) PIPE > ~ldm/util/metar2nc -t 30 -l logs -d data/dec_data/obs/metar etc/metar.cdl That doesn't look like you changed "~ldm" to "/home/ldm". Did you? Did it work? If not, what was the error message? Regards, Steve Emmerson Ticket Details =================== Ticket ID: RQD-888533 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.