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.
>From: Carl Drews <address@hidden> >Organization: NCAR/RAL >Keywords: 200502111625.j1BGPOv2029002 LDM log files Hi Carl, >I am getting a log file, but I can't seem to rotate the logs by hand: > >. >. >. >-rw-rw-r-- 1 ldm 10012 992 Feb 11 13:59 2005021113.stats >-rw-rw-r-- 1 ldm 10012 992 Feb 11 14:59 2005021114.stats >-rw-rw-r-- 1 ldm 10012 992 Feb 11 16:01 2005021115.stats >-rw-rw-r-- 1 ldm 10012 992 Feb 11 16:23 2005021116.stats >-rw-rw-r-- 1 ldm 10012 1119201 Feb 11 16:22 ldm-mcidas.log >-rw-rw-r-- 1 ldm 4dwx 285907 Feb 10 00:21 ldm5.restarts >-rw-rw-r-- 1 ldm 10012 0 Feb 11 00:07 ldmd.log >-rw-rw-r-- 1 ldm 10012 8694 Feb 11 13:10 pqact.log >4dwx-ingest-atec:ldm> ldmadmin newlog >hupsyslog: kill -HUP 21545: Permission denied This looks to me like your LDM installation did not include the last step where the two processes 'rpc.ldmd' and 'hupsyslog' were changed to be owned by 'root' and setuid 'root'. For reference, that step is: <as 'root'> cd ~ldm/ldm-6.2.0/src <- assuming that you are using 6.2.0 make install_setuids >4dwx-ingest-atec:ldm> pwd >/home/ldm/logs >4dwx-ingest-atec:ldm> > >Do you know what might be wrong here? This is a problem with the permissions on hupsyslog. The solution is what I outlined above. >Carl Drews >RAL/NCAR Cheers, Tom -- 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.