[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Could you check please

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.

  • Subject: Re: Could you check please
  • Date: Tue, 22 Jan 2002 12:23:55 -0700
"Mark J. Laufersweiler" wrote:
> 
> Anne,
> 
> Looks like UNL is having trouble feeding NEXRAD from us here at OU.
> If you have time, could you check our ldm logs
> (http://stokes.metr.ou.edu) and see what maybe is the problem.
> 
> I have not heard from Clint. This is just my checking out all the
> logs since the upgrade and  seeing how well the new machine is
> performing.
> 
> Thanks.
> 
> mjl
> 
> Here are some other measures:
> 
> > ldmping papagayo.unl.edu
> Jan 18 18:01:16      State    Elapsed Port   Remote_Host          rpc_stat
> Jan 18 18:01:16 RESPONDING   0.073062  388   papagayo.unl.edu
> Jan 18 18:01:41 RESPONDING   0.013462  388   papagayo.unl.edu
> Jan 18 18:02:06 RESPONDING   0.013310  388   papagayo.unl.edu
> 
> > ping papagayo.unl.edu
> PING papagayo.unl.edu (129.93.52.150): 56 data bytes
> 64 bytes from 129.93.52.150: icmp_seq=0 ttl=248 time=12.968 ms
> 64 bytes from 129.93.52.150: icmp_seq=1 ttl=248 time=13.243 ms
> 64 bytes from 129.93.52.150: icmp_seq=2 ttl=248 time=13.265 ms
> 64 bytes from 129.93.52.150: icmp_seq=3 ttl=248 time=13.252 ms
> 64 bytes from 129.93.52.150: icmp_seq=4 ttl=248 time=13.302 ms
> 64 bytes from 129.93.52.150: icmp_seq=5 ttl=248 time=13.080 ms
> 64 bytes from 129.93.52.150: icmp_seq=6 ttl=248 time=13.171 ms
> 64 bytes from 129.93.52.150: icmp_seq=7 ttl=248 time=12.821 ms
> 64 bytes from 129.93.52.150: icmp_seq=8 ttl=248 time=13.094 ms
> ^C
> --- papagayo.unl.edu ping statistics ---
> 9 packets transmitted, 9 packets received, 0% packet loss
> round-trip min/avg/max/stddev = 12.821/13.133/13.302/0.150 ms
> 
> > traceroute papagayo.unl.edu
> traceroute to papagayo.unl.edu (129.93.52.150), 64 hops max, 40 byte packets
>  1  TM-65-D.del.GCN.ou.edu (129.15.192.1)  0.353 ms  0.248 ms  0.241 ms
>  2  TM-NOC-1-56.del.ou.edu (129.15.1.56)  0.327 ms  0.339 ms  0.304 ms
>  3  164.58.10.97 (164.58.10.97)  1.695 ms  0.767 ms  0.726 ms
>  4  oc12-pos-kscy.abilene.ucaid.edu (164.58.0.50)  7.341 ms  7.343 ms  7.198 
> ms
>  5  ks-2-p00.r.greatplains.net (164.113.238.194)  7.227 ms  7.486 ms  7.254 ms
>  6  ks-2-unl.r.greatplains.net (164.113.234.133)  12.861 ms  13.247 ms  
> 12.430 ms
>  7  * * *
>  8  papagayo.unl.edu (129.93.52.150)  13.058 ms  12.531 ms  12.608 ms
> 
> --
> --------------------------------------------------------------------
>   Dr. Mark J. Laufersweiler     |
>   School of Meteorology         |     Those who give up essential
>   University of Oklahoma        |   liberties for temporary safety
>   address@hidden                | deserve neither liberty nor safety.
>   (405) 325-6032                |             - Benjamin Franklin
>   (405) 325-7689  (fax)         |

Hi Mark,

I just took a look at your logs.  It looks as if the problem with
papagayo has gone away - only one reconnect in the past 28 hours.

Do you know what changed?

Anne
-- 
***************************************************
Anne Wilson                     UCAR Unidata Program            
address@hidden                 P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************