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

[LDM #JLH-115818]: 13.6



Patrick,

I moved your inquiry into our user-support tracking system so that others can
benefit.

> I installed your latest work on my 4 relays and everything seemed to be
> going smoothly and running.. then I looked a little closer
> 
> each ./runtime directory still pointed to the old ldm installation so to
> fix, I did like we used to do in the old days ...
> 
> rm runtime
> ln -s ldm-6.13.6 runtime
> ln -s runtime/* .
> 
> then I started examining the logs to see if anything else was amiss.. on
> one of my primary relays sitting on the HE backbone i noticed this:
> 
> address@hidden:~/var/logs$ cat ldmd.log
> 20170204T010054.144155Z ldmd[1497] NOTE ldmd.c:980:main() Starting Up
> (version: 6.13.6; built: Feb  3 2017 18:11:02)
> 20170204T010054.144279Z ldmd[1497] NOTE ldmd.c:526:create_ldm_tcp_svc()
> Using local address 0.0.0.0:388
> 20170204T010054.145078Z ldmd[1497] WARN ldmd.c:547:create_ldm_tcp_svc()
> Can't register TCP service 300029 on port 388
> 20170204T010054.145088Z ldmd[1497] WARN ldmd.c:550:create_ldm_tcp_svc()
> Downstream LDMs won't be able to connect via the RPC portmapper daemon
> (rpcbind(8),

The warning means that the LDM was unable to register itself with the 
portmapper daemon running on your system and, therefore, downstream LDM-s
won't be able to use your portmapper daemon to connect to your LDM. The
cause could be that your not running a portmapper daemon (e.g., portmapper,
rpcbind) or that you are but the LDM isn't running with the proper privilege
(the program might not be owned by root and setuid).

This is most likely irrelevant, however, because almost all LDM-s use the
well-known port 388 to connect to each other -- bypassing the portmapper
daemon entirely.

> So now I'm thinking how could that be? so i followed the old steps to check.
> 
> /etc/rpc
> ldmd 300029 ldm
> 
> check
> 
> /etc/services
> ldm 388/udp unidata
> ldm 388/tcp unidata
> 
> check
> 
> local0.debug .. check.. or we wouldn't have gotten the logs...
> 
> rebooted to see if error is still there... check it is..
> 
> turned off the firewall to see if something is blocking tcp/udp ports...
> both are open, yet the error is still there...

> this did not solve the issue either

> address@hidden:~/ldm-6.13.6/bin$ sudo chmod u+srwx,g+rx,o+rx ldmd
> address@hidden:~/ldm-6.13.6/bin$ sudo chmod u+srwx,g+rx,o+rx hupsyslog
> 
> what am I forgetting?

Are you running a portmapper daemon?

    ps -ef | egrep 'portmapper|rpcbind'

Many sites don't because they consider it a security risk.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: JLH-115818
Department: Support LDM
Priority: Normal
Status: Closed
===================
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.



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.