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

20020613: ldmd.log after OSF upgrade?

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: 20020613: ldmd.log after OSF upgrade?
  • Date: Thu, 13 Jun 2002 11:38:30 -0600
>From: "Neil R. Smith" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200206131717.g5DHH1J17911

>Hi folks,
>I'm running ldm 5.1.2 for our NNEXRAD ingest on a
>Compaq Alpha DS20E. I just upgraded the OS from
>5.0A to 5.1A and now the ~ldm/logs/ldmd.log is
>neither being initialized nor written too. Was
>there a system executable that got moved between
>the OS versions? The ldm config and install location
>did not change. I looked in ~/bin/ldmadmin for
>suspicious system file references and didn't
>see anything threatening. Any ideas?
>Thanks, -Neil
>PS: I AM getting data ingest and correct file
>    output as before (as far as I can tell).
>
>---
>Neil R. Smith, Comp. Sys. Mngr.         address@hidden
>Dept. Atmospheric Sci., Texas A&M Univ. 979/845-6272 
>
>


Neil,

LDM logging is done through the local0 service, Your entries in
/etc/syslog.conf may have been overwritten by your OS upgrade.

See the LDM installation instructions for configuring logging though
syslog.conf.

Steve Chiswell