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.
Evan, Please don't send us email formatted in HTML. > I got the LDM working here at CSU and have become the primary feeder > for other people requesting LDM data in the lab.� I came across this > problem I wanted to get your advice on.<br> > > ldmadmin > watch lists files all the time... > > pqact.conf > says: > NEXRAD2 > ^L2-BZIP2/(....)/([0-9][0-9][0-9][0-9][0-1][0-9][0-3][0-9])([0-2][0-9][0-5][0-9])([0-9][0-9])� > � > FILE� � � /var/data/ldm/images/nexrad2/\1/\1_\2_\3 Use the "pqact.conf" pattern in a "notifyme" invocation. Does it work (i.e., show NEXRAD2 data-products)? > [ldm@iblmw1 > etc]$ ll /var/data/ldm/images/nexrad2<br> > total 0<br> > [ldm@iblmw1 etc]$ > I said > "chmod a+w > /var/data/ldm/*" - that didn't help at all You should use the "-R" option of "chmod" to allow all subdirectories to be writable. > and bin/logs ldmd.log says: > Jul 17 > 13:22:37 iblmw1 rpc.ldmd[10875] > NOTE: Starting Up (version: 6.6.5; built: Jul 17 2007 12:<br> > 11:48)<br> > Jul 17 13:22:37 iblmw1 rpc.ldmd[10875] NOTE: Using local address > 0.0.0.0:388<br> > Jul 17 13:22:37 iblmw1 pqact[10876] NOTE: Starting Up<br> > Jul 17 13:22:37 iblmw1 pqact[10876] NOTE: Starting from insertion-time > 2007-07-17 13:22:34.04964<br> > 1 UTC<br> > Jul 17 13:22:37 iblmw1 rtstats[10877] NOTE: Starting Up (10875)<br> > Jul 17 13:22:37 iblmw1 192.168.38.86[10878] NOTE: Starting Up(6.6.5): > 192.168.38.86:388 20070717<br> > 122237.059 TS_ENDT {{NEXRAD2,� ".*"}}<br> > Jul 17 13:22:37 iblmw1 192.168.38.86[10878] NOTE: LDM-6 desired > product-class: > 20070717122237.06<br> > 0 TS_ENDT {{NEXRAD2,� ".*"},{NONE,� > "SIG=dfe0840ae1644e1f7444604e9ac6fd5d"}}<br> > Jul 17 13:22:37 iblmw1 192.168.38.86[10878] NOTE: Upstream LDM-6 on > 192.168.38.86 is willing to<br> > be a primary feeder<br> > Jul 17 13:24:02 iblmw1 rtstats[10877] WARN: Couldn't connect to LDM on > rtstats.unidata.ucar.edu<br> > using either port 388 or portmapper; : RPC: Remote system error - > Connection > refused<br> > Jul 17 13:25:19 iblmw1 last message repeated 129 times<br> > Jul 17 13:26:44 iblmw1 last message repeated 130 times<br> > Jul 17 13:28:12 iblmw1 last message repeated 130 times<br> > ldmd.log (END)<br> > </span></font></p> > <p class="MsoNormal">Can you decipher the problem here Steve?� It > seems > the data is coming into the LDM but is not being saved.� Is the line > in > the pqact.conf file suspect?� What is the purpose/effect of the > rtstats > warning?<br> Don't worry about the "rtstats" messages. > </p> > <p class="MsoNormal">The second issue I have is one of LDM NEXRAD2 feed > type bandwidth.� It seems the NEXRAD2 feed is really bogging down the > network in our lab.� Is there anyway possible to only transmit data > from 1 or 2 NEXRAD sites?� You can request data from only one or two sites. > Can something be configured on the upstream > server to only pass data from certain radar to downstream LDMs?� This > would really help us out a lot.<br> Upstream filtering is possible (see <http://www.unidata.ucar.edu/software/ldm/ldm-current/basics/ldmd.conf.html#ALLOW>). I recommend, however, only requesting the sites in which you're interested. Regards, Steve Emmerson Ticket Details =================== Ticket ID: RKK-379892 Department: Support LDM Priority: Normal Status: Closed