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

[LDM #VVJ-331218]: LDM 6.11.7 Errors - exit LDM Not starting

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 #VVJ-331218]: LDM 6.11.7 Errors - exit LDM Not starting
  • Date: Sat, 27 Sep 2014 11:11:05 -0600
Russ,

> One reason I can't get out to uniata from the geoprod serves is they do
> not have network NATs to get outside the firewall.

I wonder if a similar mechanism is disallowing the connections that your LDM-s 
can't make. There were no messages in the LDM log file on your FOS server 
regarding a connection attempt from Geoprod4. When you tried a notifyme(1) to 
one of our IDD servers, the same lack of messages occurred.

> But, I was just
> googling teh "ERROR: NOTIFYME 7" and found our conversations on
> http://www.unidata.ucar.edu/support/help/MailArchives/ldm/msg07146.html
> and it is displaying my server IP addresses.
> 
> Please remove those convesations as we cannot display out internal IP
> addresses to the public.

Done.

It took one of us a half-hour to edit the emails. We normally make all support 
email publicly available in order to support our users while reducing our 
costs. In the future, would you please add a comment IN EVERY APPLICABLE EMAIL 
about not making it public. Thanks.

> Still puzzled as to why my geoprod serves cannot talk to my internal FOS
> servers....working on it..

I'm beginning to suspect your network and firewall rules. Using telnet(1) on 
Geoprod4 to access the LDM on your FOS server -- together with a network 
snooper and a network administrator -- should allow you to diagnose the 
problem. If the LDM on your FOS server isn't logging the connection attempt, 
then the LDM isn't seeing it.

> Thanks
> Russ

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: VVJ-331218
Department: Support LDM
Priority: Normal
Status: Closed