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

[LDM #UEV-538539]: LDM crash 3/16/2014

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: [LDM #UEV-538539]: LDM crash 3/16/2014
  • Date: Mon, 17 Mar 2014 10:01:33 -0600
Gilbert,

Apparently, the downstream LDM couldn't connect to the upstream LDM server via 
port 388 and so tried using the upstream's portmapper. This succeeded but, due 
to a latent bug in the downstream LDM code, resulted in a NULL client handle 
(and boom!).

I've corrected the code and am working on making a new release. In the 
meantime, ensure that the upstream LDM is available on port 388 and, if 
possible, stop the portmapper on the upstream site (many sysadmins consider it 
a security risk, anyway).

Again, thanks for sending this in.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: UEV-538539
Department: Support LDM
Priority: Normal
Status: Closed