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

[LDM #UST-447927]: LDM - LDM 6.4.5 SIGSEGV

Christian,

> I installed the new beta version. Indeed, I do not have anymore sigsegv
> signals.

That's good news.

> However, the cause of this trouble is this (fron the logs), which
> happens each 30 secs:
> Jun 09 09:28:41 kepler idd.cise-nsf.gov[25762] ERROR: Bad file descriptor
> Jun 09 09:28:41 kepler idd.cise-nsf.gov[25762] ERROR: readtcp():
> select() error on socket 4
> Jun 09 09:28:41 kepler idd.cise-nsf.gov[25762] ERROR: one_svc_run(): RPC
> layer closed connection
> Jun 09 09:28:41 kepler idd.cise-nsf.gov[25762] ERROR: Disconnecting due
> to LDM failure; Connection to upstream LDM closed
> Jun 09 09:28:43 kepler idd.cise-nsf.gov[25762] NOTE: LDM-6 desired
> product-class: 20060609091849.539 TS_ENDT {{NIMAGE,
> "(VIS|IR|WV).*(CONUS|SUPER-NATIONAL)"},{NONE,
> "SIG=68e887506856d93e9986831de31532e9"}}
> Jun 09 09:28:44 kepler idd.cise-nsf.gov[25762] NOTE: Upstream LDM-6 on
> idd.cise-nsf.gov is willing to be a primary feeder
> 
> Is there a problem with idd.cise-nsf.gov ??

I don't know.  The problem you're seeing is due to the TCP connection to
the NSF computer getting closed for an unknown reason.  I've seen this
before but have been unable to discover the reason why the TCP connection
shuts down -- dispite a lot of effort.

Does this really happen on your system every 30 seconds?  Are you missing
any data as a consequence?

It could be that upgrading the LDM on the NSF computer *might* fix the
problem.  I'll see what I can do.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: UST-447927
Department: Support LDM
Priority: Normal
Status: On Hold