This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Unidata Support wrote: > > ------- Forwarded Message > > >To: address@hidden, > >To: address@hidden > >cc: address@hidden, > >cc: address@hidden, > >cc: address@hidden > >From: David Knight <address@hidden> > >Subject: Re: about halo in City College of New York > >Organization: UCAR/Unidata > >Keywords: 200108061915.f76JF1122065 > > Xiaodong Yan, > First, you should send all computer related problems > to address@hidden - this way whoever is available first > can respond to you. > > Nothing has changed at this that should effect you (at I don't think > it has). > > I've noticed that frequently after network problems that the ldm product > queue gets corrupted. > > I suggest you > 1) stop the ldm on halo (actually since I don't see any entries from halo > in our log files I suspect it is already down) > 2) recreate the ldm product queues > 3) restart the ldm on halo. > > Then we can see what if anything shows up in our logs here from halo. > > I do notice some strange things with halo: > > Ping seems to be very inconsistant: > ping -s halo.sci.ccny.cuny.edu > PING halo.sci.ccny.cuny.edu: 56 data bytes > 64 bytes from halo.sci.ccny.cuny.edu (134.74.52.189): icmp_seq=0. time=17. ms > 64 bytes from halo.sci.ccny.cuny.edu (134.74.52.189): icmp_seq=1. time=10. ms > 64 bytes from halo.sci.ccny.cuny.edu (134.74.52.189): icmp_seq=2. time=472. ms > 64 bytes from halo.sci.ccny.cuny.edu (134.74.52.189): icmp_seq=3. time=186. ms > 64 bytes from halo.sci.ccny.cuny.edu (134.74.52.189): icmp_seq=4. time=202. ms > 64 bytes from halo.sci.ccny.cuny.edu (134.74.52.189): icmp_seq=7. time=11. ms > 64 bytes from halo.sci.ccny.cuny.edu (134.74.52.189): icmp_seq=8. time=40. ms > 64 bytes from halo.sci.ccny.cuny.edu (134.74.52.189): icmp_seq=9. time=2646. > ms > 64 bytes from halo.sci.ccny.cuny.edu (134.74.52.189): icmp_seq=10. time=2482. > ms > 64 bytes from halo.sci.ccny.cuny.edu (134.74.52.189): icmp_seq=11. time=2432. > ms > 64 bytes from halo.sci.ccny.cuny.edu (134.74.52.189): icmp_seq=12. time=1781. > ms > 64 bytes from halo.sci.ccny.cuny.edu (134.74.52.189): icmp_seq=13. time=1313. > ms > > Also, ldmping produces portmapper errors - > > ldmping -v -l - -h halo.sci.ccny.cuny.edu > Aug 06 18:57:29 State Elapsed Port Remote_Host rpc_stat > Aug 06 18:57:41 NAMED 12.040540 0 halo.sci.ccny.cuny.edu can't > contact portmapper: RPC: Timed out > > I suspect there might still be either network problems at ccny, or, > perhaps a problem with halo. You might want to reboot that machine > to see if that helps. > > I've cc'ed this to address@hidden in case they have > some insight to share. > > David > > > > > Dear Dr. Knight, > > My name is Xiaodong Yan, a computer system administrator in City College of > > New York. Professor Hindman here ask me to help him figure out the problem > > with halo (halo.sci.ccny.cuny.edu, our ldm machine to get data) which isn't > > getting new data from the host "redwood.atmos.albany.edu". > > > > It happened last week, about August 02, when there is a college wide network > > congestion problem. Shortly after that halo isn't getting any new data. I > > try to figure out the problem, apparent the server "redwood" is still > > online, and halo has no problem to "ping" it. But when I use the "ldmping", > > I got following messages: > > > > Aug 06 18:10:20 SVC_UNAVAIL 0.034723 0 redwood.atmos.albany.edu > > h_clnt_create(redwood.atmos.albany.edu): Connection refused > > ..................( repeats) > > Aug 06 18:10:45 SVC_UNAVAIL 0.035243 0 redwood.atmos.albany.edu RPC: > > Program not registered > > ..................(repeats) > > > > I am not sure where the problem is. Is there any change at redwood at albany > > that disallow halo from getting new data? Or that's a problem with > > configuration here. Since we didn't make any changes recently, I hope you > > may give me clue about what we can > > do to get new data. > > > > regards, > > Xiaodong > > ================================= > > Mr. Xiaodong Yan > > System Administrator, Science Computing > > Room: Marshak Science Building, J-302 > > City College of City University of New York > > New York, NY 10031 > > Tel: 212.650.7885 > > Email: address@hidden > > Backup: address@hidden > > ================================= > > > > > > ------- End of Forwarded Message Hello Xiaodong Yan, I am the LDM support person at Unidata. Did you try David's suggestion of stopping the LDM, rebuilding the queue, and restarting? If so, how did that work for you? Anne -- *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://www.unidata.ucar.edu/ ****************************************************