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

[LDM #SER-849220]: Request for adding new IPs to allowed LDM connection


> I am trying to set up a new ldm server to mimic the actions of an old one
> that is about  to retire.
> The old one is really old, and as such it works. It is called cori.met, and
> is still ticking connected to idd.unidata and Pennstate.

OK.  I don't think that cori.met is reporting real-time stats back to us -
it is not showing up in the list of sites/machines in our Statistics by
Host page:


> The new one has a history already. When I first compiled the ldm it had the
> hostname wrong, the LDMHOME wrong, and the config files pointing to
> a wrong ldm home. Just so you are aware. I have fixed all these issues.


> So, I think.
> Oh, and also it has a new CentOS7 image with minimal installation meaning
> some basic things can be not installed in the OS.


> I have recompiled the ldm after fixing what I have noticed was wrong, and
> am trying to connect with the hostname nids.geos.tamu.edu, IP
> Per your advice I am trying to call notifyme with the following results:
> [ldm@nids ~]$ notifyme -vl- -f ANY -h idd.unidata.ucar.edu
> 20201008T144409.601340Z notifyme[24907]             notifyme.c:main:363
> NOTE  Starting Up: idd.unidata.ucar.edu: 20201008144409.600987
> TS_ENDT {{ANY, ".*"}}
> 20201008T144409.601500Z notifyme[24907]             ldm5_clnt.c:forn5:460
> NOTE  LDM-5 desired product-class: 20201008144409.600987
> TS_ENDT {{ANY, ".*"}}
> 20201008T144409.603062Z notifyme[24907]             error.c:err_log:236
> INFO  Resolving idd.unidata.ucar.edu to took
> 0.001375 seconds
> 20201008T144409.664942Z notifyme[24907]
> ldm5_clnt.c:forn_signon:272         ERROR NOTIFYME(idd.unidata.ucar.edu):
> 7: Access denied by remote server
> ^C20201008T144414.631546Z notifyme[24907]             notifyme.c:cleanup:68
> NOTE  exiting
> [ldm@nids ~]$ hostname
> nids.geos.tamu.edu

The fact that the 'notifyme' REQUEST to idd.unidata.ucar.edu did not
work suggests that reverse DNS does not exist for your machine, but
an 'nslookup' shows that it does:

~: nslookup nids.geos.tamu.edu

Non-authoritative answer:
Name:   nids.geos.tamu.edu

~: nslookup

Non-authoritative answer:      name = nids.geos.tamu.edu.

Authoritative answers can be found from:

If you have 'telnet' installed, you can test to see if you
can get to idd.unidata.ucar.edu as follows:

<on nids.geos.tamu.edu>
telnet idd.unidata.ucar.edu 388

A successful connection will show the following output:

Connected to idd.unidata.ucar.edu.
Escape character is '^]'.

An output like this would show that there is no firewall blocking
outbound access to port 388 on your machine, in your department,
in your institution.  If it does not connect, it shows that something
(e.g., firewall rule) is blocking outbound access to a remote machine
on port 388).

> Would you, please, check if you see anything on your end like me reporting
> the wrong hostname, or something else obviously wrong.

Another way to test the ability of the LDM on nids.geos.tamu.edu is for
you to run the same kind of 'notifyme' invocation while I am monitoring
LDM log files on the machine trying to be contacted.  This test would need
to be coordinated so that I am watching while you are trying the following

<as ldm on nids.geos.tamu.edu>
notifyme -vl- -f ANY -h node3.unidata.ucar.edu

Please let me know when you have time to run this test, and I will watch
the LDM log file on node3.unidata.ucar.edu.


Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
Unidata HomePage                       http://www.unidata.ucar.edu

Ticket Details
Ticket ID: SER-849220
Department: Support IDD
Priority: Normal
Status: Open
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.