Justin, I figured it was something like that. I need to think a bit. I'll get back to you as soon as I can. Regards, Steve Emmerson ------- Original Message Date: Wed, 19 Oct 2005 09:16:45 -0400 From: Justin Cooke <address@hidden>To: Steve Emmerson <address@hidden data.ucar.edu> cc: Paula Freeman <address@hidden>, Brent Gordon <address@hidden>, address@hidden Subject: Re: "pbuf_flush: time elapsed" problem Steve...a few clarifications, > > On Oct 18, 2005, at 5:06 PM, Steve Emmerson wrote: >> >> I assume that when you say "our NEXRAD2 feed" that you mean the >> UPSTREAM >> LDM process that's sending NEXRAD2 data-products. Please tell me if >> this assumption is incorrect. > Actually I was wrong in my earlier email, we are talking about the downstream ldm that is placing NEXRAD2 into our product queue. The process that is getting data from the upstream LDM server is what is hanging. > The LDM system that feeds us is restarted twice a day, that's why > there is a connection failure ~14:15. At 14:54 I sent the 1228948 > process a USR2 to go into verbose mode, once data stopped being > received by the upstream LDM we attached truss. > > Again, this only seems to happen when the upstream ldm is in verbose > mode. This process ran for 5 days in silent mode with no problems but > stopped after 3 hours once it was put into verbose. Here when I refer to the "upstream ldm" I should have been saying "downstream ldm", I was confused on the terminology of what processes are considered upstream or downstream. Since we do not send products to any other machine through LDM I considered all processes to be upstream since that is where they are receiving data from. I didn't consider the processes actually putting products into the queue on our machine to be downstream. But they actually are. Hopefully this is clear... Justin ------- End of Original Message
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.