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

20030820: [awipsldm] LDM Crashing...

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20030820: [awipsldm] LDM Crashing...
  • Date: Wed, 20 Aug 2003 14:20:18 -0600
Brad,

> Date: Wed, 20 Aug 2003 19:11:52 -0000
> From: address@hidden
> Reply-To: The AWIPS LDM list <address@hidden>
> To: The AWIPS LDM list <address@hidden>
> Subject: [awipsldm] LDM Crashing...

The above message contained the following:

> AwipsLDM List
> Has anyone had problems with LDM crashing after running a few minuets?  We 
> have checked all of the config files, can't find anything wrong.  In the 
> past, LDM would run about a week before crashing, which seems to be very 
> common. Lately ours only runs for a few minuets.  Here is a sample of our 
> /var/adm/syslog/syslog.log at the time of a crash.
> 
> Aug 20 18:04:35 ls1-gld ldm-11[174]: FEEDME(ldm-11.crh.noaa.gov): reclass: 
> 20030820170435.330 TS_ENDT {{EXP,  "^(BCQ*.*|rwis\.kdot)"},{FSL5,  
> ".*(etabcq*.*|...........GribF...|...........GribF..)"},{EXP,  
> ".*(GLDLSR.dat)"},{EXP,  ".*(GLDalert.dat)"},{EXP,  ".*(GLDalertw.dat)"}}
> Aug 20 18:04:35 ls1-gld ldm-11[174]: FEEDME(ldm-11.crh.noaa.gov): OK
> Aug 20 18:04:36 ls1-gld ldm-11[174]: RECLASS: 20030820170436.045 TS_ENDT 
> {{EXP,  "^(BCQ*.*|rwis\.kdot)"},{FSL5,  
> ".*(etabcq*.*|...........GribF...|...........GribF..)"},{EXP,  
> ".*(GLDLSR.dat)"},{EXP,  ".*(GLDalert.dat)"},{EXP,  ".*(GLDalertw.dat)"}}
> Aug 20 18:04:36 ls1-gld ldm-11[174]: Connection reset by peer
> Aug 20 18:04:58 ls1-gld remshd[417]: connect from gw-gld
> Aug 20 18:05:06 ls1-gld ldm-11[174]: run_requester: 20030820170506.698 
> TS_ENDT {{PPS,  ".*"},{EXP,  "^(BCQ*.*|rwis\.kdot)"},{FSL5,  
> ".*(etabcq*.*|...........GribF...|...........GribF..)"},{EXP,  
> ".*(GLDLSR.dat)"},{EXP,  ".*(GLDalert.dat)"},{EXP,  ".*(GLDalertw.dat)"}}
> Aug 20 18:05:13 ls1-gld rpc.ldmd[170]: child 174 terminated by signal 11
> Aug 20 18:05:13 ls1-gld eldm[176]: Interrupt
> Aug 20 18:05:13 ls1-gld pqact[173]: Interrupt
> Aug 20 18:05:13 ls1-gld pqbinstats[172]: Interrupt
> Aug 20 18:05:13 ls1-gld pqexpire[171]: Interrupt
> Aug 20 18:05:13 ls1-gld rpc.ldmd[170]: Interrupt
> 
> Any ideas?

What version of the LDM is running on ls1-gld?

What version of the LDM is running on ldm-11?

Was a core-file created by the SIGSEGV (signal 11) sent to process 174?
If so, what is the stack-trace?

Regards,
Steve Emmerson
LDM Developer