Jeff, > It seems as if this rears its head every time I update 6.9.x > > from starting 6.9.8 > > -bash-3.2$ ldmadmin stop > Stopping the LDM server... > Waiting for the LDM server to terminate... > -bash-3.2$ rm runtime > -bash-3.2$ ln -s ldm-6.9.8 runtime > -bash-3.2$ ldmadmin start > The self-consistency of the product-queue couldn't be determined. > See the logfile for details. > LDM not started > -bash-3.2$ rm runtime > -bash-3.2$ ln -s ldm-6.9.7 runtime > -bash-3.2$ ldmadmin start > The product-queue is OK. > Checking pqact(1) configuration-file(s)... > /usr/local/ldm/etc/pqact.conf: syntactically correct > Checking LDM configuration-file (/usr/local/ldm/etc/ldmd.conf)... > Starting the LDM server... > -bash-3.2$ > > from the LDM log > > Jun 14 21:02:29 feeds3 pqcheck[7708] NOTE: Starting Up (7670) > Jun 14 21:02:29 feeds3 pqcheck[7708] ERROR: mmap: (nil) 0 4075618304: Cannot > allocate memory > Jun 14 21:02:29 feeds3 pqcheck[7708] ERROR: pq_get_write_count() failure: > /usr/local/ldm/var/queues/ldm.pq: Cannot allocate memory > Jun 14 21:02:29 feeds3 pqcheck[7708] NOTE: Exiting > Jun 14 21:03:14 feeds3 pqcheck[7820] NOTE: Starting Up (7780) > Jun 14 21:03:14 feeds3 pqcheck[7820] NOTE: Exiting Wow! An mmap(3) system-call error. That should not happen. What happens with a queue that's half the size? (Delete and remake the queue.) > Jeff Lake K8JSL > http://www.MichiganWxSystem.com > https://www.TheWeatherCenter.net Regards, Steve Emmerson Ticket Details =================== Ticket ID: DNN-647229 Department: Support LDM Priority: Normal Status: Closed