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

[IDD #RDQ-217349]: IDD/LDM startup problem, no data, no log

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: [IDD #RDQ-217349]: IDD/LDM startup problem, no data, no log
  • Date: Thu, 24 Apr 2008 16:27:51 -0600
Mike,

The following output:

bash-2.03$ grep LOG $HOME/src/config/ldmconfig.h
...
#define LOG_LDM LOG_LOCAL0

indicates that your LDM will use the "local0" facility for
logging.  According to this entry in your "/etc/syslog.conf"
file:

local0.debug            /var/log/tcplog

LDM log messages will be appended to the file "/var/log/tcplog" --
which is probably not what you want.

LDM log messages will also be appended to the file "/var/adm/messages"
because "local0.none" isn't in this entry in "/etc/syslog.conf:

*.err;kern.debug;daemon.notice;mail.crit;local1.none    /var/adm/messages

Assuming that you want to use the "local1" facility for LDM
logging (rather than the default "local0") then you must do the
following: 1) re-execute the "configure" script with the option
"--enable-logging=local1"; and 2) rebuild and re-install the LDM
package.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: RDQ-217349
Department: Support LDM
Priority: Normal
Status: Closed