Gerry, [Please pass this on to John.] > > I restarted LDM. When starting up, it had a problem with the counter, > > and wouldn't start (this is quite common in my experience). If that is the case, the the LDM was not stopped cleanly. If and "ldmadmin start" command indicates that the writer-counter of the product-queue is not zero and no other LDM is running, then you should recreate the product-queue before starting the LDM. > > I created > > a new product queue from scratch (because reseting the counter > > sometimes seems to leave the queue in a corrupt state, which causes > > problems further down the line). And the files started flowing again... > > > > There were no errors in the ldmd.log for Florida. > > > > Anybody got any tips they'd like to share about how to spot that feeds > > have stopped of their own accord? Or should I restart LDM periodically? Downstream LDM processes are very persistent in their attempts to obtain data-products from an upstream LDM (they will, for example, retry every minute until they are serviced). One way to see this is to put the relevant downstream LDM into verbose logging mode (via a "kill -USR2" command) and check the log file. In our experience, the overwhelming majority of data-reception problems of this nature are caused by the data-products simply not being injected into the LDM network. I am very interested in evidence to the contrary. Please feel free to contact me. Regards, Steve Emmerson Ticket Details =================== Ticket ID: YQU-684227 Department: Support IDD SCOOP Priority: Normal Status: Closed
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.