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, One more thing, when you do get your data, what is the latency of the products? If near none, may not be a network issue, if pushing an hour, we may have located the problem... Thanks, -Jeff ____________________________ _____________________ Jeff Weber address@hidden Unidata Support PH:303-497-8676 NWS-COMET Case Study Library FX:303-497-8690 University Corp for Atmospheric Research 3300 Mitchell Ln http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 ________________________________________ ______________________ On Thu, 23 Aug 2001, Jeff Weber wrote: > Hi Adam, > > (jweber) laraine:/home/jweber 1 % ldmping -i5 -h sirocco.srcc.lsu.edu > Aug 23 19:55:33 State Elapsed Port Remote_Host > rpc_stat > Aug 23 19:55:33 RESPONDING 0.127509 388 sirocco.srcc.lsu.edu > Aug 23 19:55:38 RESPONDING 0.036370 388 sirocco.srcc.lsu.edu > Aug 23 19:55:43 RESPONDING 0.035674 388 sirocco.srcc.lsu.edu > Aug 23 19:55:48 RESPONDING 0.035661 388 sirocco.srcc.lsu.edu > Aug 23 19:55:53 RESPONDING 0.035857 388 sirocco.srcc.lsu.edu > Aug 23 19:55:58 RESPONDING 0.035385 388 sirocco.srcc.lsu.edu > Aug 23 19:56:03 RESPONDING 0.035772 388 sirocco.srcc.lsu.edu > Aug 23 19:56:08 RESPONDING 0.035702 388 sirocco.srcc.lsu.edu > > > Hmmm, cannot replicate here. This lends me to believe it may have > something to do with your ISP or network conditions. Perhaps it is getting > "clogged" and therefore cannot resolve the ldmping packets. > > The NNEXRAD issue may also be playing a part, we (LSU) may be feeding too > many folks the NNEXRAD feed, so the machine may fall behind for awhile > during these peak data periods...When this happens again, try doing a > traceroute, I know these are small packets, but it may lend some > additional info.. > > > There is no reason the LDM should just quit, and I am very surprised there > is no log entry regarding the shutdown. Could you please snip the tail of > your log and send to me, maybe I can see something in there that might > give a clue as to what is going on. > > I will contact LSU and see if any other downstream sites have mentioned > difficulties, we have not heard from them here at Unidata..but that does > not always mean all is well. > > What are you requesting from LSU? > > How is your request line configured? > > I guess we still have some "tuning" left for your LDM.. > > > I am cc'ing Anne Wilson who helps develop the LDM code, she is away this > week, but will be back monday and can lend insight then if we have not > solved the problem by then. > > Thank you, > > -Jeff > ____________________________ _____________________ > Jeff Weber address@hidden > Unidata Support PH:303-497-8676 > NWS-COMET Case Study Library FX:303-497-8690 > University Corp for Atmospheric Research 3300 Mitchell Ln > http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 > ________________________________________ ______________________ > > On Thu, 23 Aug 2001, adam taylor (994) wrote: > > > I am the new contact. address@hidden > > > > I have an interesting problem on this end but I'm not sure who to direct > > this to. When i run: > > > > ldmping -i5 -h sirocco.srcc.lsu.edu > > > > I get: > > > > (DATE) State Elapsed Port Remote_Host rpc_stat > > (THE DATE) NAMED 12.132903 0 sirocco.srcc.lsu.edu can't contact > > portmapper: > > RPC: Timed out > > and i get that almost without fail every time. Every once and a > > while i get it to say RESPONDING and a time of around 3 or so. > > > > I have gotten numbers in the 30's before but for the most part, 12 or so > > is the average. > > > > Also, I have been watching LSU's feed for a while and there are 5 to ten > > minute times where i get nothing but nexrad feed products and even then it > > is real slow. > > > > Also one more thing, the ldm server is just spontaniously quiting with no > > error message of anykind. I have noticed that it happens, or seems, then > > when there is a really bad network lag it seems to quit. I was watching > > it today and just all of a sudden the feed stopped. when i ran ldmadmin > > isrunning it came back as no. I have version 5.1.2 running on a dual P3 > > 933 with 1 GIG RAM running RedHat 7.0 > > > > Any throughts on this??? > > > > Thanks in advance > > > > Adam > > _________________________________________________________________________ > > > > On Thu, 23 Aug 2001, Jeff Weber wrote: > > > > > Hey Adam, > > > > > > While I have you... > > > > > > Is > > > > > > Chris Clarke > > > > > > address@hidden > > > > > > 318-342-1891 > > > > > > Still current contact info for UNL or should you be the contact? > > > > > > Thank you, > > > > > > -Jeff > > > ____________________________ _____________________ > > > Jeff Weber address@hidden > > > Unidata Support PH:303-497-8676 > > > NWS-COMET Case Study Library FX:303-497-8690 > > > University Corp for Atmospheric Research 3300 Mitchell Ln > > > http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 > > > ________________________________________ ______________________ > > > > > > On Thu, 23 Aug 2001, adam taylor (994) wrote: > > > > > > > Ok, the feed has decided to return to normal, we are finally getting the > > > > HDS and WMO feeds too. Thanks anyways. > > > > > > > > Adam > > > > > > > > > > > > > > > > > > > >