Re: Top level CONDUIT relay

Thanks Justin,

I also had a typo in my message:
ldm1 is running slower than ldm2

Now if the feed to ldm2 all of a sudden slows down if Pete and other
sites add a request to it, it would really signal some sort of total
bandwidth limitation
on the I2 connection. Seemed a little coincidental that we had a show
period
of good connectivity to ldm1 after which it slowed way down.

Steve


On Tue, 2007-06-19 at 17:01 -0400, Justin Cooke wrote:
> I just realized the issue. When I disabled the "pqact" process on ldm2 
> earlier today it caused our monitor script (in cron, every 5 min) to 
> kill the LDM and restart it. I have removed the check for the pqact in 
> that monitor...things should be a bit better now.
> 
> Chi.Y.Kang wrote:
> > Huh, i thought you guys were on the system.  let me take a look on ldm2
> > and see what is going on.
> >
> >
> > Justin Cooke wrote:
> >   
> >> Chi.Y.Kang wrote:
> >>     
> >>> Steve Chiswell wrote:
> >>>  
> >>>       
> >>>> Pete and David,
> >>>>
> >>>> I changed the CONDUIT request lines at NSF and Unidata to request data
> >>>> from ldm1.woc.noaa.gov rather than ncepldm.woc.noaa.gov after seeing
> >>>> lots of
> >>>> disconnect/reconnects to the ncepldm virtual name.
> >>>>
> >>>> The LDM appears to have caught up here as an interim solution.
> >>>>
> >>>> Still don't know the cause of the problem.
> >>>>
> >>>> Steve
> >>>>       
> >>>>         
> >>> I know the NCEP was stop and starting the LDM service on the ldm2 box
> >>> where the VIp address is pointed to at this time.  how is the current
> >>> connection to LDM1?  is the speed of the conduit feed acceptable?
> >>>   
> >>>       
> >> Chi, NCEP has not restarted the LDM on ldm2 at all today. But looking
> >> at the logs it appears to be dying and getting restarted by cron.
> >>
> >> I will watch and see if I see anything.
> >>
> >> Justin
> >>     
> >
> >
> >   
-- 
Steve Chiswell <address@hidden>
Unidata