I've seen this before
Apr 10 15:48:21 db ldmd[3083] NOTE: child 3087 terminated by signal 6:
pqsurf -p ^(S[AP]) -Q /usr/local/ldm/var/queues/pqsurf.pq -d
/usr/local/ldm /usr/local/ldm/etc/pqsurf.conf
Apr 10 15:48:21 db ldmd[3083] NOTE: Killing (SIGTERM) process group
Apr 10 15:48:21 db ldmd[3083] NOTE: Exiting
-----------------------------------------------------
-Jeff Lake K8JSL
MichiganWxSystem.com
AllisonHouse.com
TheWeatherCenter.net
GRLevelXStuff.com
On 4/10/2013 11:50, daryl herzmann wrote:
Hi Jeff,
Does your ldm log files show an immediate segfault? I reported such a
case like this for RHEL 6.4 to Unidata yesterday.
Apr 8 13:35:10 iem21 ldmd[17764] NOTE: child 18269 terminated by
signal 11
Apr 8 13:35:10 iem21 ldmd[17764] NOTE: Killing (SIGTERM) process group
Does 'dmesg' or 'abortd' show segfaults occuring?
daryl
On Wed, 10 Apr 2013, Jeff Lake wrote:
uggh this is frustrating, but probably simple...
rebooted my server after a mass of yum updates
now ldm-6.11.4 acts like it starts, but doesn't
-bash-4.1$ldmadmin start
The product-queue is OK.
Checking pqact(1) configuration-file(s)...
/usr/local/ldm/etc/ddplus.conf: syntactically correct
/usr/local/ldm/etc/pqact.conf: syntactically correct
Checking LDM configuration-file (/usr/local/ldm/etc/ldmd.conf)...
Starting the LDM server...
-bash-4.1$ ldmadmin watch
There is no LDM server running
