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

[LDM #ORR-654962]: ldmadmin newlog

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: [LDM #ORR-654962]: ldmadmin newlog
  • Date: Fri, 21 Feb 2020 09:54:53 -0700
Michael,

We have had the problem since upgrading some systems from RHEL6 to
> RHEL7. Below is the newlog and refresh_logging info.
>
> The command: "command kill -s USR1 -- -`cat $HOME/ldmd.pid`" did not
> start logging to the new, empty log file.
>
> The command: "kill -s USR1 -- -`cat $HOME/ldmd.pid`" did start logging
> to the new, empty log file, correctly.
>

I thought that was impossible, but apparently not.

I think you identified the problem, which is the location of the
> ldmd.pid file or the LDMHOME env setting.
>

I believe the solution has two parts:

   1. Replace "command kill" in the refresh_logging(1) utility with
   "/bin/kill". This change will be in the next release.
   2. Ensure that the LDMHOME environment variable has the value
   "/usr1/ldm".

> Should the LDMHOME env variable be set to /usr1/ldm/ldm-6.13.11?

Definitely not! The LDMHOME variable, in your case, should be "/usr1/ldm".

Regards,
Steve Emmerson
LDM developer



Ticket Details
===================
Ticket ID: ORR-654962
Department: Support LDM
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.