[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

aeolus update

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.

  • Subject: aeolus update
  • Date: Tue, 05 Feb 2002 20:52:08 -0700
Hi all,

In an earlier message I said I planned to rebuild the queue on aeolus. 
Well, I've decided not to.  Things have been running properly for about
two hours now.  So, instead of rebuilding the queue I've put the
rpc.ldmd process for motherlode in debug mode in anticipation of the
problem occurring again.  I'm rotating the logs every 30 minutes, so the
logs shouldn't grow too huge.  I'm keeping a bunch of them to cover the
time until the morning.  Disk space seems sufficient for this.

Larry, should the ldm die I'd suggest letting it be until we can look at
it again in the morning.  

But, if you must restart it, please save ~ldm/logs/ldmd.log, i.e.,
rename it with some other name.  Then, you'll need to 'touch
~ldm/logs/ldmd.log' to get logging working again.  Also, it might be
interesting to save the queue if you can.  You only need to rename it to
some other name, then do 'ldmadmin mkqueue' to make another one.

I'll check things once more tonight, then again in the AM.

Anne

-- 
***************************************************
Anne Wilson                     UCAR Unidata Program            
address@hidden                  P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************