NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Justin, If the ldm on ldm2 is dying, then it may have a corrupt queue,so I would suggest doing : ldmamdin stop ldmadmin delqueue ldmadmin mkqueue ldmadmin start Is this the wueue that you remade on Friday? Thanks for all your afforts in looking at this, Steve Chiswell Unidata User Support On Tue, 2007-06-19 at 14:12 -0400, 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