John, > In the hour since I reconfigured adiabat to pull only NEXRAD2 > products, it hasn't ingested any other than the handfull it did > initially, at least according to 'ldmadmin watch'. > Because of that I'm less inclined to blame bandwidth for the > problem. I still can't figure out why LDM refuses to pull the data > from idd.unidata.ucar.edu. I think NEXRAD2 data is flowing from idd.unidata to Adiabat but that the data is too old and is being rejected. This is consistent with the output from the NEXRAD2, downstream LDM on Adiabat when sent a USR2 signal. I'm concerned about overlap in the REQUEST entries in the LDM configuration-file. REQUEST entries should either be disjoint in the data that they request or identical: there should be no overlap; otherwise, more bandwidth than necessary might be used. I don't know if this is the case with your entries because I don't know what data the upstream LDM-s have. If I had to, however, I would modify the entries to the following: request GEM ".*" ldm.meteo.ec.gc.ca request ANY-GEM-EXP-NEXRAD2-GPS-CONDUIT ".*" marconi.rwic.und.edu request ANY-GEM-EXP-NEXRAD2-GPS-CONDUIT ".*" 126.96.36.199 request ANY-GEM-EXP-NEXRAD2-GPS-CONDUIT ".*" 188.8.131.52 request ANY-GEM-EXP-NEXRAD2-GPS-CONDUIT ".*" 184.108.40.206 request EXP "^IA\.rwis......\.sao" mesonet.agron.iastate.edu request EXP "^IA\.snet......\.sao" mesonet.agron.iastate.edu request EXP ".*" pircsl4.agron.iastate.edu request GPS ".*" suomildm1.cosmic.ucar.edu request CONDUIT "$" idd.unidata.ucar.edu request CONDUIT "$" idd.unidata.ucar.edu request CONDUIT "$" idd.unidata.ucar.edu request CONDUIT "$" idd.unidata.ucar.edu request CONDUIT "$" idd.unidata.ucar.edu request NEXRAD2 ".*" idd.unidata.ucar.edu The modifications are to the "ALL" request to the 129.15.194.* hosts to exclude the data that's being requested from elsewhere. I notice that Adiabat is currently received NEXRAD2 data OK. Please keep an eye on it and keep me apprised. Regards, Steve Emmerson Ticket Details =================== Ticket ID: HMA-788722 Department: Support LDM Priority: Normal Status: On Hold
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.