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

19991011: LDM log file problem

>From: "Jason J. Levit" <address@hidden>
>Organization: Center for Analysis and Prediction of Storms, University of Okla
homa
>Keywords: 199910111619.KAA28000 LDM syslog

Jason,

>Recently, my LDM distribution stopped producing a log file.  No changes
>to the system have occured, and whenever I type a "ldmadmin newlog", the
>program executes but no new log is generated.  For some reason, the log
>files have just randomly stopped!!  Could you possibly give me some 
>pointers on where to start looking for the problem?  As I mentioned, no
>changes to the system have occured and it has just suddenly stopped 
>working.  I tried this:
>
>ldmadmin stop
>ldmadmin delqueue
>ldmadmin mkqueue
>ldmadmin start
>ldmadmin newlog
>
>  ....without any success.  LDM itself appears to be running correctly.
>
>  I'm running ldm-5.0.6 on a Sun Enterprise server, running SunOS 5.5.1.
>
>  Thanks for any help!

The question I have is whether or not a blank ldmd.log is created or if
logging into the new file fails.  If the problem is the latter, then
the cause is most likely syslogd.  Sun has known problems with syslogd:
sometimes it stops running; sometimes it stops logging into the LDM's
log file.  The solution in this case is to stop and restart syslogd
as 'root'.

To test out whether or not the failure is one of making a new output
LDM log file, try:

ldmadmin stop
ldmadmin newlog

If ~ldm/logs/ldmd.log is created (after renaming ldmd.log to ldmd.log.1, etc.)
then I would bet that your problem is in syslogd.  If the new log file is
not created, then I would check the write permissions on the ~ldm/logs
directory.  Typically, this is a link to some other file system, so it
is possible that the file system got remounted without the necessary write
permissions for the user running the LDM.

Tom Yoksas