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 Mike and Larry, Has the situation cleared up? It appears as if meteora is current from our end.. Jun 06 18:54:51 notifyme[3837]: 1629 20010606185919.691 HDS 109 SDUS83 KLOT 061846 /pDPALOT Jun 06 18:54:51 notifyme[3837]: 6067 20010606185919.732 HDS 110 SDUS83 KIND 061851 /pDPAIND Jun 06 18:54:51 notifyme[3837]: 8720 20010606185451.194 NNEXRAD 092 SDUS51 KBTV 061853 /pN0STYX Jun 06 18:54:51 notifyme[3837]: 6894 20010606185451.370 NNEXRAD 097 SDUS51 KCAR 061852 /pNTPCBW Jun 06 18:54:51 notifyme[3837]: 10922 20010606185451.391 NNEXRAD 098 SDUS56 KSEW 061852 /pN0VATX Jun 06 18:54:52 notifyme[3837]: 3596 20010606185451.402 NNEXRAD 099 SDUS53 KGRR 061848 /pNCRGRR Jun 06 18:54:52 notifyme[3837]: 8931 20010606185451.424 NNEXRAD 100 SDUS53 KDLH 061844 /pNCRDLH Jun 06 18:54:52 notifyme[3837]: 12886 20010606185451.509 NNEXRAD 101 SDUS53 KFSD 061853 /pN0SFSD Jun 06 18:54:52 notifyme[3837]: 256 20010606185451.516 NNEXRAD 102 SDUS51 KBUF 061848 /pNVLBUF Jun 06 18:54:52 notifyme[3837]: 10954 20010606185451.536 NNEXRAD 103 SDUS58 PAFC 061850 /pNTPAIH Jun 06 18:54:52 notifyme[3837]: 12897 20010606185451.579 NNEXRAD 105 SDUS53 KILX 061853 /pN0SILX Jun 06 18:54:52 notifyme[3837]: 13914 20010606185451.645 NNEXRAD 106 SDUS53 KIND 061851 /pNTPIND Jun 06 18:54:52 notifyme[3837]: 10630 20010606185451.709 NNEXRAD 111 SDUS52 KILM 061854 /pN0RLTX ^CJun 06 18:54:54 notifyme[3837]: Interrupt Jun 06 18:54:54 notifyme[3837]: exiting (jweber) laraine:/home/jweber 2 % Mike, Let me know if you are still having latency issues and I can do some network diagnostics. 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 Wed, 6 Jun 2001, Unidata Support wrote: > > ------- Forwarded Message > > >To: Mike Leuthold <address@hidden> > >cc: Larry Riddle <address@hidden>, > >cc: address@hidden > >From: Larry Riddle <address@hidden> > >Subject: Re: long latencies from meteora > >Organization: UCAR/Unidata > >Keywords: 200106061648.f56GmBp29597 > > --=====================_181219953==_.ALT > Content-Type: text/plain; charset="us-ascii"; format=flowed > > At 09:14 AM 6/6/2001 -0700, you wrote: > >Larry, > > I've been having trouble the last few days getting current data > >from meteora. It seems that the latencies build up and then data is > >dropped. I'm not having this problem when feeding from > >washington.edu. I've checked the traceroute from here to there and it > >looks fine so I'm a bit puzzled with where the problem lies. FYI. > > > >> A ldmping to meteora shows... > >> > >> > >> > ldmping meteora.ucsd.edu > >>Jun 06 16:16:52 State Elapsed Port Remote_Host rpc_stat > >>Jun 06 16:16:52 ADDRESSED 0.175122 0 meteora.ucsd.edu RPC: > >>Unable to receive; errno = Connection reset by peer > > Not sure what's going on. My file sizes all look good, so I'm probably > getting the data OK. > > I've just stopped the LDM, rebuilt the queue, and restarted. No science > behind it, but sometimes that's all the magic necessary to clear up this > kind of stuff. > > Let me know if there is any change. If not, I'll go talk to the network > wienie and see if somebody has done something to the portmapper or RPC. > > Larry > > > ---===---=-=-=-=-=-=-=-=-=-=-=====[\/]=====-=-=-=-=-=-=-=-=-=-=---===--- > -----===(* Climate's what we expect, but weather's what we > get. *)===----- > Larry Riddle : Climate Research Division : Scripps Institution of > Oceanography > University of California, San Diego : La Jolla, California 92093-0224 > Phone: (858) 534-1869 : Fax: (858) 534-8561 : E-Mail: address@hidden > --=====================_181219953==_.ALT > Content-Type: text/html; charset="us-ascii" > > <html> > At 09:14 AM 6/6/2001 -0700, you wrote:<br> > <blockquote type=cite class=cite cite>Larry,<br> > <x-tab> </x-tab>I've been > having trouble the last few days getting current data<br> > from meteora. It seems that the latencies build up and then data > is<br> > dropped. I'm not having this problem when feeding from<br> > washington.edu. I've checked the traceroute from here to there and > it<br> > looks fine so I'm a bit puzzled with where the problem lies. > FYI.<br> > <br> > <blockquote type=cite class=cite > cite> > A ldmping to meteora shows...<br> > <br> > <br> > > ldmping meteora.ucsd.edu<br> > Jun 06 16:16:52 State > Elapsed Port > Remote_Host > rpc_stat<br> > Jun 06 16:16:52 ADDRESSED 0.175122 > 0 meteora.ucsd.edu RPC: Unable to receive; errno = > Connection reset by peer</blockquote></blockquote><br> > Not sure what's going on. My file sizes all look good, so I'm > probably getting the data OK.<br> > <br> > I've just stopped the LDM, rebuilt the queue, and restarted. No > science behind it, but sometimes that's all the magic necessary to clear > up this kind of stuff.<br> > <br> > Let me know if there is any change. If not, I'll go talk to the > network wienie and see if somebody has done something to the portmapper > or RPC.<br> > <br> > Larry <br> > <br> > <x-sigsep><p></x-sigsep> > <font size=2> > ---===---=-=-=-=-=-=-=-=-=-=-=====[\/]=====-=-=-=-=-=-=-=-=-=-=---===---<br> > -----===(* Climate's what we expect, but weather's > what we get. *)===-----<br> > Larry Riddle : Climate Research Division : Scripps Institution of > Oceanography<br> > University of California, San Diego : La > Jolla, California 92093-0224<br> > Phone: (858) 534-1869 : Fax: (858) > 534-8561 : E-Mail: address@hidden</font></html> > > --=====================_181219953==_.ALT-- > > > ------- End of Forwarded Message > >