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.
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: address@hidden > 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