[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Support #LSJ-519536]: LDM log rotation
- To: Ryan.L.Solomon@xxxxxxxx
- Subject: [Support #LSJ-519536]: LDM log rotation
- From: "Unidata LDM Support" <support-ldm@xxxxxxxxxxxxxxxx>
- Date: Fri, 11 Apr 2008 15:51:05 -0600
- Delivered-to: support-ldm@unidata.ucar.edu by laraine.unidata.ucar.edu (Postfix) with ESMTP id EE8BECB19B; Fri, 11 Apr 2008 15:51:05 -0600 (MDT) id C7295D4FBA; Fri, 11 Apr 2008 15:51:05 -0600 (MDT)
Ryan,
> We're experiencing a problem with our LDM log files. I set up the cron
> the way the documentation describes ("ldmadmin newlog") but it doesn't
> work. It renames the current log to a file with a numerical sequence
> extension (i.e., ldmd.log.1) and creates a new ldmd.log file (all is
> well so far). But nothing gets written to the new file. Instead, the
> log messages continue to be written to the first log file (which is now
> called ldmd.log.1). I've tried it on our RHEL3, RHEL4, and Solaris 8
> systems, all with the same results.
>
> Any ideas?
Is the system logging daemon running? Try the command "ps -ef |
grep syslog".
Is the "hupsyslog" utility owned by root and setuid? Try the command
"ls -l bin/hupsyslog"
Is SELINUX disabled? Try the command "fgrep SELINUX /etc/selinux/config".
> Thanks.
>
> --
> ---------------------------------------
> Ryan Solomon
> Techniques Development Meteorologist
> Aviation Weather Center (NOAA/NWS/NCEP)
> 7220 NW 101st Terrace, Room 101
> Kansas City, MO 64153-2371
>
> Email: Ryan.L.Solomon@xxxxxxxx
> Phone: 816.584.7251
> URL: http://aviationweather.gov/
> ---------------------------------------
Regards,
Steve Emmerson
Ticket Details
===================
Ticket ID: LSJ-519536
Department: Support LDM
Priority: Normal
Status: On Hold
