[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:43:20 -0700
Dan,

> I checked further into my implementation.  To make sure everything was as it 
> should be.  I removed the installations and re-installed cleanly.  So the 
> setup is 2 users, ldm uses port 388, ldm_test uses port 38888.
> 
> I started the LDM running for the user ldm.  I ran ldmping and this is what I 
> see:
> 
> [ldm@sys18 ~]$ ldmping -i 5 147.81.80.185
> Jan 31 18:04:10 INFO:      State    Elapsed Port   Remote_Host           
> rpc_stat
> Jan 31 18:04:10 INFO: RESPONDING   0.001000  388   147.81.80.185
> Jan 31 18:04:15 INFO: RESPONDING   0.000109  388   147.81.80.185
> Jan 31 18:04:20 INFO: RESPONDING   0.000107  388   147.81.80.185
> Jan 31 18:04:25 INFO: RESPONDING   0.000112  388   147.81.80.185
> 
> 
> Which is what I should see.  If I become user ldm_test and run the same 
> command, as I understand it, I should see nothing.  However, ran I become 
> user ldm_test and run the command, this is what I see:
> 
> [ldm_test@sys18 ~/wsi_config]$ ldmping -i 5 147.81.80.185
> Jan 31 18:05:20 INFO:      State    Elapsed Port   Remote_Host           
> rpc_stat
> Jan 31 18:05:20 INFO: RESPONDING   0.001031  388   147.81.80.185
> Jan 31 18:05:25 INFO: RESPONDING   0.000111  388   147.81.80.185
> Jan 31 18:05:30 INFO: RESPONDING   0.000112  388   147.81.80.185
> Jan 31 18:05:35 INFO: RESPONDING   0.000118  388   147.81.80.185
> 
> Which means when I try and start the ldm as ldm_test and it checks to see if 
> it is already running with ldmadmin isrunning, it will fail.
> 
> 
> Should I see this when I run as the user ldm_test:
> 
> [ldm_test@sys18 ~/wsi_config]$ ldmping -i 5 147.81.80.185
> Jan 31 18:05:20 INFO:      State    Elapsed Port   Remote_Host           
> rpc_stat
> 
> 
> Any thoughts?

What's the absolute pathname of the ldmping(1) utility you executed as user 
"ldm_test"? I suspect that the PATH environment variable for the "ldm_test" 
user causes the "ldm" user's ldmping(1) utility to be executed.

When executing the "ldm_test" user's ldmping(1) utility (with no corresponding 
LDM server running), you should see something like this:

    ~/ldm/package/src: ldmping -i0
    Jan 31 20:41:44 INFO:      State    Elapsed Port   Remote_Host           
rpc_stat
    Jan 31 20:41:44 INFO: Resolving localhost to 127.0.0.1 took 0.000305 seconds

> Thanks
> Dan

Regards,
Steve Emmerson

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