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.
The performance of the product-queue should scale as the inverse of the log of the number of slots. Try a large number and see. Steve Emmerson (sent from my phone) On Apr 30, 2016 16:06, "Robert Much" <address@hidden> wrote: > New Client Reply: Queue Product Slots > > Steve, > I can certainly try the beta version. Any thoughts regarding the > workaround solution? Would there be a sensible number of queue slots to > set that might avoid the error? Does a set number of slots (say 500,000) > have an adverse affect on LDM performance, etc.? > > Bob > > ________________________________________ > From: Unidata LDM Support [address@hidden] > Sent: Saturday, April 30, 2016 2:08 PM > To: Robert Much > Cc: address@hidden > Subject: [LDM #SYX-505877]: Queue Product Slots > > Robert, > > The problem you're encountering might be fixed in a beta version of the > LDM that has yet to be released. That version has been and is being > successfully tested here and at another site. You are welcome to try it. > The URL is > > > http://cp.mcafee.com/d/1jWVIe4zqb3ytSjhOejsdTdIIczxNEVvvdLzCm6kjhOqejqdTHLe6zCVEVudLzCm7D4nzsqAfzfBmX4MkGxHtendGEqTjBPvWMWMCevW_8ILfcnuWZOWrb5-jspspuLORQr8EGEEFYG7DR8OJMddECQjt-hojuv78I9CzATsSXdpbctCJPs98rfurJIuZ1L5CO67EaUg-uUuwGnsV5DHYPQZzN4kdQrmmH6psZ1k5dMAxIZVKSNXQ6Pr5QTPpFr2EsdCy031w3wcnvK-Ye76BR8Qg0eTXvCy0bhGwTqpEw63WPErpudDCQq > > The main difference that you would encounter is logging: your version uses > the system logging daemon and, by default, the new version doesn't. > Instead, logging occurs directly to the log file. This change should be > transparent. You'll find, however, that the format of a log message is > slightly different: it will have increased time precision and indicate > where in the source-code the message was generated. > > Please feel free to contact me if you have any questions. > > > The version is 6.12.6. This communication can be public. The "ldmadmin > config" output: > > > > hostname: ec2-52-0-8-214.compute-1.amazonaws.com > > os: Linux > > release: 3.13.0-45-generic > > ldmhome: /usr/local/ldm > > LDM version: 6.12.6 > > PATH: > /usr/local/ldm/ldm-6.12.6/bin:/usr/local/ldm/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games > > LDM conf file: /usr/local/ldm/etc/ldmd.conf > > pqact(1) conf file: /usr/local/ldm/etc/pqact.conf > > scour(1) conf file: /usr/local/ldm/etc/scour.conf > > product queue: /run/shm/ldm.pq > > queue size: 4G bytes > > queue slots: default > > reconciliation mode: decrease maximum latency > > pqsurf(1) path: /usr/local/ldm/var/queues/pqsurf.pq > > pqsurf(1) size: 2M > > IP address: 0.0.0.0 > > port: 388 > > PID file: /usr/local/ldm/ldmd.pid > > Lock file: /usr/local/ldm/.ldmadmin.lck > > maximum clients: 256 > > maximum latency: 3600 > > time offset: 3600 > > log file: /var/log/ldm/ldm.log > > numlogs: 7 > > log_rotate: 1 > > netstat: /bin/netstat -A inet -t -n > > top: /usr/bin/top -b -n 1 > > metrics file: /var/log/ldm/metrics.txt > > metrics files: /var/log/ldm/metrics.txt* > > num_metrics: 4 > > check time: 1 > > delete info files: 0 > > ntpdate(1): /usr/sbin/ntpdate > > ntpdate(1) timeout: 5 > > time servers: ntp.ucsd.edu ntp1.cs.wisc.edu ntppub.tamu.edu > otc1.psu.edu timeserver.unidata.ucar.edu > > time-offset limit: 10 > > Regards, > Steve Emmerson > > Ticket Details > =================== > Ticket ID: SYX-505877 > Department: Support LDM > Priority: Normal > Status: Closed > > > > The information contained in this communication is confidential, is > intended only for the use of the recipient(s) named above, and may be > legally privileged. If the reader of this message is not the intended > recipient, you are hereby notified that any dissemination, distribution, or > copying of this communication is strictly prohibited. If you have received > this communication in error, please re-send this communication to the > sender and delete the original message or any copy of it from your computer > system. > > > > Ticket Details > =================== > Ticket ID: SYX-505877 > Department: Support LDM > Priority: Normal > Status: Open > Link: > https://andy.unidata.ucar.edu/esupport/staff/index.php?_m=tickets&_a=viewticket&ticketid=26988 > > Ticket Details =================== Ticket ID: SYX-505877 Department: Support LDM Priority: Normal Status: Open