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.
Hi Michael, Sorry for the dual answers from Steve and me... re: > This is what "notifyme" returns: > > [ldm@ftp-dmz-198 ~]$ notifyme -vl- -f ANY -h 155.80.186.10 > Jul 20 17:59:28 notifyme[21196] NOTE: Starting Up: 155.80.186.10: > 20120720175928.021 TS_ENDT {{ANY, ".*"}} > Jul 20 17:59:28 notifyme[21196] NOTE: LDM-5 desired product-class: > 20120720175928.021 TS_ENDT {{ANY, ".*"}} > Jul 20 18:00:20 notifyme[21196] NOTE: LDM-5 desired product-class: > 20120720175928.021 TS_ENDT {{ANY, ".*"}} > Jul 20 18:01:10 notifyme[21196] NOTE: LDM-5 desired product-class: > 20120720175928.021 TS_ENDT {{ANY, ".*"}} > Jul 20 18:02:02 notifyme[21196] NOTE: LDM-5 desired product-class: > 20120720175928.021 TS_ENDT {{ANY, ".*"}} > ^CJul 20 18:02:05 notifyme[21196] NOTE: exiting > [ldm@ftp-dmz-198 ~]$ When 'notifyme' successfully contacts an upstream host, one will see a message like: Jul 20 18:07:41 notifyme[3079] NOTE: NOTIFYME(155.80.186.10): OK Your 'notifyme' output does not include this thus indicating that it is not talking to the LDM on 155.80.186.10. Aside comment: - if the 'notifyme' request was being rejected, you would see a message like: Jul 20 18:09:57 notifyme[3121] ERROR: NOTIFYME(155.80.186.10): 7: Access denied by remote server Since you are not seeing an 'Access denied by remote server' message, the problem is _not_ one of being ALLOWed by the upstream macchine. re: > I get a response about every 50 seconds. This is different from the > ldmping results which doesn't return anything following the issuance of the > ldmping command. Yes, the ways that 'ldmping' and 'notifyme' work are different. They are both, however, saying the same thing -- your attempts to contact the ldm on 155.80.186.10 are _not_ making it to the LDM on 155.80.186.10. Since the LDM on 155.80.186.10 can 'ldmping' your local machine, I would venture to guess that the firewall on 155.80.186.10 is blocking things coming in on port 388. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: CLA-594617 Department: Support LDM Priority: Normal Status: Closed