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.
Christian, > To: address@hidden > From: "Christian =?ISO-8859-1?Q?Pag=E9?=" <address@hidden> > Subject: LDM - IRIX64 - Signal 11, ldm killed?!? > Organization: UQAM > Keywords: LDM signal 11 shutdown The above message contained the following: > Institution: Universite du Quebec a Montreal / Atmospheric Science Group > Package Version: 6.0.13 > Operating System: IRIX64 > Hardware Information: SGI > Inquiry: Hi, > > My LDM was killed by signal 11. Any idea why it happened? > > Jun 30 04:17:40 3Q:io ldm[118833812]: ERROR: requester6.c:196: Upstream LDM > died > Jun 30 04:18:10 5Q:io ldm[118833812]: Desired product class: > 20030629160007.684 TS_ENDT {{GEM, ".*" > }} > Jun 30 04:18:10 5Q:io ldm[118833812]: Connected to upstream LDM-6 > Jun 30 04:18:10 5Q:io ldm[118833812]: Upstream LDM is willing to feed > Jun 30 14:46:53 3Q:io ldm[118833812]: ERROR: requester6.c:196: Upstream LDM > died > Jun 30 14:47:23 5Q:io ldm[118833812]: Desired product class: > 20030630040009.540 TS_ENDT {{GEM, ".*" > }} > Jun 30 14:47:25 5Q:io ldm[118833812]: Connected to upstream LDM-6 > Jun 30 14:47:25 5Q:io ldm[118833812]: Upstream LDM is willing to feed > Jun 30 16:16:50 3Q:io ldm[118833812]: ERROR: requester6.c:196: Upstream LDM > died > Jun 30 16:17:20 5Q:io ldm[118833812]: Desired product class: > 20030630040009.540 TS_ENDT {{GEM, ".*" > }} > Jun 30 16:17:20 5Q:io ldm[118833812]: Connected to upstream LDM-6 > Jun 30 16:17:20 5Q:io ldm[118833812]: Upstream LDM is willing to feed > Jun 30 16:17:31 5Q:io rpc.ldmd[121683381]: child 121702674 terminated by > signal 11 I would like to know more about process 121702674. Would you please send me the output from the following command executed in the "logs" subdirectory of the LDM user: $ fgrep '[121702674]' `ls -rt ldmd.log*` Regards, Steve Emmerson