[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Stokes Status
- Subject: Re: Stokes Status
- Date: Tue, 22 Jan 2002 14:56:41 -0700
"Mark J. Laufersweiler" wrote:
>
> Patrick (and Anne),
>
> I have noticed the RECLASS messages in my ldmd logfile as well. I am
> not sure as to what is going on with the feed. I know that nothing
> has changed in my ldmd.conf and I have you listed to receive the
> UNIDATA feed just as before. I am not sure what is the problem.
>
> I have included a few measures from stokes and traceroute is showing
> a slowdown at your gateway. UNL is also showing similar problems
> with their gateway as well.
>
> mjl
>
> > ldmping blizzard.storm.uni.edu
> Jan 22 16:52:43 State Elapsed Port Remote_Host
> rpc_stat
> Jan 22 16:52:43 RESPONDING 0.149686 388 blizzard.storm.uni.edu
> Jan 22 16:53:09 RESPONDING 0.106938 388 blizzard.storm.uni.edu
> Jan 22 16:53:34 RESPONDING 0.064857 388 blizzard.storm.uni.edu
> Jan 22 16:53:59 RESPONDING 0.042484 388 blizzard.storm.uni.edu
> Jan 22 16:54:24 RESPONDING 0.032805 388 blizzard.storm.uni.edu
> Jan 22 16:54:49 RESPONDING 0.035892 388 blizzard.storm.uni.edu
> Jan 22 16:55:14 RESPONDING 0.053825 388 blizzard.storm.uni.edu
> Jan 22 16:55:39 RESPONDING 0.032961 388 blizzard.storm.uni.edu
> Jan 22 16:56:04 RESPONDING 0.049337 388 blizzard.storm.uni.edu
> Jan 22 16:56:29 RESPONDING 0.043182 388 blizzard.storm.uni.edu
> Jan 22 16:56:54 RESPONDING 0.033116 388 blizzard.storm.uni.edu
> Jan 22 16:57:19 RESPONDING 0.067092 388 blizzard.storm.uni.edu
> ^C
>
> > ping blizzard.storm.uni.edu
> PING blizzard.storm.uni.edu (134.161.223.216): 56 data bytes
> 64 bytes from 134.161.223.216: icmp_seq=0 ttl=242 time=71.272 ms
> 64 bytes from 134.161.223.216: icmp_seq=1 ttl=242 time=52.737 ms
> 64 bytes from 134.161.223.216: icmp_seq=2 ttl=242 time=53.574 ms
> 64 bytes from 134.161.223.216: icmp_seq=3 ttl=242 time=52.268 ms
> 64 bytes from 134.161.223.216: icmp_seq=4 ttl=242 time=55.970 ms
> 64 bytes from 134.161.223.216: icmp_seq=5 ttl=242 time=58.439 ms
> 64 bytes from 134.161.223.216: icmp_seq=6 ttl=242 time=61.795 ms
> 64 bytes from 134.161.223.216: icmp_seq=7 ttl=242 time=53.086 ms
> 64 bytes from 134.161.223.216: icmp_seq=8 ttl=242 time=56.236 ms
> 64 bytes from 134.161.223.216: icmp_seq=9 ttl=242 time=51.634 ms
> 64 bytes from 134.161.223.216: icmp_seq=10 ttl=242 time=36.059 ms
> ^C
> --- blizzard.storm.uni.edu ping statistics ---
> 11 packets transmitted, 11 packets received, 0% packet loss
> round-trip min/avg/max/stddev = 36.059/54.825/71.272/8.053 ms
>
> > traceroute blizzard.storm.uni.edu
> traceroute to blizzard.storm.uni.edu (134.161.223.216), 64 hops max,
> 40 byte packets
> 1 TM-65-D.del.GCN.ou.edu (129.15.192.1) 0.488 ms 0.214 ms 0.288 ms
> 2 TM-NOC-1-56.del.ou.edu (129.15.1.56) 0.209 ms 0.263 ms 0.288 ms
> 3 164.58.10.97 (164.58.10.97) 0.799 ms 0.665 ms 0.676 ms
> 4 164.58.1.6 (164.58.1.6) 1.000 ms 1.444 ms 0.876 ms
> 5 164.58.1.6 (164.58.1.6) 0.996 ms 1.038 ms 0.875 ms
> 6 208.30.196.69 (208.30.196.69) 31.118 ms 27.130 ms 27.892 ms
> 7 sl-bb22-fw-4-3.sprintlink.net (144.232.8.249) 27.998 ms 27.714 ms
> 25.474 ms
> 8 sl-bb22-kc-14-0.sprintlink.net (144.232.18.186) 35.815 ms 38.268 ms
> 38.619 ms
> 9 sl-gw10-kc-6-0.sprintlink.net (144.232.23.82) 37.645 ms 34.937 ms
> 37.478 ms
> 10 sl-icomm-2-0.sprintlink.net (160.81.219.138) 46.736 ms 44.343 ms
> 44.766 ms
> 11 * * *
> 12 UNI-ICN-t3.icn.state.ia.us (207.165.237.182) 48.033 ms 43.402 ms
> 43.199 ms
> 13 starbase1.uni.edu (134.161.1.1) 43.076 ms 43.347 ms 43.301 ms
> 14 blizzard.storm.uni.edu (134.161.223.216) 45.036 ms 45.015 ms 43.770 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 and Patrick,
From stokes' logs I see that blizzard is having trouble. The ldmping
results above tell me that, at least for that time period, blizzard can
only recieve at best about 33 products per second, and at worst 16 from
stokes. I think that the connection doesn't support the volume of data
that blizzard is requesting.
I know that latencies have been a problem for U. Nothern Iowa in the
past. I was going to recommend that Patrick try (yet again?) to reduce
his requests and see if the RECLASSes are reduced. But, now I see that
the requests from blizzard were actually *increased* at 15:49 today:
Jan 22 15:48:36 blizzard(feed)[50732]: RECLASS: 20020122144736.578
TS_ENDT {{HDS, "^[YZ].[UR].*/mETA|^Y.A... KWBH|^[YZ].Q.*/mNGM|^Y.Q...
KWBC.*(/mAVN|/mSSIAVN)|^[YZ].Q.*/mRUC"},{IDS|DDPLUS, ".*"},{MCIDAS,
".*"}}
Jan 22 15:48:36 blizzard(feed)[50732]: pq_sequence failed: Input/output
error (errno = 5)
Jan 22 15:48:36 blizzard(feed)[50732]: Exiting
Jan 22 15:49:02 blizzard[50733]: Connection from blizzard.storm.uni.edu
Jan 22 15:49:02 blizzard(feed)[50733]: Starting Up: 20020122144901.973
TS_ENDT {{HDS, ".*"},{IDS|DDPLUS, ".*"},{MCIDAS, ".*"}}
Jan 22 15:49:02 blizzard(feed)[50733]: topo: blizzard.storm.uni.edu
UNIDATA
I'm passing this over to Jeff to continue. We have a few ideas about
some things to try...
Anne
--
***************************************************
Anne Wilson UCAR Unidata Program
address@hidden P.O. Box 3000
Boulder, CO 80307
----------------------------------------------------
Unidata WWW server http://www.unidata.ucar.edu/
****************************************************