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

20030518: LDM not logging on Sun Solaris 5.8

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: 20030518: LDM not logging on Sun Solaris 5.8
  • Date: Mon, 19 May 2003 07:53:57 -0600
>From: Chris Novy - Systems <address@hidden>
>Organization: SIU
>Keywords: 200305160023.h4G0NBLd007554 LDM-6 ldmadmin stop

Hi Chris,

>Is there any reason you can think of why there's nothing in my ldmd.log
>file?   Doing a tail command shows no activity.  Is it possible I
>corrupted the log file somehow and LDM can't write to it?

Corruption of the log file is not likely.  Each time the LDM is stopped
and restarted the log file ~ldm/logs/ldmd.log moved to a new name
(rotated) and a new one gets created.

What is more likely is necessary LDM entries in /etc/syslog.conf
are not setup/not setup correctly.

Was logging working?  If yes, then did you change anything in
/etc/syslog.conf?  If no, is syslogd running?  Did you ever
setup /etc/syslog.conf to support logging?

I am betting that syslogd is not running.  syslogd exiting is a known
bug on Sun Solaris for which there have been patches issued.  If
syslogd is not running, you will need to restart it as 'root':

/usr/sbin/syslogd

If syslogd _is_ running, then it might be wedged.  In this case
you will have to stop and restart it as 'root'.

Please let us know if your problem is not related to syslogd.

Cheers,

Tom