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

19991015: LDM log file problem (cont.)

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: 19991015: LDM log file problem (cont.)
  • Date: Fri, 15 Oct 1999 10:42:37 -0600
>From: "Jason J. Levit" <address@hidden>
>Organization: Center for Analysis and Prediction of Storms, University of Okla
homa
>Keywords: 199910111619.KAA28000 LDM syslog

Jason,

>The system administrator was able to restart syslogd from afar, and 
>I tried: 
>
>  ldmadmin stop
>  ldmadmin newlog
>  ldmadmin start
>
>  ....but nothing happened.  Nothing is being generated in the log file,
>though when I put junk into ldmd.log, it *does* rotate the logs - it
>just doesn't put anything into the file.
>
>  Any suggestions on what to try from here?  Thanks for your insights.

This is _still_ a syslogd problem.  This is bourne out by the fact that
/var/adm/messages has not been updated since October 9:

ldm@dot% ls -l messages*
-rw-r--r--   1 root     other          0 Oct  9 04:05 messages
-rw-r--r--   1 root     other       7447 Oct  3 23:14 messages.0
-rw-r--r--   1 root     other    18098766 Oct  3 23:14 messages.1
-rw-r--r--   1 root     other    18307692 Sep 25 04:05 messages.2

I tried sending a HUP to syslogd (by running 'hupsyslog' as 'ldm'),
but saw no changes.

My only recommendation now is to try rebooting.

Tom