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.
Justin, > I see the products in the notifyme but not in the ldmadmin watch... > > Jun 09 20:11:13 notifyme[1569] INFO: 2390242 20140609200922.192 EXP > 000 /usr1/tmp/mi.zip > Jun 09 20:11:27 notifyme[1569] INFO: 1138992 20140609200926.229 EXP > 000 /usr1/tmp/ut.zip > Jun 09 20:11:42 notifyme[1569] INFO: 516263 20140609201142.740 EXP > 000 NAT_N0Q_201406092010.gif > Jun 09 20:11:46 notifyme[1569] INFO: 1524512 20140609200930.264 EXP > 000 /usr1/tmp/nd.zip > Jun 09 20:11:49 notifyme[1569] INFO: 542856 20140609200934.287 EXP > 000 /usr1/tmp/me.zip > Jun 09 20:11:53 notifyme[1569] INFO: 241734 20140609201124.434 EXP > 000 hrrr.ER.t1800z.APCPsfc.F1400.Grb2 > Jun 09 20:12:01 notifyme[1569] INFO: 39 20140609201201.734 EXP > 000 srh-ls-cpnrs2a.keep_alive.20387 > > ldmadmin watch has our other request feeds to other servers, but not > srh-ls-cpnrs2.srh.noaa.gov. > > So, from your perspective, the only thing that could be blocking this feed > is their ALLOW statement? The only thing I can think of that's consistent with notifyme(1) working, "ldmadmin watch" not working, and nothing untoward in the LDM log file is a restrictive ALLOW entry at the upstream site. Please keep us apprised. > Thanks again Steve, > > Justin Regards, Steve Emmerson Ticket Details =================== Ticket ID: NDJ-862794 Department: Support LDM Priority: Normal Status: Closed