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

Re: 20050919: sasquatch

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: Re: 20050919: sasquatch
  • Date: Mon, 19 Sep 2005 16:28:23 -0600
Tom,

>Date: Mon, 19 Sep 2005 13:50:34 -0600
>From: Tom Yoksas <address@hidden>
>Organization: UCAR/Unidata
>To: Gerry Creager <address@hidden>
>Subject: 20050919: sasquatch 

The above message contained the following:

> The reason for the LDM exit was a segmentation violation in one of the 
> rpc.ldmds:
[snip]
> Sep 18 05:29:09 sasquatch ernie[21808]: hiya6: TS_ZERO TS_ENDT {{EXP,  ".*"}}
[snip]
> Sep 18 05:29:15 sasquatch ernie[21808]: hiya6: TS_ZERO TS_ENDT {{EXP,  ".*"}}
> Sep 18 05:29:15 sasquatch rpc.ldmd[12714]: child 21808 terminated by signal 11
[snip]

A segmentation violation in a downstream LDM associated with multiple
HIYA-s, eh?  I believe FSL is having a similar problem.

I think there's a problem with the downstream LDM code that's being
triggered by multiple HIYA-s from the rtstats(1) program.  I'm
investigating.

Regards,
Steve Emmerson