[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SA19 -LDM timing out.
- Subject: Re: SA19 -LDM timing out.
- Date: Wed, 22 Jan 2003 16:51:07 -0700 (MST)
HI,
Am I correct in assuming that no data has been recieved since it failed?
I am currently, and back 15000 seconds seeing nada..
/local/ldm/etc% notifyme -vl - -h 117.16.1.45 -o 15000
Jan 22 23:45:37 notifyme[9424]: Starting Up: 117.16.1.45:
20030122193537.380 TS_ENDT {{ANY, ".*"}}
^CJan 22 23:46:01 notifyme[9424]: Interrupt
Jan 22 23:46:01 notifyme[9424]: exiting
/local/ldm/etc% notifyme -vl - -h 198.215.11.31 -o 15000
Jan 22 23:46:25 notifyme[9436]: Starting Up: 198.215.11.31:
20030122193625.536 TS_ENDT {{ANY, ".*"}}
^CJan 22 23:46:46 notifyme[9436]: Interrupt
Jan 22 23:46:46 notifyme[9436]: exiting
I am headed out currently but will dig in deeper tomorrow, unless my wife
has our baby...any day now! But I will not be out of office long, but if
you do not hear from me tomorrow, please redirect to
address@hidden...I will get it either way if i am here, but if
gone will still get attention..
Cheers,
-Jeff
____________________________ _____________________
Jeff Weber address@hidden
Unidata Support PH:303-497-8676
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, 22 Jan 2003, Teresa Van Hove wrote:
> Jeff,
>
> We have a site that was down for a month and they changed some network
> stuff and now the site is back up, but LDM is timing out. Here's what
> I found with a little poking:
>
>
> -- ldmping 198.215.11.31
> Jan 22 22:47:36 State Elapsed Port Remote_Host
> rpc_stat
> Jan 22 22:47:46 SVC_UNAVAIL 9.994689 0 198.215.11.31
> h_clnt_create(198.215.11.31): Timed out while creating connection
> Jan 22 22:48:11 ADDRESSED 0.000004 0 198.215.11.31
> h_clnt_create(198.215.11.31): Timed out while creating connection
>
> Do you have any suggestions? the SA19 cpu is running portmap. They
> are doing some IP 'aliasing' (198.215.11.31 is the public IP#, but
> internally the CPU is 117.16.1.45
>
> LDM was working for the site before, and I can ldmping to our LDM CPU
> (128.117.29.217) from there.
>
> I may be out all day tomorrow, so please cc Maggie with any
> suggestions.
> Thanks Much,
>
> Teresa
>
>
> Teresa Van Hove
> Associate Scientist GST/UCAR
> address@hidden
> ---------------------------------
>