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 Ken, Pete Pokrandt CCed us on his reply to you yesterday. Since we haven't seen any additional email traffic from either you or Pete, we do not know if your problem has been resolved, or if you are in need of some assistance. Are you now receiving data? If not, have you examined your LDM log file(s) (~ldm/logs/ldmd.log*) to see if you can get an idea of what is amiss? One quick thought... if your LDM had been running for a long time and/or if you rebooted your machine without gracefully exiting the LDM first (via 'ldmadmin stop' as the user 'ldm'), your LDM queue could be damaged. Guessing that this could be the cause or your problem, we recommend that you do the following: <as 'ldm' on rain.agry.purdue.edu> cd ~ldm ldmadmin stop ldmadmin delqueue ldmadmin mkqueue ldmadmin start If you choose to delete and remake the queue, please let us (Pete and the UPC) know if this resolved your problem. Cheers, Tom > Ken (cc Unidata support) > > Nothing should have changed on my end, except maybe updating the ldm to > a newer version. I did update idd.aos.wisc.edu to a new machine, but > that was last summer, so I'd think if there were an error, we'd have > seen it a long time ago. There is definitely data flowing through > idd.aos.wisc.edu. > > Here's my allow line on idd.aos.wisc.edu: > > allow DDPLUS|HRS|IDS|DIFAX ^rain.agry.purdue.edu$ > > Here are the latest messages out of my ldmd.log that contain > agry.purdue.edu. > > > May 17 17:19:03 idd rain.agry.purdue.edu(feed)[5688] NOTE: Starting > Up(6.9.8/6): 20120517221639.533 TS_ENDT {{HDS, ".*"}}, SIG=NONE, Primary > May 17 17:19:03 idd rain.agry.purdue.edu(feed)[5688] NOTE: topo: > rain.agry.purdue.edu {{HDS, (.*)}} > May 17 17:19:03 idd rain.agry.purdue.edu(feed)[5687] NOTE: Starting > Up(6.9.8/6): 20120517221639.533 TS_ENDT {{IDS|DDPLUS, ".*"}}, SIG=NONE, > Primary > May 17 17:19:03 idd rain.agry.purdue.edu(feed)[5687] NOTE: topo: > rain.agry.purdue.edu {{IDS|DDPLUS, (.*)}} > May 21 12:24:05 idd rain.agry.purdue.edu(feed)[19021] NOTE: Starting > Up(6.9.8/6): 20120521171709.273 TS_ENDT {{HDS, ".*"}}, SIG=NONE, Primary > May 21 12:24:05 idd rain.agry.purdue.edu(feed)[19021] NOTE: topo: > rain.agry.purdue.edu {{HDS, (.*)}} > May 21 12:24:05 idd rain.agry.purdue.edu(feed)[19022] NOTE: Starting > Up(6.9.8/6): 20120521171709.059 TS_ENDT {{IDS|DDPLUS, ".*"}}, SIG=NONE, > Primary > May 21 12:24:05 idd rain.agry.purdue.edu(feed)[19022] NOTE: topo: > rain.agry.purdue.edu {{IDS|DDPLUS, (.*)}} > May 21 12:32:22 idd rain.agry.purdue.edu(feed)[19021] ERROR: Couldn't > flush connection; nullproc_6() failure to rain.agry.purdue.edu: RPC: > Unable to receive; errno = Connection reset by peer > May 21 12:32:22 idd rain.agry.purdue.edu(feed)[19022] ERROR: Couldn't > flush connection; nullproc_6() failure to rain.agry.purdue.edu: RPC: > Unable to receive; errno = Connection reset by peer > May 21 12:32:31 idd rain.agry.purdue.edu(feed)[19115] NOTE: Starting > Up(6.9.8/6): 20120521171709.059 TS_ENDT {{IDS|DDPLUS, ".*"}}, SIG=NONE, > Primary > May 21 12:32:31 idd rain.agry.purdue.edu(feed)[19115] NOTE: topo: > rain.agry.purdue.edu {{IDS|DDPLUS, (.*)}} > May 21 12:32:31 idd rain.agry.purdue.edu(feed)[19116] NOTE: Starting > Up(6.9.8/6): 20120521171709.273 TS_ENDT {{HDS, ".*"}}, SIG=NONE, Primary > May 21 12:32:31 idd rain.agry.purdue.edu(feed)[19116] NOTE: topo: > rain.agry.purdue.edu {{HDS, (.*)}} > > Are you still not seeing any data? What do your connection attempts look > like in your ldmd.log? > > Pete > > > On 05/21/2012 12:37 PM, Scheeringa, Kenneth L wrote: > > > > Hi Pete, > > > > I needed to reboot rain.agry.purdue.edu just now but found out after > > the reboot > > > > I am not seeing any products via ldmwatch from the idd.aos.wisc.edu > > LDM feed. > > > > I haven't restarted my LDM in a long time so maybe there has been a change > > > > on your end I have to catch up with? > > > > Ken Scheeringa > > > > Associate State Climatologist > > > > Indiana State Climate Office > > > > > -- > Pete Pokrandt - Systems Programmer > UW-Madison Dept of Atmospheric and Oceanic Sciences > 608-262-3086 - address@hidden > > > 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: VDJ-799591 Department: Support IDD Priority: Normal Status: Closed