rpc timed out errors

• To: ldm-users@xxxxxxxxxxxxxxxx
• Subject: rpc timed out errors
• From: Mike Leuthold <leuthold@xxxxxxxxxxxxxxxx>
• Date: Tue, 6 Aug 2002 09:20:31 -0700

Hello,
        Arizona has recently experienced problems getting data from
upstream sites and sending data to downstream sites.  Ldmping to some
sites never responds, but others it will after a few timeouts.  

[ldm@nimbus ~/etc]$ ldmping -t2 aeolus.ucsd.edu
Aug 06 16:05:01      State    Elapsed Port   Remote_Host           rpc_stat
Aug 06 16:05:03   H_CLNTED   2.016290  388   aeolus.ucsd.edu  select: RPC: 
Timed out
Aug 06 16:05:30  ADDRESSED   2.000402    0   aeolus.ucsd.edu  RPC: Timed out
Aug 06 16:05:58      NAMED   2.020380    0   aeolus.ucsd.edu  can't contact 
portmapper: RPC: Timed out
Aug 06 16:06:25   H_CLNTED   2.017000  388   aeolus.ucsd.edu  select: RPC: 
Timed out
Aug 06 16:06:52  ADDRESSED   2.000363    0   aeolus.ucsd.edu  RPC: Timed out
Aug 06 16:07:19      NAMED   2.020366    0   aeolus.ucsd.edu  can't contact 
portmapper: RPC: Timed out

[ldm@nimbus ~/etc]$ ldmping -t2  cirp.met.utah.edu
Aug 06 16:13:33      State    Elapsed Port   Remote_Host
Aug 06 16:13:35   H_CLNTED   2.012154  388   cirp.met.utah.edu  select: RPC: 
Timed out
Aug 06 16:14:02  ADDRESSED   2.000383    0   cirp.met.utah.edu  RPC: Timedout
Aug 06 16:14:30      NAMED   2.020340    0   cirp.met.utah.edu  can'tcontact 
portmapper: RPC: Timed out
Aug 06 16:14:57   H_CLNTED   2.010341  388   cirp.met.utah.edu  select: RPC: 
Timed out
Aug 06 16:15:24  ADDRESSED   2.000371    0   cirp.met.utah.edu  RPC: Timedout
Aug 06 16:15:51      NAMED   2.020371    0   cirp.met.utah.edu  can'tcontact 
portmapper: RPC: Timed out
Aug 06 16:16:18   H_CLNTED   2.010325  388   cirp.met.utah.edu  select:RPC: 
Timed out


[ldm@nimbus ~/etc]$ ldmping -t2 -i2 sunny89.atmos.washington.edu
Aug 06 16:08:02      State    Elapsed Port   Remote_Host           rpc_stat
Aug 06 16:08:04   H_CLNTED   2.012256  388   sunny89.atmos.washington.edu  
select: RPC: Timed out
Aug 06 16:08:08  ADDRESSED   2.000354    0   sunny89.atmos.washington.edu  RPC: 
Timed out
Aug 06 16:08:10 RESPONDING   0.194701  388   sunny89.atmos.washington.edu
Aug 06 16:08:12 RESPONDING   0.047653  388   sunny89.atmos.washington.edu
Aug 06 16:08:14 RESPONDING   0.047981  388   sunny89.atmos.washington.edu
Aug 06 16:08:16 RESPONDING   0.053682  388   sunny89.atmos.washington.edu
Aug 06 16:08:18 RESPONDING   0.047599  388   sunny89.atmos.washington.edu

cyclone 30% ldmping -t2 motherlode.ucar.edu
Aug 06 16:07:18      State    Elapsed Port   Remote_Host           rpc_stat
Aug 06 16:07:20   H_CLNTED   2.027280  388   motherlode.ucar.edu  select: Timed 
out
Aug 06 16:07:47  ADDRESSED   1.999823    0   motherlode.ucar.edu  Timed out
Aug 06 16:08:12 RESPONDING   0.100701  388   motherlode.ucar.edu
Aug 06 16:08:37 RESPONDING   0.020170  388   motherlode.ucar.edu
Aug 06 16:09:02 RESPONDING   0.027098  388   motherlode.ucar.edu


My thinking was that it was related to Arizona's Telecom people fooling
with a firewall since my problems started around the same time.  Telecom
says that they are no longer running it.  What goes against the firewall
this theory is that telnet can connect via port 388, some sites do
eventually respond to ldmping, and I do get some data from these sites,
for awhile.
Any ideas?

thanks.

Mike


 --
Mike Leuthold
Atmospheric Sciences/Institute of Atmospheric Physics
University of Arizona
leuthold@xxxxxxxxxxxxxxxx
520-621-2863

• Follow-Ups:
  • Re: rpc timed out errors
    • From: Mike Leuthold
  • Re: rpc timed out errors
    • From: Gilbert Sebenste