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 Adam, re: tornado clock's off > Yea, before i sent the message i checked the clock and it was 57 > seconds behind. I synced the clock and restarted everything. Since > it still did not work, i sent in a support message. OK. Thanks for checking the clock first! re: > when i run this command: > > notifyme -v -h idd.unidata.ucar.edu > > I see data comming in, in the ldmd.log file: > > Aug 20 21:17:46 tornado notifyme[18233] INFO: > 7f460a6036dd904f92a867ec91d394b2 28140 20120820211745.420 NEXRAD2 765006 > L2-BZIP2/KCLX/20120820211729/765/6/I/V03/0 > Aug 20 21:17:46 tornado notifyme[18233] INFO: > 7e578a6f271d7672441491d6175ebf4f 60167 20120820211745.217 NEXRAD2 356044 > L2-BZIP2/KLOT/20120820211530/356/44/I/V06/0 I checked all of the real servers that comprise idd.unidata.ucar.edu. I found the 'notifyme' connections by tornado, and they looked normal. The feed request(s) showed up OK also. Because of these two findings I decided to restart the LDM on the cluster node that was servicing tornado to see if the situation would clear. I see that tornado reconnected at 15:41:24: Aug 20 15:41:24 uni20 tornado.geos.ulm.edu(feed)[17199] NOTE: Starting Up(6.8.0/6): 20120820204123.086 TS_ENDT {{NEXRAD2|GEM|FNMOC|CONDUIT, ".*"}}, SIG=988b1aa8eeb286adb8e5c942b3d5935a, Primary Aug 20 15:41:24 uni20 tornado.geos.ulm.edu(feed)[17199] NOTE: topo: tornado.geos.ulm.edu {{NEXRAD2|GEM|FNMOC|CONDUIT, (.*)}} Aug 20 15:43:01 uni20 tornado.geos.ulm.edu(feed)[17262] NOTE: Starting Up(6.8.0/6): 20120820204258.473 TS_ENDT {{NEXRAD2|GEM|FNMOC|CONDUIT, ".*"}}, SIG=57828d8b4d7fdd5f742ca15d6daa1028, Primary Aug 20 15:43:01 uni20 tornado.geos.ulm.edu(feed)[17262] NOTE: topo: tornado.geos.ulm.edu {{NEXRAD2|GEM|FNMOC|CONDUIT, (.*)}} Aug 20 15:43:50 uni20 tornado.geos.ulm.edu(noti)[17736] NOTE: Starting Up(6.8.0/5): 20120820214350.217 TS_ENDT {{EXP|NXRDSRC|NEXRAD2|NEXRAD3|NPORT|NIMAGE|GEM|FNMOC|GPS|FAA604|DIFAX|NMC|FSL5|FSL4|FSL3|FSL2|UNIDATA|SPARE|0x80000000, ".*"}} Aug 20 15:43:50 uni20 tornado.geos.ulm.edu(noti)[17736] NOTE: topo: tornado.geos.ulm.edu EXP|NXRDSRC|NEXRAD2|NEXRAD3|NPORT|NIMAGE|GEM|FNMOC|GPS|FAA604|DIFAX|NMC|FSL5|FSL4|FSL3|FSL2|UNIDATA|SPARE|0x80000000 Question: - are you now seeing data from idd.unidata.ucar.edu in the tornado LDM queue? re: > But when i run 'ldmadmin watch' I see nothing except the UNIDATA feed > showing up from pavan and LIGHTNING from striker2 Just for a sanity check, please run: <as 'ldm'> notifyme -vl- -o 300 This should show the same thing as 'ldmadmin watch', but ... re: > Any thoughts? Please try the 'notifyme' invocation and let us know what it shows. re: >Do i need to move this into the support-ldm area? No. Those who read the support-idd inquiries also read support-ldm inquiries, so moving the department will not result in more eyes looking into the problem. 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: HIF-625790 Department: Support IDD Priority: Normal Status: Closed