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 Rusty, re: > Here is the output: > > [ldm@geoprod4 etc]$ notifyme -vl- -f ANY -h iddb.unidata.ucar.edu > Aug 21 21:49:26 notifyme[26766] NOTE: Starting Up: iddb.unidata.ucar.edu: > 20150821214926.731 TS_ENDT {{ANY, ".*"}} > Aug 21 21:49:26 notifyme[26766] NOTE: LDM-5 desired product-class: > 20150821214926.731 TS_ENDT {{ANY, ".*"}} > Aug 21 21:49:26 notifyme[26766] INFO: Resolving iddb.unidata.ucar.edu to > 128.117.130.3 took 0.002357 seconds > Aug 21 21:50:16 notifyme[26766] NOTE: LDM-5 desired product-class: > 20150821214926.731 TS_ENDT {{ANY, ".*"}} > Aug 21 21:50:16 notifyme[26766] INFO: Resolving iddb.unidata.ucar.edu to > 128.117.130.3 took 0.006819 seconds > Aug 21 21:51:06 notifyme[26766] NOTE: LDM-5 desired product-class: > 20150821214926.731 TS_ENDT {{ANY, ".*"}} > Aug 21 21:51:06 notifyme[26766] INFO: Resolving iddb.unidata.ucar.edu to > 128.117.130.3 took 0.001491 seconds This proves that your 'notifyme' request to iddb.unidata.ucar.edu is not getting through. If it was, you would see a line that looks like: $ notifyme -vl- -f ANY -h iddb.unidata.ucar.edu Aug 21 22:01:59 notifyme[4675] NOTE: Starting Up: iddb.unidata.ucar.edu: 20150821220159.379 TS_ENDT {{ANY, ".*"}} Aug 21 22:01:59 notifyme[4675] NOTE: LDM-5 desired product-class: 20150821220159.379 TS_ENDT {{ANY, ".*"}} Aug 21 22:01:59 notifyme[4675] INFO: Resolving iddb.unidata.ucar.edu to 128.117.130.3 took 0.002046 seconds Aug 21 22:01:59 notifyme[4675] NOTE: NOTIFYME(iddb.unidata.ucar.edu): OK Note the OK indication. or one that said that the request was denied. Since neither of these show in your listing, and since our firewall is allowing all inbound traffic to port 388 on all of our cluster nodes, we are confident that the problem is that the NOAA firewall is blocking outbound requests to iddb.unidata.ucar.edu. The only solution for this (which will undoubtedly not be possible by tomorrow) is to have the NOAA network people to enable outbound traffic on port 388 to iddb.unidata.ucar.edu. You should pursue this even if it can't happen for tomorrow's outage as there will invariably be more in the future. 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: MHB-874023 Department: Support IDD Priority: Normal Status: Closed