[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #OCY-683651]: pqact crashes

Hi Bob,

Thanks for the info!

Can you send us your LDM configuration file so we can take
a look?  The reason I ask is your comment in a previous email
that your LDM log file is empty.

IMO (Steve may or may not agree), if I were in your position,
I would rebuild and reinstall LDM-6.13.12 from scratch saving
all output into log files.

For instance:

<as 'ldm'>
ldmadmin stop   <- just to be sure
ldmadmin clean  <-       "

cd ~/ldm-6.13.12/src
make distclean
./configure > configure.log 2>&1
make install > makeinstall.log 2>&1

re:
> With 'ldmadmin start' hung in one terminal, this is the output of those 
> commands in another:

Experimentation by us determined that the hanging is not the LDM server,
'ldmd', but, rather, the 'ldmamdin' Perl script.  The 'ps -ef | grep ldmd'
not showing any 'ldmd' process(es) is what we both saw when we removed
the setuid root bit on the 'ldmd' executable.

re:
> [ldm@chs-mets-02-d ~]$ ll
> 
> total 12440
> lrwxrwxrwx. 1 ldm ldm      11 Oct  9 15:50 bin -> runtime/bin
> drwxr-x---. 2 ldm ldm     146 Oct 10 00:03 etc
> drwxr-x---. 2 ldm ldm      80 Oct  9 23:41 etc.bak

Is there some reason you chose to (presumably) rename the existing
~ldm/etc directory to ~ldm/etc.bak?  Was this done as part of your
troubleshooting?

re:
> lrwxrwxrwx. 1 ldm ldm      15 Oct  9 15:50 include -> runtime/include
> drwxr-x---. 7 ldm ldm      67 Oct 10 17:18 ldm-6.13.11
> -rw-r-----. 1 ldm ldm 6287461 May  6  2019 ldm-6.13.11.tar.gz
> drwxr-x---. 7 ldm ldm      67 Oct  9 15:49 ldm-6.13.12
> -rw-r-----. 1 ldm ldm 6440466 Sep 30 16:59 ldm-6.13.12.tar.gz
> -rw-r-----. 1 ldm ldm       0 Oct 10 17:34 ldmd.pid
> lrwxrwxrwx. 1 ldm ldm      11 Oct  9 15:50 lib -> runtime/lib
> lrwxrwxrwx. 1 ldm ldm       8 Oct  9 17:24 logs -> var/logs
> lrwxrwxrwx. 1 ldm ldm      11 Oct 10 17:33 runtime -> ldm-6.13.12
> lrwxrwxrwx. 1 ldm ldm      13 Oct  9 15:50 share -> runtime/share
> lrwxrwxrwx. 1 ldm ldm      11 Oct  9 15:50 src -> runtime/src
> drwxrwxr-x. 2 ldm ldm    4096 Oct  9 17:36 util
> drwxr-x---. 5 ldm ldm      44 Oct  9 15:50 var
> 
> [ldm@chs-mets-02-d ~]$ cat ldmd.pid

This is definitely weird.

re:
> [ldm@chs-mets-02-d ~]$ date
> Sat Oct 10 17:36:23 UTC 2020

Yup, I see that the ldmd.pid file was just created.

re:
> [ldm@chs-mets-02-d ~]$ ps -ef | grep ldmd
> ldm        3816   3495  0 17:37 pts/1    00:00:00 grep --color=auto ldmd

The questions are:

- why did 'ldmd' exit

- why there is no LDM log file output


> [ldm@chs-mets-02-d ~]$
> 
> You can see the empty pid file was just created, and there's no ldmd process
> running.  Interestingly, when I link runtime to ldm-6.13.11, everything works
> as advertised.

This comment is exactly why I suggest building/installing LDM-6.13.12
from scratch.

re:
> Thanks for the support!

No worries.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: OCY-683651
Department: Support LDM
Priority: Normal
Status: Open
===================
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.