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

Re: 20001116: IDD delivery of Unidata-Wisconsin imagery for 11/10- 11/13

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: Re: 20001116: IDD delivery of Unidata-Wisconsin imagery for 11/10- 11/13
  • Date: Mon, 20 Nov 2000 14:36:20 -0700
"Arthur A. Person" wrote:
> 
> Anne,
> 
> On Mon, 20 Nov 2000, Anne Wilson wrote:
> 
> > I understand that you found no abberations in your ldm log, but I'd like
> > to take a look at the log just the same - do you still have it?
> 
> Actually, I was never able to look at an ldm log because it had already
> been purged by the time I knew of this problem.  What I learned was from
> looking at system logs and email.  I should probably set the ldm system to
> keep more/longer logs for these purposes.
> 
> > I've discussed this with Tom and Russ.  The ldm is programmed to discontinue
> > an unsuccessful RPC after a short period of time, probably a minute or
> > so, then reestablish the connection.  I don't know what went wrong in
> > this case.  Our main top tier machine, motherlode, handled the
> > disconnect just fine.
> 
> Seems strange to me, too, since I don't recall having problems like this
> before either.
> 
> > I understand that back in the early days of version 5 things like this
> > would happen, but those problems were apparently fixed.  We haven't seen
> > anything like this for at least a year (as long as I've been here), if
> > not several years.  Other than looking at the logs, at this point I
> > would just wait and see if it happens again.
> >
> > For the record, what version of the ldm are you running?  What hardware
> > and OS are you using?
> 
> We run the ldm on a Sun Enterpise 2 dual processor with Solaris 2.7.  The
> ldm version is 5.1.2.  I guess I'll try and increase the number of logs
> kept... I think that's a configuration in ldmadmin or something...
> correct?
> 

Hi Art,

Yes, there's a configuration section in ldmadmin.  The number of logs is set to 
4 by default.  But, you decide if it's really worthwhile to keep more logs - 
the vast majority of the time 4 seems to be plenty.   If this is truly only an 
aberration, then ... it won't happen again! :)   If it does happen again and 
you aren't able to stash the appropriate log then I would be more inclined to 
suggest increasing the number of logs.

Anne


> Arthur A. Person
> Research Assistant, System Administrator
> Penn State Department of Meteorology
> email:  address@hidden, phone:  814-863-1563

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