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.
Trent, First off, it looks like the path of the LDM product-queue file in your boot-time script differs from the path that the LDM system uses. Please send me the output of the command "ls -l $HOME/bin", executed by the LDM user. The files "hupsyslog" and "ldmd" should be owned by "root" and setuid. > I've done the setuid, see below, > > chmod u+srwx,g+rx,o+rx hupsyslog > > > But, I still see the following when starting ldmd > > [root@netrs-sgpc1 bin]# service ldmd start > Starting LDM (/home/ldm/ldm-6.10.1/bin/rpc.ldmd) via boot script. > /home/ldm/ldm-6.10.1/data/ldm.pq does not exist, making new queue. > pqcreate: create "/home/ldm/var/queues/ldm.pq" failed: File exists > make_pq(): mkqueue(1) failed > The product-queue is OK. > Checking pqact(1) configuration-file(s)... > /home/ldm/etc/pqact.conf: syntactically correct > hupsyslog: kill -HUP 1621: Permission denied > new_log(): Couldn't notify system logging daemon > start_ldm(): Couldn't rotate log files > > I don't understand the error on the logging daemon. We don't use syslog, > rather we use rsyslog. I've checked the config, it looks ok. > > I know that ldm doesn't own the pid of rsyslog, how can I fix this? > > Thanks, > > -- Trent Doyle > Systems Admin. III > Southern Great Plains > Office: 580-388-4053 Regards, Steve Emmerson Ticket Details =================== Ticket ID: KTG-709466 Department: Support LDM Priority: Normal Status: Closed