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.
Wen, > When I started ldm, it displays message as below: > > ldm@fujita:~/etc> ../bin/ldmadmin start > WARNING: The checking of the system clock is disabled. You might > loose data if the clock is off. To enable this checking, > set the variable "$check_time" to 1 in the configuration-file, > /home/ldm/etc/ldmadmin-pl.conf. > The product-queue is OK. > Checking pqact(1) configuration-file(s)... > etc/pqact.gempak: syntactically correct > Shutting down syslog services > done > Starting syslog services > done > Checking LDM configuration-file (/home/ldm/etc/ldmd.conf)... > Starting the LDM server... > > It seems syslog works. Now when ldm starts, a new version of ldmd.log is > generated. The contents is copied here: > > ldm@fujita:~/etc> more ../logs/ldmd.log > Jul 20 15:34:55 fujita rpc.ldmd[391] NOTE: Starting Up (version: 6.8.1; > built: Apr 30 2010 10:07:37) > Jul 20 15:34:55 fujita rpc.ldmd[391] NOTE: Using local address 0.0.0.0:388 > Jul 20 15:34:55 fujita pqact[393] NOTE: Starting Up > Jul 20 15:34:55 fujita rtstats[394] NOTE: Starting Up (391) > Jul 20 15:34:55 fujita pqact[393] WARN: No such file or directory > Jul 20 15:34:55 fujita pqact[393] WARN: stateRead(): Couldn't open > "etc/pqact.gempak.state" > Jul 20 15:34:55 fujita pqact[393] WARN: Previous-state information doesn't > exist. Continuing... > Jul 20 15:35:10 fujita pqact[393] NOTE: child 395 exited with status 126 > (decoders/dcnldn-m25000-b30-sminute05-ddata/gempak/logs/dcnldn.log-eGEMTBL=/home/gempak/GEMPAK5.11.4/gempak/tablesdata/gempak/nldn/YYYYMMDDHHNN_nldn.gem) > > Thanks for your time to check the messages, I don't see any "Starting Up" messages from any downstream LDM-s. Do you have any REQUEST entries in your LDM configuration-file (typically "etc/ldmd.conf")? Are you following the instructions for configuring an LDM system at <http://www.unidata.ucar.edu/software/ldm/ldm-current/basics/configuring.html>? Regards, Steve Emmerson Ticket Details =================== Ticket ID: CIB-153307 Department: Support LDM Priority: High Status: Closed