[LDM #FST-256974]: updating to latest ldm version causes hanging

Hi,

> I updated to 6.13.11 just now, and when I try to run as the ldm user, it
> hangs:
> 
> here is the log:
> 
> 20190814T213621.434835Z ldmd[1855]                  ldmd.c:main:986
> NOTE  Starting Up (version: 6.13.11; built: Aug 14 2019
> 21:18:23)
> 20190814T213621.435078Z ldmd[1855]                  priv.c:rootpriv:44
> ERROR Operation not permitted
> 20190814T213621.435115Z ldmd[1855]                  priv.c:rootpriv:44
> ERROR Couldn't set effective user-ID to root's (0)

The above error-message makes me suspect that the LDM package wasn't installed 
correctly.

What's the output of the command "ls -l $HOME/bin"?

> 20190814T213621.435393Z ldmd[1855]
> ldmd.c:create_ldm_tcp_svc:475       ERROR Permission denied
> 20190814T213621.435427Z ldmd[1855]
> ldmd.c:create_ldm_tcp_svc:475       ERROR Couldn't obtain local address
> 0.0.0.0:388 for server
> 20190814T213621.435473Z ldmd[1855]                  ldmd.c:cleanup:192
> NOTE  Exiting
> 20190814T213621.435553Z ldmd[1855]                  ldmd.c:cleanup:248
> NOTE  Terminating process group
> 20190814T213621.435635Z ldmd[1855]
> semRWLock.c:srwl_deleteByKey:353    ERROR No such file or directory
> 20190814T213621.435666Z ldmd[1855]
> semRWLock.c:srwl_deleteByKey:353    ERROR Couldn't get semaphore set
> 20190814T213621.435695Z ldmd[1855]                  uldb.c:uldb_delete:2047
> ERROR Shared-memory database doesn't exist
> 20190814T213621.435724Z ldmd[1855]                  uldb.c:uldb_delete:2058
> ERROR Semaphore-based read/write lock doesn't exist
> 20190814T213621.435753Z ldmd[1855]                  ldmd.c:cleanup:274
> ERROR Message-queue isn't empty

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: FST-256974
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.