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.
>From: Jim Koermer <address@hidden> >Organization: UCAR/Unidata >Keywords: 200305212159.h4LLxclL042738 LDM IDD pqing Unisys NOAAPORT Jim, >This seems to be the remaining LDM problem on cyclone from ldmd.conf: > >May 25 05:13:44 cyclone pqact[91074]: pipe_dbufput: >decoders/ldmConnect-e.zone0305/usr/local/ldm/data/gempak/nwx/pubprod/zone >write error > >I believe that these are the corresponding pqact.conf entries: ># Zone Forecasts ># 20030524 - ldmConnect version found in /home/ldm/decoders.old; made a hard ># link from ~/decoders/ldmConnect to ~/decoders.old/ldmConnect > >WMO ^FPUS5[1-6] .... ([0-3][0-9])([0-2][0-9]) > PIPE decoders/ldmConnect -e .zone (\1:yy)(\1:mm) >/usr/local/ldm/data/gempak/nwx/pubprod/zone >WMO ^FPAK[56][789] .... ([0-3][0-9])([0-2][0-9]) > PIPE decoders/ldmConnect -e .zone (\1:yy)(\1:mm) >/usr/local/ldm/data/gempak/nwx/pubprod/zone >WMO ^FPCA[46]2 .... ([0-3][0-9])([0-2][0-9]) > PIPE decoders/ldmConnect -e .zone (\1:yy)(\1:mm) >/usr/local/ldm/data/gempak/nwx/pubprod/zone >WMO ^FPHW01 .... ([0-3][0-9])([0-2][0-9]) > PIPE decoders/ldmConnect -e .zone (\1:yy)(\1:mm) >/usr/local/ldm/data/gempak/nwx/pubprod/zone >WMO ^FOPN00 .... ([0-3][0-9])([0-2][0-9]) > PIPE decoders/ldmConnect -e .zone (\1:yy)(\1:mm) >/usr/local/ldm/data/gempak/nwx/pubprod/zone ># > >Is perhaps this version of ldmConnect too old? It probably is, but I don't know if that is the cause of the problem. ldmConnect was one of the modules that I had to link from decoders.old. I just downloaded the latest decoders package to cyclone and unpacked it in ~ldm. I did a diff on the ldmConnect you have running currently (~ldm/decoders/ldmConnect) and the one in the new distribution (~ldm/decoders-2.4.4/src/ldmConnect/ldmConnect) and only see 4 lines that are different. Nonetheless, I removed the old one from ~ldm/decoders and replaced it with the latest version. I then edited the pqact.conf entries to make them look as much like ones that we ran awhile ago on a machine here at the UPC (our entries follow), and edited the new ldmConnect to set the location of perl to match where I found it on cyclone (/usr/bin/perl instead of /usr/local/bin/perl). For reference, here are the ldmConnect invocations that we were running: # Zone Forecasts (FPUS5[0-6], FPCA52, etc.) WMO ^...... .... ([0-3][0-9])([0-2][0-9]).*/pZFP PIPE /usr/local/ldm/decoders/ldmConnect -e .zone (\1:yyyy)(\1:mm) dat a/gempak/nwx/pubprod/zone WMO ^FPAK[56][789] .... ([0-3][0-9])([0-2][0-9]) PIPE /usr/local/ldm/decoders/ldmConnect -e .zone (\1:yyyy)(\1:mm) dat a/gempak/nwx/pubprod/zone WMO ^FOPN00 .... ([0-3][0-9])([0-2][0-9]) PIPE /usr/local/ldm/decoders/ldmConnect -e .zone (\1:yyyy)(\1:mm) dat a/gempak/nwx/pubprod/zone The largest differences I find between these actions and the ones you currently is the first action in this list and two others that you have. By the way, I just saw a .zone product created in ~ldm/data/gempak/nwx/pubprod/zone, so the new setup is working. I wonder if the ldmConnect actions were ever working on cyclone. I say this since the output directory for the combined ('connect'ed) products, ~ldm/data/gempak/nwx/pubprod/zone, did not exist in any directory tree that I saw on cyclone. I created the zone directory under pubprod to try and get this to work. >I checked write permissions and they were okay. I did check the general setup (pqact.conf entries; directory read/write permissions, etc.) and did not find anything obvious. I did just notice, however, that the location of perl in the old ldmConnect script did not match the Perl installation on cyclone. I have to now believe that this was the problem all along. Finally, I put a new LDM on snow, but saw that one wasn't running there anyway. Did you want/need that LDM-install? Also, I see that mammatus is still running an LDM-5 and reporting pqbinstats output. Is mammatus to be upgraded or decommissioned? The logins I have do not work for mammatus. Cheers, Tom