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.
Daryl, > Here's the result of trying to start LDM after the system crashed. The > system is a fully patched RHEL6 64bit system. I rebuilt the queue and it > is running fine now. > > thanks, > daryl > > [ldm@chinook ~]$ ldmadmin stop > Stopping the LDM server... > kill 18175: No such process > [ldm@chinook ~]$ ldmadmin start > The product-queue is OK. > Checking pqact(1) configuration-file(s)... > /local/ldm/etc/pqact.conf: syntactically correct > Checking LDM configuration-file (/local/ldm/etc/ldmd.conf)... > Starting the LDM server... > [ldm@chinook ~]$ > [ldm@chinook ~]$ ldmadmin tail > May 9 10:55:55 chinook pqact[26064] WARN: Previous-state information > doesn't exist. Continuing... > May 9 10:56:24 chinook mtarchive-priv.geol.iastate.edu[26070] NOTE: > Data-product with signature 2bdc512445f7a2493b66880615ace748 wasn't found > in product-queue > May 9 10:56:24 chinook mtarchive-priv.geol.iastate.edu([26070] NOTE: > Starting Up(6.9.7/6): 20110509145624.033 TS_ENDT {{EXP, ".*"}}, > SIG=2bdc512445f7a2493b66880615ace748, Primary > May 9 10:56:24 chinook mtarchive-priv.geol.iastate.edu([26070] NOTE: > topo: mtarchive-priv.geol.iastate.edu {{EXP, (.*)}} > May 9 10:56:27 chinook mtarchive-priv.geol.iastate.edu([26070] ERROR: > assertion "info->sz <= xdrs->x_handy" failed: file "pq.c", line 6698 > May 9 10:56:27 chinook ldmd[26062] NOTE: child 26070 terminated by signal > 6 > May 9 10:56:27 chinook ldmd[26062] NOTE: Killing (SIGTERM) process group > May 9 10:56:27 chinook ldmd[26062] NOTE: Exiting > May 9 10:56:27 chinook pqact[26064] NOTE: Exiting > May 9 10:56:27 chinook ldmd[26062] NOTE: Terminating process group Well, that never should have happened. Could your product-queue have become corrupted somehow? Was anything untoward happening on the system just before this occurred? Have you had any other problems with the disk that contains the product-queue? Any memory problems? Regards, Steve Emmerson Ticket Details =================== Ticket ID: XLL-812744 Department: Support LDM Priority: Normal Status: Closed