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

[LDM #NUP-437021]: Multiple LDMs running on one system

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 #NUP-437021]: Multiple LDMs running on one system
  • Date: Tue, 31 Jan 2012 13:55:15 -0700
Dan,

> Double-checked the paths, but saw the same thing.
> 
> [ldm_test@sys18 ~]$ whoami
> ldm_test
> [ldm_test@sys18 ~]$ which ldmping
> /usr/local/ldm_test/bin/ldmping
> 
> [ldm_test@sys18 ~]$ /usr/local/ldm_test/bin/ldmping -i0
> Jan 31 20:45:56 INFO:      State    Elapsed Port   Remote_Host           
> rpc_stat
> Jan 31 20:45:56 INFO: Resolving localhost to 127.0.0.1 took 0.000355 seconds
> [ldm_test@sys18 ~]$
> [ldm_test@sys18 ~]$ /usr/local/ldm_test/bin/ldmping -i0 147.81.80.185
> Jan 31 20:46:11 INFO:      State    Elapsed Port   Remote_Host           
> rpc_stat
> Jan 31 20:46:11 INFO: RESPONDING   0.001313  388   147.81.80.185

Actually, you didn't see the same thing. Only the "ldm" user's ldmping(1) 
utility indicated that it connected to an LDM server.

> Now for both the ldm user and the ldm_test user they are set to the same IP 
> 147.81.80.185.  So that when the ldmping is running it passed that IP.  Is 
> that a problem?

Having the same IP address isn't a problem because of the different port 
numbers.

> Thanks
> Dan

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: NUP-437021
Department: Support LDM
Priority: Normal
Status: Closed