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

20000516: ldm won't write data or logs (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: 20000516: ldm won't write data or logs (cont.)
  • Date: Tue, 16 May 2000 17:06:31 -0600
>From: Mike Trexler <address@hidden>
>Organization: NCSU
>Keywords: 200005161729.e4GHTY416404 LDM log syslogd

Mike,

>Thanks for the help.  It, of course, was a simple error in my pqact file
>that prevented the data from being written.

It is always the simple problems that are easy to get tripped up on :-(

>I should have used pqactcheck before I can whinny to you.  Sorry.

No problem.

>About the log files, though, I am running on Solaris and I had my sys
>admin restart syslogd and here's what she sent me:

>******
>Hi Mike,
>
>I've HUP'ped the syslogd, that should kick start it.
>
>sol.ncsc.org:/home/carole/Tests% tail -1 /var/adm/messages
>May 16 16:20:58 sol.ncsc.org syslogd: configuration restart
>sol.ncsc.org:/home/carole/Tests%
>
>Let me know if that worked or not.
>
>Thanks, CAROLE
>******

>Even after, I restarted the ldm and still no log.  Any other ideas?

She should stop and restart syslogd.  A HUP won't do what is needed since
it is most likely wedged.  Again, you should:

o stop the LDM
o stop and restart syslogd
o restart the LDM

Before the LDM restart, just to make sure, verify that ~ldm/logs/ldmd.log
is writable by the user that runs the LDM.

>thanks again,

You are welcome.

>Mike

Tom