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

[LDM #POI-149293]: LDM log rollover

James,

The "ldmadmin newlog" command is known to work, so something's amiss.

Would you please become the LDM user in their home-directory and send us the 
output from the command

    ls -l bin/refresh_logging && cat bin/refresh_logging

> With the LDM no longer using syslogd, we're trying to get the log rollover
> feature to work. However, it's not working for us.
> 
> ldm@llwxldm2new[227]: ls -l
> 
> total 328
> 
> -rw-------. 1 ldm ldm 335461 Jan 30 20:13 ldmNexrad.log
> 
> ldm@llwxldm2new[228]: ldmadmin newlog
> 
> ldm@llwxldm2new[229]: ls -l
> 
> total 448
> -rw-------. 1 ldm ldm      0 Jan 30 20:13 ldmNexrad.log
> -rw-------. 1 ldm ldm 456926 Jan 30 20:13 ldmNexrad.log.1
> 
> <snip>
> 
> ldm@llwxldm2new[235]: ls -l
> 
> total 4500
> -rw-------. 1 ldm ldm       0 Jan 30 20:13 ldmNexrad.log
> -rw-------. 1 ldm ldm 4606955 Jan 30 20:27 ldmNexrad.log.1
> 
> Notice how a new log file is created but never grows. And here are a
> couple of entries from the Registry:
> 
> ldm@llwxldm2new[239]: regutil /log/count
> 
> 1000
> 
> ldm@llwxldm2new[240]: regutil /log/file
> 
> /opt/ldm/var/logs/ldmNexrad.log
> 
> From what I know of Unix inodes, I'm not surprised by this. It looks like
> the LDM software has not released the inode of the first log file. But I
> suppose the newlog command has a way around this in normal circumstances.
> 
> Any advice would be appreciated.
> 
> By the way, this is LDM 6.13.6.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: POI-149293
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.