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

[LDM #IPY-349366]: ldmd segfaulting



Hi Don,

re:
> I am in the midst of cutting over to latest version, 6.11.6, of LDM.
> I get the following when trying to start ldm...
> 
> address@hidden ~]$ ldmadmin start
> The product-queue is OK.
> Checking pqact(1) configuration-file(s)...
> /opt/ldm/etc/pqact.conf: syntactically correct
> Checking LDM configuration-file (/opt/ldm/etc/ldmd.conf)...
> start(): Problem with LDM configuration-file: Mar 19 15:28:25 ldmd[2055]
> NOTE: Starting Up (version: 6.11.6; built: Feb 11 2014 16:26:21)
> address@hidden ~]$ echo $?
> 1
> 
> I googled the message and found a thread, LDM #MSO-599919, with something
> similar.  I ran the following:
> 
> address@hidden ~]$ bin/ldmd -vl - -n etc/ldmd.conf
> Mar 19 15:49:08 ldmd[2309] NOTE: Starting Up (version: 6.11.6; built: Feb 11 
> 2014 16:26:21)
> Segmentation fault
> 
> I have attached a copy of my ldmd.conf file.  Can you help me resolve this?

Our LDM developer will need to weigh-in on why 'bin/ldmd -vl - -n etc/ldmd.conf'
is dumping core, but I can tell you what you need to do to fix your ldmd.conf
problem:

- move the REQUEST line which is currently the last line in the file to anywhere
  before the last ACCEPT entry in the file

  For instance, the following works fine:

#
###############################################################################
# Accept Entries
###############################################################################
# ACCEPT: Who can feed us, currently this action is ONLY needed for WSI data
#
# accept <feedset> <pattern> <hostname pattern>
#
# accept anything from yourself
#
accept  ANY     ".*"            ^((localhost|loopback)|(127\.0\.0\.1\.?$))
accept  EXP     "^rtstats.*"    ^castor\.rcac\.purdue\.edu\.?$
accept  EXP     "^rtstats.*"    ^pollux\.rcac\.purdue\.edu\.?$
accept  EXP     "^rtstats.*"    ^blizzard\.rcac\.purdue\.edu\.?$
request CRAFT   ".*"    pollux.rcac.purdue.edu
accept  EXP     "^rtstats.*"    ^[a-z].*\.eas\.purdue\.edu\.?$

  But this will cause the core dump:

#
###############################################################################
# Accept Entries
###############################################################################
# ACCEPT: Who can feed us, currently this action is ONLY needed for WSI data
#
# accept <feedset> <pattern> <hostname pattern>
#
# accept anything from yourself
#
accept  ANY     ".*"            ^((localhost|loopback)|(127\.0\.0\.1\.?$))
accept  EXP     "^rtstats.*"    ^castor\.rcac\.purdue\.edu\.?$
accept  EXP     "^rtstats.*"    ^pollux\.rcac\.purdue\.edu\.?$
accept  EXP     "^rtstats.*"    ^blizzard\.rcac\.purdue\.edu\.?$
accept  EXP     "^rtstats.*"    ^[a-z].*\.eas\.purdue\.edu\.?$
request CRAFT   ".*"    pollux.rcac.purdue.edu

Why the former example causes a core dump and the latter does not,
I can't say.  I did verify that the former example works and the
latter does not.

As a matter of readability, I suggest putting all REQUEST lines in the
same part of the file.

re:
> Thanks!

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: IPY-349366
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.