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

Re: 20010727: Problem getting ldmd.log created

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: 20010727: Problem getting ldmd.log created
  • Date: Fri, 27 Jul 2001 20:44:42 -0600
Unidata Support wrote:
> 
> ------- Forwarded Message
> 
> >To: address@hidden
> >From: James Murakami <address@hidden>
> >Subject: Problem getting ldmd.log created
> >Organization: UCAR/Unidata
> >Keywords: 200107272140.f6RLex112564
> 
> Hi,
> 
> I'm having a problem getting the "ldmd.log" files to
> be created. The problem started when I was installing
> GEMPAK5.6c1. In the process of clearing space, I may
> have accidentally removed then existing "ldmd.log"
> file. In any case, nothing new is created when I
> restart (that is stop, then start) ldmadmin. Even
> when deleting and making a new queue (delqueue and
> mkqueue), no update is generated.
> 
> I haven't changed anything, directory-wise with
> the bin directory (where the ldmadmin program resides--
> /home/ldm/bin). All had been well prior to this. If
> I did alter some file, I don't recall what the crucial
> file could have been.
> 
> Since, I'm not a programmer, you'll have to instruct
> things in a little more in detail.
> 
> Thank you in advance.
> 
> James
> 
> --------------------------------------
> James Murakami
> Staff Meteorologist/Student Affairs
> Department of Atmospheric Sciences
> University of California, Los Angeles
> 405 Hilgard Ave.
> Los Angeles, CA  90095-1565
> 
>    e-mail:  address@hidden
> telephone:  310-825-2418
>       Fax:  310-206-5219
> ---------------------------------------
> 
> ------- End of Forwarded Message

Hi James,

The file ~ldm/logs/ldmd.log must exist before the syslog daemon will
write to it - it will not be created for you.  If you inadvertently
deleted it then you must create it again.  Do 'touch ~ldm/logs/ldmd.log'
to create a 0 length file.  From there, the syslog daemon will take over
and write messages to the file.

Try this, and let me know if this fixes your problem or not.

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