[LDM #RSJ-676480]: pqinsert and pqcheck segfaults

John,

[I copied your "ldm-users" email into our support-email system.]

The error you saw was due to the failure of a sanity-check of the product-queue
when it's opened. This should not have occurred.

Was any other process simultaneously accessing the product-queue? Was the LDM
running or was it stopped? Was a crontab(1) entry accessing the queue?

Did something happen that could have corrupted the queue? Did the computer
crash? Did the power go out?

In order for the LDM system to continue, the product-queue will have to be
re-created.

> I’m now getting seg faults on both an older build and a fresh compile of
> LDM (6.13.5 and 6.12.14).
> 
> This all worked before I had to rebuild my system from scratch (Ubuntu
> 16.04 LTS)
> 
> All compilation and configuration seems to work fine.
> 
> Output of gdb:
> 
> Reading symbols from ./pqcheck...done.
> (gdb) run
> Starting program: /home/ldm/ldm-6.13.5/bin/pqcheck
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> 20161103T142135.640016Z pqcheck[16469] NOTE pqcheck.c:150:main() Starting
> Up (16469)
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff7b799d7 in ctl_gopen (
> path=0x7ffff7dd47a0 <queuePath> "/home/ldm/var/queues/ldm.pq",
> pq=0x616440)
> at pq.c:4744
> 4744            if (!(pq->rlp->nalloc == pq->nalloc && pq->tqp->nalloc ==
> pq->nalloc

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: RSJ-676480
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.