[LDM #ORR-654962]: ldmadmin newlog

Hello Michael,

> The "ldmadmin newlog" command is no longer rotating ldmd logs as
> expected. We are using ldm version 6.13.11 on RHEL7.

When did it stop working? What changed then?

> After running ldmadmin newlog, a new ldmd.log file gets created, but the
> logs are still being written to ldmd.log.1 (see below).
> 
> Any suggestions on how to resolve this?
> 
> Thanks,
> Mike
> 
> > [user@host logs]$ ls -altr
> > total 213196
> > drwxrwxr-x. 4 ldm ldm        44 Dec  5 18:14 ..
> > -rw-r--r--. 1 ldm ldm       314 Dec 13 22:18 ldmd.log.7
> > -rw-rw-r--. 1 ldm ldm   7893555 Dec 17 22:22 ldmd.log.6
> > -rw-r--r--. 1 ldm ldm       320 Dec 17 22:22 ldmd.log.5
> > -rw-rw-r--. 1 ldm ldm 167064734 Feb  7 16:56 ldmd.log.4
> > -rw-r--r--. 1 ldm ldm       471 Feb  7 17:15 ldmd.log.3
> > -rw-r--r--. 1 ldm ldm  43063720 Feb 20 18:22 ldmd.log.2
> > -rw-rw-r--. 1 ldm ldm         0 Feb 20 18:57 ldmd.log
> > drwxrwxr-x. 2 ldm ldm       148 Feb 20 18:57 .
> > -rw-r--r--. 1 ldm ldm    202597 Feb 20 19:46 ldmd.log.1
> > [user@host logs]$

Would you please send me the output from the following commands, executed by 
the LDM user:
    cd ~/bin
    ls -l newlog refresh_logging
    cat refresh_logging

Does the following command cause logging to the new, empty log file?
    command kill -s USR1 -- -`cat $HOME/ldmd.pid`

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: ORR-654962
Department: Support LDM
Priority: Normal
Status: Closed
===================
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.