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.
Manuel, > I execute expire and it doesn't expire anything. I run pqmon so you can > see the old product is still there: > > ldm@tigge-ldm:~/etc> pqexpire -vl- -i 0 -a 86400 > Nov 02 17:51:03 pqexpire[15626] NOTE: Starting Up > Nov 02 17:51:03 pqexpire[15626] NOTE: Exiting > Nov 02 17:51:03 pqexpire[15626] NOTE: > Up since: 20061102175103.669 > Nov 02 17:51:03 pqexpire[15626] NOTE: > Queue usage (bytes):4000002048 > Nov 02 17:51:03 pqexpire[15626] NOTE: > (nregions): 82186 > Nov 02 17:51:03 pqexpire[15626] NOTE: > nprods deleted 0 > ldm@tigge-ldm:~/etc> > ldm@tigge-ldm:~/etc> pqmon > Nov 02 17:51:51 pqmon NOTE: Starting Up (15755) > Nov 02 17:51:51 pqmon NOTE: nprods nfree nempty nbytes maxprods > maxfree minempty maxext age > Nov 02 17:51:51 pqmon NOTE: 13398 994 962170 3838888712 82186 > 5094 894302 428144 2692000 > Nov 02 17:51:51 pqmon NOTE: Exiting I suspect that a process has a lock on that old data-product. Do you have the lsof(1) or fuser(1) utility? If so, then use it to discover the set of processes that have the product-queue open. Then, investigate those processes using the ps(1) utility. One of them should be different from the rest because of its age or because it shouldn't be running. When you've identified it, then terminate it. Regards, Steve Emmerson Ticket Details =================== Ticket ID: YZT-357848 Department: Support IDD TIGGE Priority: Normal Status: Closed